Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
AliMickey opened this issue Feb 4, 2025 · 0 comments
Open
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@AliMickey
Copy link

AliMickey commented 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 :( .

@AliMickey AliMickey added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Feb 4, 2025
@DanSheps DanSheps added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants