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

fix: wait for cloud-init.service to fully activate #3020

Closed
wants to merge 1 commit into from

Conversation

catmsred
Copy link
Collaborator

@catmsred catmsred commented Mar 27, 2024

Once the systemd constraint on After cloud-config.service was removed, there are situations where cloud-config.service runs so long after pro that the python code that waits for cloud-config.service to finish activating is being bypassed as if cloud-init isn't on the system. This change forces pro to wait for cloud-config to finish if cloud-init is running at all.

Fixes #3000

Please Squash this PR with this commit message

fix: wait for cloud-init.service to fully activate

Once the systemd constraint on After cloud-config.service was
removed, there are situations where cloud-config.service runs so
long after pro that the python code that waits for
cloud-config.service to finish activating is being bypassed as if
cloud-init isn't on the system.  This change forces pro to wait
for cloud-config to finish if cloud-init is running at all.

Fixes: #3000 

Checklist

  • I have updated or added any unit tests accordingly
  • I have updated or added any integration tests accordingly [still TODO]
  • Changes here need to be documented, and this was done in:

Does this PR require extra reviews?

  • Yes
  • No

@@ -54,6 +71,7 @@ def test_wait_for_cloud_config(
active_state_side_effect,
expected_sleep_calls,
):
print(active_state_side_effect)
Copy link
Member

Choose a reason for hiding this comment

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

This one is not needed anymore (:

Once the systemd constraint on After cloud-config.service was
removed, there are situations where cloud-config.service runs so
long after pro that the python code that waits for
cloud-config.service to finish activating is being bypassed as if
cloud-init isn't on the system.  This change forces pro to wait
for cloud-config to finish if cloud-init is running at all.
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.

Bug: pro sometimes runs before cloud-config.service
2 participants