controller/node: skip update vlanconfig with witness node #105
Conversation
This file contains 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
- we did not apply any vlanconfig on the witness node,
so we need to skip the vlanconfig update when witness
node change.
Signed-off-by: Vicente Cheng <[email protected]>
Vicente-Cheng
force-pushed
the
fix-matched-nodes-update
branch
from
afa8df4 to
0a70edf
Compare
|
@Mergifyio backport v0.4.x |
✅ Backports have been created
|
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.
Problem:
Now, the
matched-nodeswill filter out the witness node with creation.However, the controller has a chance to update the witness node to the
matched-nodeson the controller part.Solution:
We need to skip to update the
matched-nodeswith the witness node change.Related Issue:
#104 (comment)
Test plan:
Make sure the
matched-nodesannotation of vlanconfig does not contain any witness node.