Empty cable objects after deleting last termination

[kr3ator]

NetBox version

v3.3.5

Python version

3.10

Steps to Reproduce

1. Create two devices with interfaces.
2. Create a cable between the devices.
3. Delete device A.
4. Either delete device B or the interface of device B that was used in the Cable.

Expected Behavior

The Cable object should be deleted after deleting the last termination.

Observed Behavior

The Cable object is not deleted and has no terminations in it.

[fggec]

Same here.

[jeremystretch]

The Cable object should be deleted after deleting the last termination.

I think our current sticking point is deciding whether or not the above assertion is true. I don't have a strong opinion either way, but the current implementation permits cables to exist with no terminations at either end. Whether this was by design or by accident I can't recall. 😆

[CADbloke]

It is physically possible for a cable to exist without terminations so it should probably be possible too in the documentation for that cable. imho.

[fggec]

Yes but then you have to reference it somewhere in the Doku. I see 3 possible solutions for this:

1. cables can exist without a termination. -> Reference in Doku
2. cables cannot exist without a termination. -> should be deleted.
3. let the users choose if 1 or 2. this could be a separate checkbox or separate window. When you delete a device the user can select every cable that should be deleted or not with checkboxes maybe. Also for single cable if it's disconnected and has only one termination on one device left.

I would prefer the third way

[jeremystretch]

We discussed this in today's maintainers meeting, and the consensus was to delete a cable upon the deletion of its last termination. In the UI, this will first prompt the user to confirm the cable's deletion.

[CADbloke]

We discussed this in today's maintainers meeting, and the consensus was to delete a cable upon the deletion of its last termination. In the UI, this will first prompt the user to confirm the cable's deletion.

What will the default behaviour for the API be? Alternatively, can we specify they behaviour in the API call?

[arthanson]

Thinking for the API case it should probably maintain default of not deleting the cable, but provide an option "delete_if_unterminated" or something on the termination delete API.

Also there is the bulk-disconnect case, not sure if it makes sense to put a cable deletion confirmation on that as well.. would need to filter the cables that have no terminations and present a list of all of them.

[PaulWestphal]

I'm getting an AtributeError when trying to edit a cable after deleting all terminations on one side:

<class 'AttributeError'>

'str' object has no attribute 'label'

Python version: 3.10.6
NetBox version: 3.4.6

[serge-deiss-obt]

@PaulWestphal :
I do get the same Error if i try to edit them, however it is still possible to delete them.
In the GUI there is currently to my knowledge no way to filter for these now orphaned Cables specifically to delete them in Bulk.

<class 'AttributeError'>

'str' object has no attribute 'label'

Python version: 3.10.6
NetBox version: 3.4.8