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

IPAM page shows all services with IP's, not services associated with the IP. #17163

Closed
ThomasADavis opened this issue Aug 14, 2024 · 1 comment
Assignees
Labels
beta Concerns a bug/feature in a beta release 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

@ThomasADavis
Copy link

Deployment Type

Self-hosted

NetBox Version

netbox-687679c4bb-hrt96 NetBox Community v4.1.0-beta1

Python Version

3.12

Steps to Reproduce

  1. create two devices with two different IP's.
  2. create on each device, two different services.
  3. check the IP page, and note that all services are listed, not just the one associated with the IP.

Expected Behavior

Only services associated with the IP should show up.

Observed Behavior

All services show up under the IP address.

same db copied between two instances shows this with the v4.07:
Screenshot_2024-08-14_11-46-00

and this with the v4.1beta1 instance:

Screenshot_2024-08-14_11-47-07

I've stripped the netbox v4.1b1 instances of all plugins and check to make sure this still occurs.

@ThomasADavis ThomasADavis added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Aug 14, 2024
@arthanson arthanson removed their assignment Aug 15, 2024
@arthanson arthanson added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation beta Concerns a bug/feature in a beta release 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 Aug 15, 2024
@arthanson
Copy link
Collaborator

If you just add the service and don't specifically associate it with the IP it will still show, tested on develop and it does not show.

@arthanson arthanson self-assigned this Aug 15, 2024
@arthanson arthanson added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Aug 15, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
beta Concerns a bug/feature in a beta release 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

No branches or pull requests

3 participants