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

Bulk edit virtual machine parent interface #5487

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

Originally created by @MrDiba on GitHub (Oct 7, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.0.6

Python version

3.9

Steps to Reproduce

  1. Create a virtual machine with interfaces named eth0 through eth3
  2. Select the "Interfaces" tab under the VM view
  3. Select eth0 to eth2 and click Edit
  4. Expand the "Parent" field dropdown

Expected Behavior

I would expect that when I want to change the parent of a few interfaces on a specific virtual machine, that I would only have the option to select one of the interfaces of that virtual machine.

Observed Behavior

I see all of the interfaces existing on every virtual machine without knowing to what virtual machine they belong.

Originally created by @MrDiba on GitHub (Oct 7, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.0.6 ### Python version 3.9 ### Steps to Reproduce 1. Create a virtual machine with interfaces named `eth0` through `eth3` 2. Select the "Interfaces" tab under the VM view 3. Select eth0 to eth2 and click Edit 4. Expand the "Parent" field dropdown ### Expected Behavior I would expect that when I want to change the parent of a few interfaces on a specific virtual machine, that I would only have the option to select one of the interfaces of that virtual machine. ### Observed Behavior I see all of the interfaces existing on every virtual machine without knowing to what virtual machine they belong.
adam added the type: bugstatus: accepted labels 2025-12-29 19:28:35 +01:00
adam closed this issue 2025-12-29 19:28:36 +01:00
adam commented 2025-12-29 19:28:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 7, 2021):

Per the bug report template:

Additionally, do not rely on the demo instance for reproducing suspected bugs, as its data is prone to modification or deletion at any time.

Please rewrite your bug report to not rely on any data in the demo instance. Thanks.

Edit: I've updated it for you.

@jeremystretch commented on GitHub (Oct 7, 2021): Per the bug report template: > Additionally, **do not rely on the demo instance** for reproducing suspected bugs, as its data is prone to modification or deletion at any time. Please rewrite your bug report to not rely on any data in the demo instance. Thanks. Edit: I've updated it for you.
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#5487
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?