AssertionError response when attempting to create cable #12076
-
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
Sounds like your database has got into an inconsistent state (which can happen, since Netbox/Django model validation is subject to various race conditions) If you can get a backtrace from your error, that will help. You can get this by setting EMAIL and ADMINS in configuration.py, and then reproducing the error - a full report including the backtrace should be emailed to you. Or you can set DEBUG=True and get the backtrace in the web interface. |
Beta Was this translation helpful? Give feedback.
-
OK, here's some context for that code: it's trying to trace a cable path.
It seems that if there are multiple rearports linked to the same cable, then each rearport is expected to have a single position only. (A rearport with multiple "positions" is one that links to multiple frontports) Try tracing from UPG Rx and UPG Tx, using the automatic cable tracing and/or manually following cables, and look at each rearport on the path, and see which ones have been defined to have multiple positions, and if that's what you expect. You may be able to find what's different about these two particular frontports that causes the crash. For example, even if each frontport is only linked to a single rearport, the rearport might have been defined to have more than 1 position. |
Beta Was this translation helpful? Give feedback.
OK, here's some context for that code: it's trying to trace a cable path.