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

Changing cable from planned to installed breaks both the connection and tracing #4488

New Issue
Closed
opened 2025-12-29 18:36:33 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:36:33 +01:00
Owner
Copy Link

Originally created by @phseidler on GitHub (Jan 22, 2021).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.10.1

Steps to Reproduce

  1. Change any cable from planned to installed
  2. When tracing the cable, you get the following error message:
    grafik
  3. The cable still shows up as connected, but the interface, power port, etc. shows this:
    grafik
  4. When the page is reloaded, at the point where it shows the connection, there is nothing there anymore:
    grafik
    This shows up on both connected devices.
  5. When looking at the cable, it still shows up as connected and what it is connected to.
  6. This bug was reproducable for both me and a colleague, who used the demo version.

Expected Behavior

Cable should still be properly connected when changed from planned to installed

Observed Behavior

When tracing a cable, you get an error message and the connection doesn't show up everywhere anymore, even though it apparently still exists.

Originally created by @phseidler on GitHub (Jan 22, 2021). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for reporting reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, please start a discussion instead: https://github.com/netbox-community/netbox/discussions Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report, and that any plugins have been disabled. --> ### Environment * Python version: 3.6.8 * NetBox version: 2.10.1 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a client library such as pynetbox. --> ### Steps to Reproduce 1. Change any cable from planned to installed 2. When tracing the cable, you get the following error message: ![grafik](https://user-images.githubusercontent.com/77830257/105468198-0219e280-5c97-11eb-92cc-442949aa6cda.png) 3. The cable still shows up as connected, but the interface, power port, etc. shows this: ![grafik](https://user-images.githubusercontent.com/77830257/105468870-bf0c3f00-5c97-11eb-8b6f-d918e5b594d7.png) 4. When the page is reloaded, at the point where it shows the connection, there is nothing there anymore: ![grafik](https://user-images.githubusercontent.com/77830257/105469666-e6174080-5c98-11eb-8bd0-74d0b3bc2abd.png) This shows up on both connected devices. 5. When looking at the cable, it still shows up as connected and what it is connected to. 6. This bug was reproducable for both me and a colleague, who used the demo version. <!-- What did you expect to happen? --> ### Expected Behavior Cable should still be properly connected when changed from planned to installed <!-- What happened instead? --> ### Observed Behavior When tracing a cable, you get an error message and the connection doesn't show up everywhere anymore, even though it apparently still exists.
adam added the status: duplicate label 2025-12-29 18:36:33 +01:00
adam closed this issue 2025-12-29 18:36:33 +01:00
adam commented 2025-12-29 18:36:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 22, 2021):

Sounds like #5488. Please upgrade to the latest release and re-test.

@jeremystretch commented on GitHub (Jan 22, 2021): Sounds like #5488. Please upgrade to the latest release and re-test.
adam commented 2025-12-29 18:36:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 26, 2021):

I'm almost certain this is a duplicate of #5488, so I'm going to close it out, but please comment here if you're still able to reproduce this issue on the latest release.

@jeremystretch commented on GitHub (Jan 26, 2021): I'm almost certain this is a duplicate of #5488, so I'm going to close it out, but please comment here if you're still able to reproduce this issue on the latest release.
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
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#4488
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?