This is harmless, but is indicative of some odd logic in the migration script.
Description
Description
Details
Details
- Difficulty level
- Unknown (require assessment)
- Version
- 1.2.0
- Why the issue appeared?
- Will be filled on close
Event Timeline
Comment Actions
The fault was in XorpConfigParser, whose "set" function behaves as if all nodes were multi nodes, so it was adding a value where none was needed (that's on top of the fact that it didn't properly check if it exists).
With the new library, that's no longer an issue.