starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Deleting connected Interface leaves Server Error-prone Cable behind #8965

New Issue
Closed
opened 2025-12-29 20:43:27 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:43:27 +01:00
Owner
Copy Link

Originally created by @koratfood on GitHub (Dec 14, 2023).

Deployment Type

Self-hosted

NetBox Version

v3.6.6

Python Version

3.10

Steps to Reproduce

  1. Create two devices (e.g.: DevA and DevB, of any Device Type and at any Location you want)
  2. Add an interface (name: "TestInt", type: 1GE) to each of the devices you created
  3. Connect a cable between testint on DevA and testint on DevB
  4. Delete interface TestInt on DevB
  5. Attempt to edit the still-existing Cable object on DevA

Expected Behavior

If the Cable object's continued existence in NetBox is even justifiable past reproduction step no. 4, the Cable should remain editable so that the user can reterminate it. Alternatively, there should at the very least be a proper error message telling the user why it is not, and what to do about it.

Observed Behavior

Screenshot_20231214_202036

Originally created by @koratfood on GitHub (Dec 14, 2023). ### Deployment Type Self-hosted ### NetBox Version v3.6.6 ### Python Version 3.10 ### Steps to Reproduce 1. Create two devices (e.g.: DevA and DevB, of any Device Type and at any Location you want) 2. Add an interface (name: "TestInt", type: 1GE) to each of the devices you created 3. Connect a cable between testint on DevA and testint on DevB 4. Delete interface TestInt on DevB 5. Attempt to edit the still-existing Cable object on DevA ### Expected Behavior If the Cable object's continued existence in NetBox is even justifiable past reproduction step no. 4, the Cable should remain editable so that the user can reterminate it. Alternatively, there should at the very least be a proper error message telling the user why it is not, and what to do about it. ### Observed Behavior ![Screenshot_20231214_202036](https://github.com/netbox-community/netbox/assets/64777963/69f8ac5c-9257-4651-9857-6b59680bccb0)
adam added the type: bugstatus: duplicate labels 2025-12-29 20:43:27 +01:00
adam closed this issue 2025-12-29 20:43:27 +01:00
adam commented 2025-12-29 20:43:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 14, 2023):

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #11460 for further discussion.

@jeremystretch commented on GitHub (Dec 14, 2023): Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #11460 for further discussion.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: duplicate type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8965
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?