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

Creation of sub interface of existing device after upgrade lists sub interface above parent interface. #3813

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

Originally created by @tigger4life on GitHub (Jun 25, 2020).

Environment

  • Python version: 2.7.5 and 3.6.8
  • NetBox version: 2.8.6-ldap

Steps to Reproduce

  1. Add components | Interfaces to an existing device
  2. Create sub virtual interface (like ge-0/0/1.2). No other changes needed
  3. Create interface
    This only happens when adding an interface to an existing device. Upgraded from 2.8.4-ldap

Expected Behavior

I expected the sub interface to show up under it's parent ge-0/0/1.

Observed Behavior

The sub interface was listed above parent interface not below.

Originally created by @tigger4life on GitHub (Jun 25, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. 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, and that any plugins have been disabled. --> ### Environment * Python version: 2.7.5 and 3.6.8 * NetBox version: 2.8.6-ldap <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. 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 client library such as pynetbox. --> ### Steps to Reproduce 1. Add components | Interfaces to an existing device 2. Create sub virtual interface (like ge-0/0/1.2). No other changes needed 3. Create interface This only happens when adding an interface to an existing device. Upgraded from 2.8.4-ldap <!-- What did you expect to happen? --> ### Expected Behavior I expected the sub interface to show up under it's parent ge-0/0/1. <!-- What happened instead? --> ### Observed Behavior The sub interface was listed above parent interface not below.
adam closed this issue 2025-12-29 18:31:19 +01:00
adam commented 2025-12-29 18:31:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 25, 2020):

Python version: 2.7.5 and 3.6.8

NetBox requires Python 3.6 or later.

NetBox version: 2.8.6-ldap

What is the significance of -ldap? This is not an official designation.

Finally, please add more detail to your ticket. You'll need to include the complete list of interfaces you've created, both in the order they appear and the order you expected them to appear.

@jeremystretch commented on GitHub (Jun 25, 2020): > Python version: 2.7.5 and 3.6.8 NetBox requires Python 3.6 or later. > NetBox version: 2.8.6-ldap What is the significance of `-ldap`? This is not an official designation. Finally, please add more detail to your ticket. You'll need to include the complete list of interfaces you've created, both in the order they appear and the order you expected them to appear.
adam commented 2025-12-29 18:31:20 +01:00
Author
Owner
Copy Link

@tigger4life commented on GitHub (Jun 25, 2020):

Apologies this is my first time reporting anything. My Cent VM has both python versions so I listed them both but NetBox is running with 3.6.8.

The -ldap is the docker version I'm using. I wanted to make sure I gave you what I was running. I didn't know if that mattered so I included it.

As far as the interfaces, from a device that was already created prior to the update, I had the following interfaces in order of appearance on the device:
xe-0/0/17
xe-0/0/17.2
xe-0/0/17.3
xe-0/0/17.4
xe-0/0/17.5
xe-0/0/17.6
xe-0/0/17.7

After the update, I create 2 new interfaces and the appear in order as follows:
xe-0/0/17.8
xe-0/0/17.9
xe-0/0/17
xe-0/0/17.2
xe-0/0/17.3
xe-0/0/17.4
xe-0/0/17.5
xe-0/0/17.6
xe-0/0/17.7

I expected the 2 new interfaces to fall in line along with the rest. I hope this helps!

@tigger4life commented on GitHub (Jun 25, 2020): Apologies this is my first time reporting anything. My Cent VM has both python versions so I listed them both but NetBox is running with 3.6.8. The -ldap is the docker version I'm using. I wanted to make sure I gave you what I was running. I didn't know if that mattered so I included it. As far as the interfaces, from a device that was already created prior to the update, I had the following interfaces in order of appearance on the device: xe-0/0/17 xe-0/0/17.2 xe-0/0/17.3 xe-0/0/17.4 xe-0/0/17.5 xe-0/0/17.6 xe-0/0/17.7 After the update, I create 2 new interfaces and the appear in order as follows: xe-0/0/17.8 xe-0/0/17.9 xe-0/0/17 xe-0/0/17.2 xe-0/0/17.3 xe-0/0/17.4 xe-0/0/17.5 xe-0/0/17.6 xe-0/0/17.7 I expected the 2 new interfaces to fall in line along with the rest. I hope this helps!
adam commented 2025-12-29 18:31:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 26, 2020):

The -ldap is the docker version I'm using

Please note that we only accept bug reports which are reproducible on a current stable release of the core NetBox product.

I am unable to replicate this behavior on v2.8.6. I'll also note that we have tests in place to ensure that this ordering logic is working.

If you can identify a specific series of discrete actions by which this condition can be replicated on a current official release, I'm happy to reopen the issue.

@jeremystretch commented on GitHub (Jun 26, 2020): > The -ldap is the docker version I'm using Please note that we only accept bug reports which are reproducible on a current stable release of the core NetBox product. I am unable to replicate this behavior on v2.8.6. I'll also note that we have [tests in place](https://github.com/netbox-community/netbox/blob/develop/netbox/dcim/tests/test_natural_ordering.py#L92) to ensure that this ordering logic is working. If you can identify a specific series of discrete actions by which this condition can be replicated on a current official release, I'm happy to reopen the 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
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#3813
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?