Compute-Init: wait for cloud-init before NFS mount #635
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We are seeing issues where compute-init hits:
TASK [Check if hostvars exist]
FAILED! => {"changed": false, "msg": "Permission denied"}
We have found we are ignoring errors on the mount.
Its possible the mount will fail if the host networking
has not be setup.
Lets wait to make sure we can talk to NFS before attempting
the NFS mount, mostly checking because the host networking
stack might not yet be setup correctly.
We could do "cloud-init status --wait" and block on cloud-init
having finished, however we don't really depend on all parts
of cloud-init being complete.
Equally, we could think about ansible-init systemd unit file
depending on cloud-init or the network being available, but
there are cases where we do not want that.
|
fatimage builds bumped above: https://github.com/stackhpc/ansible-slurm-appliance/actions/runs/14176473687/job/39712478972 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are seeing issues where compute-init hits:
TASK [Check if hostvars exist]
FAILED! => {"changed": false, "msg": "Permission denied"}
We have found we are ignoring errors on the mount. Its possible the mount will fail if the host networking has not be setup.
Lets wait to make sure we can talk to NFS before attempting the NFS mount, mostly checking because the host networking stack might not yet be setup correctly.
We could do "cloud-init status --wait" and block on cloud-init having finished, however we don't really depend on all parts of cloud-init being complete.
Equally, we could think about ansible-init systemd unit file depending on cloud-init or the network being available, but there are cases where we do not want that.