Improve systemd ordering for cloud-init-local to preserve /var mount #70
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
When enrolling bare-metal overcloud nodes with Kayobe, I encountered an ordering issue that was seemingly caused by an insufficient dependency declaration. This resulted in /var (and critical data such as authorized_keys) being overwritten during provisioning. This commit updates the systemd override to explicitly ensure the full /var mount is present before cloud-init-local.service starts.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR updates the initial systemd override to explicitly ensure the full /var mount is present before cloud-init-local.service starts.