Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
koratfood opened this issue Dec 14, 2023 · 1 comment
Closed

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

koratfood opened this issue Dec 14, 2023 · 1 comment
Labels
status: duplicate This issue has already been raised type: bug A confirmed report of unexpected behavior in the application

Comments

@koratfood
Copy link
Contributor

koratfood commented 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

@koratfood koratfood added the type: bug A confirmed report of unexpected behavior in the application label Dec 14, 2023
@jeremystretch
Copy link
Member

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

@jeremystretch jeremystretch closed this as not planned Won't fix, can't repro, duplicate, stale Dec 14, 2023
@jeremystretch jeremystretch added the status: duplicate This issue has already been raised label Dec 14, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: duplicate This issue has already been raised type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants