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

Wrong filter used when clicking number of IP addresses in VM Interface table #15059

Closed
Faabvk opened this issue Feb 6, 2024 · 1 comment · Fixed by #15140
Closed

Wrong filter used when clicking number of IP addresses in VM Interface table #15059

Faabvk opened this issue Feb 6, 2024 · 1 comment · Fixed by #15140
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@Faabvk
Copy link

Faabvk commented Feb 6, 2024

Deployment Type

Self-hosted

NetBox Version

v3.7.2

Python Version

3.8

Steps to Reproduce

Make sure you use a Virtual Machine, that has an interface with 3 or more IP addresses assigned to it.

  1. Go to a Virtual Machine page
  2. Go to interfaces tab
  3. There should be an interface with 3 or more IP addresses
    a. Instead of it showing the individual IP addresses in the table, it will show you the number of IP addresses. (Clickable link)
  4. Click link with number of IP addresses

Expected Behavior

It should link you to a filtered page that shows the IP addresses associated with the VM Interface

Observed Behavior

It links you to the right page, but as observed in the URL, it uses the wrong filter and attempts to filter for "regular" physical interfaces, so it gives you either an empty set of results, or the wrong results.

Example URL: https://netbox.xxxxxxx/ipam/ip-addresses/?interface_id=195

@Faabvk Faabvk added the type: bug A confirmed report of unexpected behavior in the application label Feb 6, 2024
@Faabvk

This comment was marked as off-topic.

@jeremystretch jeremystretch self-assigned this Feb 13, 2024
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available labels Feb 13, 2024
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: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants