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

Do not start elemental-register timer manually #1323

Merged

Conversation

davidcassany
Copy link
Contributor

Starting the service manually prevent proper ordering and tracking of related services. Having a manual start makes it difficult form other services to check its status as there is no obvious way order the related executions.

Follow up for #1263

Starting the service manually prevent proper ordering and tracking
of related services. Having a manual start makes it difficult form
other services to check its status as there is no obvious way order
the related executions.

Signed-off-by: David Cassany <[email protected]>
@davidcassany davidcassany requested a review from a team as a code owner March 26, 2024 11:44
@davidcassany
Copy link
Contributor Author

@@ -1,6 +1,9 @@
[Unit]
Description=Run elemental-register every 30 minutes
Documentation=https://elemental.docs.rancher.com
# Do not run the timer for installation media or recovery system
ConditionPathExists=!/run/elemental/live_mode
ConditionPathExists=!/run/elemental/recovery_mode
Copy link
Contributor Author

Choose a reason for hiding this comment

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

These conditions match with the conditions that were added to the manual start within the deleted file.

@davidcassany davidcassany merged commit 7a04678 into rancher:main Mar 26, 2024
16 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants