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

Quick search breaks available IPs search results #9087

New Issue
Closed
opened 2025-12-29 20:45:16 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:45:16 +01:00
Owner
Copy Link

Originally created by @charlespick on GitHub (Jan 14, 2024).

Originally assigned to: @jeremystretch on GitHub.

Deployment Type

Self-hosted

NetBox Version

3.7.0

Python Version

3.10

Steps to Reproduce

View prefix and use "quick search" to filter ip addresses

Expected Behavior

Available IPs should not change. I would argue that available IPs should not show up in quick search results at all.

Observed Behavior

The available IPs increases with the number of IP addresses filtered out. The IPs are however not actually available. Clicking on the available IPs goes onto provision an IP that is already assigned.
image

Originally created by @charlespick on GitHub (Jan 14, 2024). Originally assigned to: @jeremystretch on GitHub. ### Deployment Type Self-hosted ### NetBox Version 3.7.0 ### Python Version 3.10 ### Steps to Reproduce View prefix and use "quick search" to filter ip addresses ### Expected Behavior Available IPs should not change. I would argue that available IPs should not show up in quick search results at all. ### Observed Behavior The available IPs increases with the number of IP addresses filtered out. The IPs are however not actually available. Clicking on the available IPs goes onto provision an IP that is already assigned. ![image](https://github.com/netbox-community/netbox/assets/17918019/60269f99-dffe-4c65-a022-51a0289258c4)
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 20:45:16 +01:00
adam closed this issue 2025-12-29 20:45:17 +01:00
adam commented 2025-12-29 20:45:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 16, 2024):

Looks like a regression introduced in e4cb0c3cc2

@jeremystretch commented on GitHub (Jan 16, 2024): Looks like a regression introduced in e4cb0c3cc2738369c71484ff188a6a741c510351
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 severity: low status: accepted 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#9087
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?