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

API ipam.ip-address.filter and multiple parent prefixes unreliable #18507

Open
gurubert opened this issue Jan 28, 2025 · 1 comment
Open

API ipam.ip-address.filter and multiple parent prefixes unreliable #18507

gurubert opened this issue Jan 28, 2025 · 1 comment
Labels
status: revisions needed This issue requires additional information to be actionable type: bug A confirmed report of unexpected behavior in the application

Comments

@gurubert
Copy link

Deployment Type

Self-hosted

NetBox Version

v4.2.2

Python Version

3.11

Steps to Reproduce

A Python3 client script that uses the pynetbox REST API client implementation fetches IP addresses from Netbox via the API call netbox.ipam.ip_addresses.filter(parent = prefixes) where prefixes is a list of IP networks as strings.

Expected Behavior

Every call of that script returns the expected number of IP addresses.

Observed Behavior

Sometimes, unfortunately only randomly, some IP addresses (a couple of dozen out of nearly 5000) are missing.

netbox.ipam.ip_addresses.all() reliably returns all IPs every time.

netbox.ipam.ip_addresses.filter(parent = prefix) with only one prefix at a time also seems to reliably return the requested IPs.

@gurubert gurubert added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Jan 28, 2025
@bctiemann
Copy link
Contributor

@gurubert Can this be reproduced using the demo data in https://github.com/netbox-community/netbox-demo-data ?

Or can you develop a reproducible case using a minimal data set?

@bctiemann bctiemann added status: revisions needed This issue requires additional information to be actionable and removed status: needs triage This issue is awaiting triage by a maintainer labels Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: revisions needed This issue requires additional information to be actionable type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants