CASMTRIAGE-2793 Add Toggle for Exclusive IPv4 #21
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.
Summary and Scope
When testing CASMTRIAGE-2793 on MUG, IPv6 networking between the deployment server and client were not fully functional. During those tests, IPv6 was preventing the download of artifacts and the initial call-to-home by dracut. Using this feature MUG was able to deploy itself by forcing IPv4.
By default metal-dracut will use IPv4 unless it is told otherwise by the
new metal.ipv4 argument being set to 0.
Issue Type
Example:
Prerequisites
MUG was able to download and fetch artifacts after incorporating this RPM.
Idempotency
Risks and Mitigations
What is less risky, or more risky now - or if your mod fails is there a new risk?
We're no no longer using whatever the environment provides by default, and forcing an older IP catalogue. This is retroactive, in the sense that we may want to remove this in the future.