A minor bug was revealed in the context of reading priorities from the XML cache (T6146): the generation of the reference tree merges redundant nodes from the XML interface definitions, but failed to update top-level node data (node type, etc.); it was unnoticed as this was always the default data, but now matters as we are tracking owner/priority attributes. A simple fix addresses this.
Description
Description
Details
Details
- Difficulty level
- Easy (less than an hour)
- Version
- -
- Why the issue appeared?
- Will be filled on close
- Is it a breaking change?
- Unspecified (possibly destroys the router)
- Issue type
- Bug (incorrect behavior)
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | FEATURE REQUEST | Viacheslav | T6121 Extend service config-sync for sections vpn, policy, vrf | ||
| Resolved | BUG | jestabro | T6145 Service config-sync does not rely on priorities but must | ||
| Backport candidate | FEATURE REQUEST | jestabro | T6146 Add python script to get all priorities of service or section from XML | ||
| Backport candidate | BUG | jestabro | T6149 Update node_data when merging nodes in reference tree generation |