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

No cable trace available after upgrade to 2.10 #4507

New Issue
Closed
opened 2025-12-29 18:36:50 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:36:50 +01:00
Owner
Copy Link

Originally created by @kr3ator on GitHub (Jan 28, 2021).

Environment

  • Python version: 3.9.1
  • NetBox version: 2.10.4

Steps to Reproduce

  1. Have existing cables in the database with Netbox version lower than 2.10
  2. Upgrade Netbox to >= 2.10
  3. Go to Device --> Interfaces
  4. Click the Trace button for an interface with cable conntected

Expected Behavior

'Connection' column populated with information about the device on the other side of the cable.
After clicking the Trace button a cable trace is shown with termination A&B names, interface names, etc.

Observed Behavior

The Connection column shows '-'.
After clicking the Trace button an almost empty page is displayed. In the box named 'Related paths' it says 'None found'.

When I add a new cable everything works as expected.

Originally created by @kr3ator on GitHub (Jan 28, 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.9.1 * NetBox version: 2.10.4 <!-- 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. Have existing cables in the database with Netbox version lower than 2.10 2. Upgrade Netbox to >= 2.10 3. Go to Device --> Interfaces 4. Click the Trace button for an interface with cable conntected <!-- What did you expect to happen? --> ### Expected Behavior 'Connection' column populated with information about the device on the other side of the cable. After clicking the Trace button a cable trace is shown with termination A&B names, interface names, etc. <!-- What happened instead? --> ### Observed Behavior The Connection column shows '-'. After clicking the Trace button an almost empty page is displayed. In the box named 'Related paths' it says 'None found'. When I add a new cable everything works as expected.
adam closed this issue 2025-12-29 18:36:50 +01:00
adam commented 2025-12-29 18:36:51 +01:00
Author
Owner
Copy Link

@LuPo commented on GitHub (Jan 28, 2021):

Have you run the migrations as per the documentation?
I suppose you are running the dockerized netbox, because the update.sh already does what you need.
If I am correct, follow the missing step on https://github.com/netbox-community/netbox-docker/releases/tag/0.27.0
docker-compose run --rm netbox ./manage.py trace_paths should solve it

@LuPo commented on GitHub (Jan 28, 2021): Have you run the migrations as per the documentation? I suppose you are running the dockerized netbox, because the update.sh already does what you need. If I am correct, follow the missing step on https://github.com/netbox-community/netbox-docker/releases/tag/0.27.0 `docker-compose run --rm netbox ./manage.py trace_paths` should solve it
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
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#4507
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?