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/interfaces missing vm link in api #2562

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

Originally created by @ossark on GitHub (Apr 29, 2019).

Environment

  • NetBox version: 2.5.8

Expected Behavior

I expect to have a link from an interface to its VM exposed in the api, similar to how the link to device is done.

Observed Behavior

No explicit link from interface to virtual machine is exposed.

Originally created by @ossark on GitHub (Apr 29, 2019). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss 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. --> ### Environment * NetBox version: 2.5.8 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). 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 wrapper like pynetbox. --> <!-- What did you expect to happen? --> ### Expected Behavior I expect to have a link from an interface to its VM exposed in the api, similar to how the link to device is done. <!-- What happened instead? --> ### Observed Behavior No explicit link from interface to virtual machine is exposed.
adam closed this issue 2025-12-29 18:19:58 +01:00
adam commented 2025-12-29 18:19:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 29, 2019):

There is a link:

{
    "id": 162989,
    "virtual_machine": {
        "id": 1,
        "url": "https://netbox.internal.digitalocean.com/api/virtualization/virtual-machines/1/",
        "name": "net-util01.nyc3"
    },
    "name": "eth0",
    ...
}

Make sure you are using the VM interfaces endpoint at /api/virtualization/interfaces, not the DCIM endpoint.

@jeremystretch commented on GitHub (Apr 29, 2019): There is a link: ``` { "id": 162989, "virtual_machine": { "id": 1, "url": "https://netbox.internal.digitalocean.com/api/virtualization/virtual-machines/1/", "name": "net-util01.nyc3" }, "name": "eth0", ... } ``` Make sure you are using the VM interfaces endpoint at `/api/virtualization/interfaces`, not the DCIM endpoint.
adam commented 2025-12-29 18:19:59 +01:00
Author
Owner
Copy Link

@ossark commented on GitHub (Apr 29, 2019):

Thanks. This works.
Although, clicking on the interface from the VM (in the web gui) sends me to "dcim/interfaces"

Just out of interest, why separate interfaces on virtual machines from interfaces on devices?

@ossark commented on GitHub (Apr 29, 2019): Thanks. This works. Although, clicking on the interface from the VM (in the web gui) sends me to "dcim/interfaces" Just out of interest, why separate interfaces on virtual machines from interfaces on devices?
adam commented 2025-12-29 18:19:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 29, 2019):

The two endpoints utilize slightly different serializers for the same model: The DCIM serializer treats device as a required field, and the other uses virtual_machine.

@jeremystretch commented on GitHub (Apr 29, 2019): The two endpoints utilize slightly different serializers for the same model: The DCIM serializer treats `device` as a required field, and the other uses `virtual_machine`.
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#2562
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?