Virtual Chassis Mastership addition automatically changes device vc_position, breaking backup/restore of DB #2087
Labels
status: accepted
This issue has been accepted for implementation
type: bug
A confirmed report of unexpected behavior in the application
Issue type
[ ] Feature request
[X] Bug report
[ ] Documentation
Environment
Description
Upon creating a Virtual Chassis the position of the master gets updated to 1, causing a conflict whenever this was not the device 1 of the chassis (Example: Juniper fpc0 device being the master). This auto-update breaks backup and restore of the database.
Steps to replicate (using pynetbox for simplicity). First I create two devices and the virtual chassis
After this, using the GUI I manually moved deviceA to have position 0 and added deviceB to the cluster as I intended originally
And now backup and restore breaks because of the vc_id, position constraint
The text was updated successfully, but these errors were encountered: