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

Assigning Virtual interface as Parent interface on Device is not possible #9092

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

Originally created by @fikusir on GitHub (Jan 16, 2024).

Deployment Type

Self-hosted

NetBox Version

v3.7.0

Python Version

3.10

Steps to Reproduce

  1. Create Virtual interface on a device with name Uplink
  2. Create 1000BASE-T interface on a device LAN1
  3. Set on the interface LAN1 "Parent interface" to Uplink

Expected Behavior

That the system will allow me to assign the Virtual interface

Observed Behavior

When editing 1000BASE-T field "Parent interface" where I try to put the Virtual interface created in step nr.1 system tell me "Only virtual interfaces may be assigned to a parent interface.". But in this case it is really Virtual interface.

Originally created by @fikusir on GitHub (Jan 16, 2024). ### Deployment Type Self-hosted ### NetBox Version v3.7.0 ### Python Version 3.10 ### Steps to Reproduce 1. Create Virtual interface on a device with name **Uplink** 2. Create 1000BASE-T interface on a device **LAN1** 3. Set on the interface **LAN1** "Parent interface" to **Uplink** ### Expected Behavior That the system will allow me to assign the Virtual interface ### Observed Behavior When editing 1000BASE-T field "Parent interface" where I try to put the Virtual interface created in step nr.1 system tell me "Only virtual interfaces may be assigned to a parent interface.". But in this case it is really Virtual interface.
adam added the type: bug label 2025-12-29 20:45:20 +01:00
adam closed this issue 2025-12-29 20:45:20 +01:00
adam commented 2025-12-29 20:45:21 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jan 16, 2024):

  • Create Virtual interface on a device with name Uplink
  • Create 1000BASE-T interface on a device LAN1
  • Set on the interface LAN1 "Parent interface" to Uplink

I don't think this model is valid. Could you explain more about what you are trying to do here? This is an unsupported parent/child relationship and there is a good reason for that, in that this typically isn't possible in the real world.

When editing 1000BASE-T field "Parent interface" where I try to put the Virtual interface created in step nr.1 system tell me "Only virtual interfaces may be assigned to a parent interface.". But in this case it is really Virtual interface.

Supported parent/children relationships:

  • Physical (parent) to physical (child)
  • Physical (parent) to virtual (child)
  • Virtual (parent) to virtual (child)

Unsupported:

  • Virtual (parent) to physical (child)

Because of this, I think this should be opened as an FR with a proper use case. This currently is not a bug and is intended behaviour.

@DanSheps commented on GitHub (Jan 16, 2024): > * Create Virtual interface on a device with name **Uplink** > * Create 1000BASE-T interface on a device **LAN1** > * Set on the interface **LAN1** "Parent interface" to **Uplink** I don't think this model is valid. Could you explain more about what you are trying to do here? This is an unsupported parent/child relationship and there is a good reason for that, in that this typically isn't possible in the real world. > When editing 1000BASE-T field "Parent interface" where I try to put the Virtual interface created in step nr.1 system tell me "Only virtual interfaces may be assigned to a parent interface.". But in this case it is really Virtual interface. Supported parent/children relationships: * Physical (parent) to physical (child) * Physical (parent) to virtual (child) * Virtual (parent) to virtual (child) Unsupported: * Virtual (parent) to physical (child) Because of this, I think this should be opened as an FR with a proper use case. This currently is not a bug and is intended behaviour.
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 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#9092
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?