test(e2e): add e2e check for interface order after ClusterNetwork removal#2124
Merged
Conversation
LopatinDmitr
changed the title
Signed-off-by: Dmitry Lopatin <dmitry.lopatin@flant.com>
LopatinDmitr
force-pushed
the
test/e2e/order-interfaces
branch
from
e727c82 to
e2edb99
Compare
danilrwx
approved these changes
Mar 23, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Description
Add e2e coverage for additional network interface ordering when ClusterNetworks are removed.
The tests now support checking multiple VLAN-based ClusterNetworks and verify that guest interface names stay stable after removing the middle ClusterNetwork and rebooting the VM.
Why do we need it, and what problem does it solve?
We need regression coverage for interface renumbering/order issues in VMs with multiple additional networks.
Without this check, removing one ClusterNetwork could silently change interface naming/order in guest OS after reboot, which may break network configuration relying on persistent interface names.
Checklist
Changelog entries