-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keycloak service fails on first attempt however works on second #259
Comments
Can you please run the playbook with |
Please see below
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
When running playbook for Keycloak Quarkus the first attempt fails with the following message:
FAILED! => {"changed": false, "msg": "Unable to start service keycloak: Job for keycloak.service failed because the control process exited with error code.\nSee \"systemctl status keycloak.service\" and \"journalctl -xe\" for details.\n"}
When run again without any changes it is successful
It seems that notify : restart keyclock gets invoked on Flush Pending hanlders prior to Start and wait for keycloak service.
On the second run of the playbook, the handler is skipped because the previous run has run all the tasks that would have triggered it and runs
ansible.builtin.include_tasks: start.yml
which is succesful.
Is there a better way to handle this restart on the first run ?
ISSUE TYPE
ANSIBLE VERSION
COLLECTION VERSION
STEPS TO REPRODUCE
EXPECTED RESULTS
A successful deployment
ACTUAL RESULTS
Requires running deployment twice to achieve the same result.
On second attempt
The text was updated successfully, but these errors were encountered: