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

API returns duplicate entries for IPs with VIP role #8213

New Issue
Closed
opened 2025-12-29 20:33:52 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:33:52 +01:00
Owner
Copy Link

Originally created by @reshippie on GitHub (Jun 19, 2023).

NetBox version

v3.5.3 - netbox-docker

Python version

3.10

Steps to Reproduce

  1. Create at least 14 IPs with the VIP role, with the same address and different dns_names
  2. Using the REST API, api/ipam/ip-addresses/ fetch all of the IPs in Netbox
  3. Print out the ID and dns_name fields for all of the entries returned with that IP address.

Expected Behavior

Fetching all IP addresses from Netbox should return all of the entries stored, with no duplicate entries.

Observed Behavior

  1. There will be at least entry, out of the 14, that is missing and 1 entry that is repeated.
  2. There will be the correct number of entries returned, just not the correct number of unique entries.
Originally created by @reshippie on GitHub (Jun 19, 2023). ### NetBox version v3.5.3 - netbox-docker ### Python version 3.10 ### Steps to Reproduce 1. Create at least 14 IPs with the VIP role, with the same address and different dns_names 2. Using the REST API, `api/ipam/ip-addresses/` fetch all of the IPs in Netbox 3. Print out the ID and dns_name fields for all of the entries returned with that IP address. ### Expected Behavior Fetching all IP addresses from Netbox should return all of the entries stored, with no duplicate entries. ### Observed Behavior 1. There will be at least entry, out of the 14, that is missing and 1 entry that is repeated. 2. There will be the correct number of entries returned, just not the correct number of unique entries.
adam added the type: bug label 2025-12-29 20:33:52 +01:00
adam closed this issue 2025-12-29 20:33:52 +01:00
adam commented 2025-12-29 20:33:52 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Jun 19, 2023):

Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v3.5.3. Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.

@kkthxbye-code commented on GitHub (Jun 19, 2023): Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v3.5.3. Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.
adam commented 2025-12-29 20:33:52 +01:00
Author
Owner
Copy Link

@reshippie commented on GitHub (Jun 20, 2023):

We're definitely on the newest release.
This is our production installation, it has 21K entries in IPAM.
We've upgraded from some iteration of version 2 up through the most recent release.
We've tried dumping the Postgresql database and restoring it to another instance but we're still seeing the same behavior.

@reshippie commented on GitHub (Jun 20, 2023): We're definitely on the newest release. This is our production installation, it has 21K entries in IPAM. We've upgraded from some iteration of version 2 up through the most recent release. We've tried dumping the Postgresql database and restoring it to another instance but we're still seeing the same behavior.
adam commented 2025-12-29 20:33:52 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Jul 4, 2023):

I'll close this out as there are no proper replication steps. If you do manage to replicate it on a clean netbox install, please make a post and I'll re-open it.

@kkthxbye-code commented on GitHub (Jul 4, 2023): I'll close this out as there are no proper replication steps. If you do manage to replicate it on a clean netbox install, please make a post and I'll re-open it.
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 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#8213
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?