Handle duplication during parser second pass (LP: #2007682) #329
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
When the parser needs a second pass, some configuration is being added again to their respective lists. We handle these cases already in other places either by checking if the values are present in their data structures or checking if the number of nodes in the YAML subtree matches the number of values in the lists/hashes. The second approach doesn't work well though when the same interface is defined in another file with extra configuration (example LP: #2003061)
This PR addresses 5 cases of duplication:
The example below will generate duplicated data for the routing-policy, nameservers addresses and search domains:
Result:
The example below will generate ovs commands with duplicated protocols and controller addresses:
Result:
This behavior is also visible with
netplan get
:This is the new behavior:
Checklist
make check
successfully.make check-coverage
).