Fix HNV installation network conflicts across all distros by automati… #108
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
…cally cleaning up stale standalone interfaces after they are enslaved to the HNV bonding device. Previously, if an HNV was configured on HMC with SR_IOV and backing devices assigned HNV IDs, a new installation without bonding support caused the HNV init scripts at reboot to create bonding devices that conflicted with existing interfaces, resulting in immediate network loss. This update automates resolution of these conflicts by removing outdated standalone interfaces and transferring IP configuration to the bonded interface, eliminating the need for manual user intervention. Signed-off-by: Mingming Cao <[email protected]>
Contributor
|
It would be good to do a follow on change for ipv6 support. Also, does this work if the interface is configured for DHCP rather than a static IP? |
Member
|
Merged into next branch as commit f3ddb50 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
…cally cleaning up stale standalone interfaces after they are enslaved to the HNV bonding device. Previously, if an HNV was configured on HMC with SR_IOV and backing devices assigned HNV IDs, a new installation without bonding support caused the HNV init scripts at reboot to create bonding devices that conflicted with existing interfaces, resulting in immediate network loss. This update automates resolution of these conflicts by removing outdated standalone interfaces and transferring IP configuration to the bonded interface, eliminating the need for manual user intervention.