Replies: 1 comment 1 reply
-
An exception is not expected and should not be visible to end users, so it's a bug. If you can set DEBUG=True in configuration.py, and show the full backtrace from the exception, that would be helpful to the developers.
I think that's a situation you shouldn't be able to get into, but people have observed this in the past - indeed someone wrote a script to find orphaned cables which are terminated only at one end. Hence there are potentially two bugs here:
It's possible that the Netbox dev team will only accept one of these as a bug, as I don't know what the official policy is on the validity of cables which are terminated at one end (although I note the GUI doesn't allow a cable to be explicitly disconnected at one end) |
Beta Was this translation helpful? Give feedback.
-
Hi,
II have a typical setup
switch <--> patchpanel <--> wallmounted plug <--> device (like pc)
From the switch I can easily see the cable trace and even see what device is connected to a specific port. Great work, guys!
Now when I just delete the device (without removing the cable first) I am getting an error when I try to trace the cable from the switch as before.
This is what I am getting when trying to trace the cable.
So I have to manually trace the cable to the wallmounted plug, remove the cable (which physically does not exist any more) and then I can trace the other cables from the switch port to the plug.
In my expectation it should ignore the cable with the loose end and display the trace as far as possible.
Or is this expected?
/KNEBB
Beta Was this translation helpful? Give feedback.
All reactions