feat: add subport's segmentation id check #1310
Merged
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
mfencik
force-pushed
the
fix_native_vlan_clash
branch
3 times, most recently
from
f26079f to
0c37077
Compare
mfencik
force-pushed
the
fix_native_vlan_clash
branch
from
0c37077 to
1d5ee84
Compare
nicholaskuechler
approved these changes
Oct 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
When adding a subport to a trunk in openstack, if by a chance the segmentation_id selected by user is the same as native vlan(aka parent’s port network vlan segment) then the switch will fail to configure the switchport correctly.
This PR will impose limitation for segmenation_id of a subport. It will check all current network segment ranges and if segmentation_id used is inside current ranges, it will raise an error.