CASMPET-7263: Force goss-servers to wait until hostname is set #610
Conversation
This file contains 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
mharding-hpe
requested review from
kimjensen-hpe,
ndavidson-hpe,
jpdavis-prof,
don-bahls-hpe,
jacobsalmela and
bo-quan
leliasen-hpe
approved these changes
Oct 28, 2024
|
/backport release/1.5 release/1.4 |
|
Backporting into branch release/1.5 was successful. New PR: #612 |
|
Backporting into branch release/1.4 was successful. New PR: #613 |
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.
On gamora recently, the goss servers started before cloud-init had set the system hostname. This caused some tests not to run, because the hostname in the Goss variable file was incorrect.
This PR changes the startup script for the goss-servers service to do a few things:
I tested this on mug.