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

DCIM LLDP Neighbor issue after 2.5 upgrade. #2198

New Issue
Closed
opened 2025-12-29 17:23:31 +01:00 by adam · 5 comments
adam commented 2025-12-29 17:23:31 +01:00
Owner
Copy Link

Originally created by @VeNoMouS on GitHub (Dec 11, 2018).

Environment

  • Python version: 3.6.7
  • NetBox version: 2.5.0

After upgrade from 2.4 to 2.5 we are getting the following error when trying to view a devices lldp neigbhours.

<class 'django.urls.exceptions.NoReverseMatch'>

Reverse for 'device' with keyword arguments '{'pk': ''}' not found. 1 pattern(s) tried: ['dcim/devices/(?P<pk>\\d+)/$']

Steps to Reproduce

DCIM -> devices -> lldp-neighbours

Expected Behavior

For it to work, as in 2.4

Observed Behavior

image

Originally created by @VeNoMouS on GitHub (Dec 11, 2018). ### Environment * Python version: 3.6.7 * NetBox version: 2.5.0 After upgrade from 2.4 to 2.5 we are getting the following error when trying to view a devices lldp neigbhours. ``` <class 'django.urls.exceptions.NoReverseMatch'> Reverse for 'device' with keyword arguments '{'pk': ''}' not found. 1 pattern(s) tried: ['dcim/devices/(?P<pk>\\d+)/$'] ``` ### Steps to Reproduce DCIM -> devices -> lldp-neighbours ### Expected Behavior For it to work, as in 2.4 <!-- What happened instead? --> ### Observed Behavior ![image](https://user-images.githubusercontent.com/597545/49829500-7cf34c80-fdf3-11e8-9e4c-57a388d3a7d6.png)
adam added the type: bugstatus: accepted labels 2025-12-29 17:23:31 +01:00
adam closed this issue 2025-12-29 17:23:32 +01:00
adam commented 2025-12-29 17:23:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 11, 2018):

I'm not able to replicate this on v2.5.0. Going to http://localhost:8000/dcim/devices/<pk>/lldp-neighbors/ works as expected. Please revise your issue to include the exact steps needed to replicate the error on a fresh installation.

@jeremystretch commented on GitHub (Dec 11, 2018): I'm not able to replicate this on v2.5.0. Going to `http://localhost:8000/dcim/devices/<pk>/lldp-neighbors/` works as expected. Please revise your issue to include the exact steps needed to replicate the error on a fresh installation.
adam commented 2025-12-29 17:23:32 +01:00
Author
Owner
Copy Link

@VeNoMouS commented on GitHub (Dec 12, 2018):

We deleted the device and re-created it, and the issue went away, however the issue still only occurred after we upgraded from 2.4 to 2.5, so perhaps there is an issue in the upgrade migration process somewhere...

I am happy for this to be closed as we can not replicate the issue ourselves unless we restore the db and do a 2.4 to 2.5 upgrade again.

@VeNoMouS commented on GitHub (Dec 12, 2018): We deleted the device and re-created it, and the issue went away, however the issue still only occurred after we upgraded from 2.4 to 2.5, so perhaps there is an issue in the upgrade migration process somewhere... I am happy for this to be closed as we can not replicate the issue ourselves unless we restore the db and do a 2.4 to 2.5 upgrade again.
adam commented 2025-12-29 17:23:33 +01:00
Author
Owner
Copy Link

@bsteinert commented on GitHub (Dec 17, 2018):

i run in to the issue too. In my netbox install this only happens when there is a circuit configured on one port of the device. If there are no circuits, everything works like before.

perhaps something is broken because of the new "cables" feature...

@bsteinert commented on GitHub (Dec 17, 2018): i run in to the issue too. In my netbox install this only happens when there is a circuit configured on one port of the device. If there are no circuits, everything works like before. perhaps something is broken because of the new "cables" feature...
adam commented 2025-12-29 17:23:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 17, 2018):

Re-opening to test @bsteinert's scenario.

@jeremystretch commented on GitHub (Dec 17, 2018): Re-opening to test @bsteinert's scenario.
adam commented 2025-12-29 17:23:33 +01:00
Author
Owner
Copy Link

@bsteinert commented on GitHub (Dec 20, 2018):

@jeremystretch i have changed the "device_lldp_neighbors.html" like in "40cb576" on my netbox install and can confirm it works perfect! thank you for the quick fix of this issue!

@bsteinert commented on GitHub (Dec 20, 2018): @jeremystretch i have changed the "device_lldp_neighbors.html" like in "40cb576" on my netbox install and can confirm it works perfect! thank you for the quick fix of this issue!
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: accepted 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#2198
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?