bridge: honor bridge-allow-untagged in query-check - #353
Open
masonelmore wants to merge 1 commit into
Open
masonelmore wants to merge 1 commit into
masonelmore wants to merge 1 commit into
Conversation
A bridge port with "bridge-allow-untagged no" is configured with no pvid, but query-check derived the expected pvid from bridge-pvid alone and fell back to 1 when there was none. ifquery -c reported "bridge pvid error" on every such port. Closes CumulusNetworks#332 Signed-off-by: Mason Elmore <masonelmore@users.noreply.github.com>
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
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.
ifquery --checkandifupdisagree about the PVID a bridge port should have whenbridge-allow-untaggedisno. Apply leaves the port with no PVID (bridge.py:1914-1922). The check expects a PVID of 1, so it fails on a correct configuration. This alignsifquerywithifup. Ports that allow untagged traffic are unaffected. Closes #332.Tested on Proxmox VE 9.1.7 with ifupdown2
3.3.0-1+pmx12: