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

Impossibility of getting info about interface object that's hanged on VM #2800

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

Originally created by @Dmitresso on GitHub (Aug 9, 2019).

Environment

  • Python version: 3.6
  • NetBox version: 2.6.1, two instances

Steps to Reproduce

  1. Send http request to get information about interface hanged on VM

Expected Behavior

Get information about interface hanged on VM

What happened instead?

NetBox responses
425{"detail":"Not found."}
(first three ciphers are random, can't see any logic)
I have two NetBox instances, tested on both (the same behavior).
1-st and 2-nd requests to interfaces that are hanged on devices, all's ok. 3-d, 4-th interfaces are hanged on Virtual Machines, here I get "detail":"Not found."
netbox bug via console
The same via browser:
netbox test instance interface on device request
netbox prod instance interface on device request
netbox test instance interface on vm request
netbox prod instance interface on vm request

Originally created by @Dmitresso on GitHub (Aug 9, 2019). ### Environment * Python version: 3.6 * NetBox version: 2.6.1, two instances ### Steps to Reproduce 1. Send http request to get information about interface hanged on VM ### Expected Behavior Get information about interface hanged on VM ### What happened instead? NetBox responses 425{"detail":"Not found."} (first three ciphers are random, can't see any logic) I have two NetBox instances, tested on both (the same behavior). 1-st and 2-nd requests to interfaces that are hanged on devices, all's ok. 3-d, 4-th interfaces are hanged on Virtual Machines, here I get "detail":"Not found." ![netbox bug via console](https://user-images.githubusercontent.com/15903451/62759570-de1b0f00-baab-11e9-9b8a-0c2a4e1bbd59.png) The same via browser: ![netbox test instance interface on device request](https://user-images.githubusercontent.com/15903451/62760011-21c24880-baad-11e9-8efc-f4ff6dc717ee.png) ![netbox prod instance interface on device request](https://user-images.githubusercontent.com/15903451/62760009-21c24880-baad-11e9-92c5-580cd9f7a74a.png) ![netbox test instance interface on vm request](https://user-images.githubusercontent.com/15903451/62760012-225adf00-baad-11e9-8de2-c5b869cb4fb9.png) ![netbox prod instance interface on vm request](https://user-images.githubusercontent.com/15903451/62760010-21c24880-baad-11e9-95d4-715afcf13468.png)
adam closed this issue 2025-12-29 18:22:18 +01:00
adam commented 2025-12-29 18:22:19 +01:00
Author
Owner
Copy Link

@phurrelmann commented on GitHub (Aug 9, 2019):

You should probably use the proper API endpoint für VMs: /api/virtualization/interfaces and not /api/dcim/interfaces

@phurrelmann commented on GitHub (Aug 9, 2019): You should probably use the proper API endpoint für VMs: /api/virtualization/interfaces and not /api/dcim/interfaces
adam commented 2025-12-29 18:22:19 +01:00
Author
Owner
Copy Link

@Dmitresso commented on GitHub (Aug 9, 2019):

You should probably use the proper API endpoint für VMs: /api/virtualization/interfaces and not /api/dcim/interfaces

Ok, I'have got the interface I need following by your advice, thanks.
But why all the interfaces I add for VM get link like "/dcim/interfaces/\d+"? I think to rename topic because that's really discourages and this is a main problem.

@Dmitresso commented on GitHub (Aug 9, 2019): > > > You should probably use the proper API endpoint für VMs: /api/virtualization/interfaces and not /api/dcim/interfaces Ok, I'have got the interface I need following by your advice, thanks. But why all the interfaces I add for VM get link like "/dcim/interfaces/\d+"? I think to rename topic because that's really discourages and this is a main problem.
adam commented 2025-12-29 18:22:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 9, 2019):

Thank you for your interest in NetBox. GitHub issues are intended for reporting reproducible bugs and requesting features, and must be submitted using one of the templates provided here. For general discussion, questions, or assistance with installation issues, please post to our mailing list instead.

@jeremystretch commented on GitHub (Aug 9, 2019): Thank you for your interest in NetBox. GitHub issues are intended for reporting reproducible bugs and requesting features, and must be submitted using one of the templates provided [here](https://github.com/digitalocean/netbox/issues/new/choose). For general discussion, questions, or assistance with installation issues, please post to our [mailing list](https://groups.google.com/forum/#!forum/netbox-discuss) instead.
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#2800
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?