Skip to content
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

don't stop/start crond and don't start services after restore #453

Merged
merged 1 commit into from
Jun 6, 2024

Conversation

evgeni
Copy link
Member

@evgeni evgeni commented Jun 4, 2024

foreman-maintain takes care of all that, no need to duplicate work

foreman-maintain takes care of all that, no need to duplicate work

- name: Restart services
command: foreman-maintain service start

# We don't use pause module here because it displays a prompt
# to use ctrl+c which would break out of a production script.
- name: Wait for foreman-tasks service to start
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the sleep still needed? By now, don't we guarantee services being available after systemctl start $service?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one hunk at a time ;)

foreman-tasks takes a moment to assemble, so hammer ping often shows that one as "dead" if you do it directly after, but the sleep is certainly too long

@evgeni evgeni merged commit 85bc189 into master Jun 6, 2024
2 checks passed
@evgeni evgeni deleted the fewer-services branch June 6, 2024 11:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants