controller/node: skip update vlanconfig with witness node (backport #105) #108
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-nodes
will filter out the witness node with creation.However, the controller has a chance to update the witness node to the
matched-nodes
on the controller part.Solution:
We need to skip to update the
matched-nodes
with the witness node change.Related Issue:
#104 (comment)
Test plan:
Make sure the
matched-nodes
annotation of vlanconfig does not contain any witness node.This is an automatic backport of pull request #105 done by [Mergify](https://mergify.com).