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

InterfaceTemplate ordering does not match the order on an actual device #10731

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

Originally created by @AliMickey on GitHub (Feb 4, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.2.2.

Python Version

3.12

Steps to Reproduce

  1. Create interfaces on a device type template:
Ethernet1
Ethernet2
Ethernet3
Ethernet4
Ethernet5/1
Ethernet5/2
Ethernet5/3
Ethernet5/4
  1. Create a new device using that template.
  2. Observe that the interface order of the interfaces does not match in default ordering.
Ethernet5/1
Ethernet5/2
Ethernet5/3
Ethernet5/4
Ethernet1
Ethernet2
Ethernet3
Ethernet4

Expected Behavior

The created device should match the template, as it is a template.

Observed Behavior

The default ordering on a device's interface table does not represent the template order.

As a side note, I know this sort of issue has been raised multiple times previously however I had hoped there was an improvement in the recent v4 release that notes collation based ordering.

Whatever order the InterfaceTemplate uses is better, if i add a new interface as a test "Ethernet1/1" it correctly slots in between the existing interfaces (in the InterfaceTemplate table):

Ethernet1
Ethernet1/1
Ethernet2
Ethernet3
Ethernet4

I have cleared my interface sorting defaults, made sure multiple columns were not selected for sorting, no luck :( .

Originally created by @AliMickey on GitHub (Feb 4, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.2.2. ### Python Version 3.12 ### Steps to Reproduce 1. Create interfaces on a device type template: ``` Ethernet1 Ethernet2 Ethernet3 Ethernet4 Ethernet5/1 Ethernet5/2 Ethernet5/3 Ethernet5/4 ``` 2. Create a new device using that template. 3. Observe that the interface order of the interfaces does not match in default ordering. ``` Ethernet5/1 Ethernet5/2 Ethernet5/3 Ethernet5/4 Ethernet1 Ethernet2 Ethernet3 Ethernet4 ``` ### Expected Behavior The created device should match the template, as it is a template. ### Observed Behavior The default ordering on a device's interface table does not represent the template order. As a side note, I know this sort of issue has been raised multiple times previously however I had hoped there was an improvement in the recent v4 release that notes collation based ordering. Whatever order the InterfaceTemplate uses is better, if i add a new interface as a test "Ethernet1/1" it correctly slots in between the existing interfaces (in the InterfaceTemplate table): ``` Ethernet1 Ethernet1/1 Ethernet2 Ethernet3 Ethernet4 ``` I have cleared my interface sorting defaults, made sure multiple columns were not selected for sorting, no luck :( .
adam added the type: bugstatus: needs ownerpending closureseverity: low labels 2025-12-29 21:35:18 +01:00
adam closed this issue 2025-12-29 21:35:18 +01:00
adam commented 2025-12-29 21:35:19 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 7, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (May 7, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
adam commented 2025-12-29 21:35:19 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 6, 2025):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jun 6, 2025): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure severity: low status: needs owner 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#10731
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?