starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Global search on IP address with mask not giving results #8318

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

Originally created by @aodix on GitHub (Jul 10, 2023).

NetBox version

3.5.4

Python version

3.8

Steps to Reproduce

  1. Create IP with subnet (ex: 10.0.0.105/32)
  2. use search function with exact match or Partial match to find the IP
    image

Expected Behavior

find the ip address when available in netbox
image

Observed Behavior

No results found when searching
image

Originally created by @aodix on GitHub (Jul 10, 2023). ### NetBox version 3.5.4 ### Python version 3.8 ### Steps to Reproduce 1. Create IP with subnet (ex: 10.0.0.105/32) 2. use search function with exact match or Partial match to find the IP ![image](https://github.com/netbox-community/netbox/assets/20492819/e5befecf-d410-4988-b050-3ae75066881a) ### Expected Behavior find the ip address when available in netbox ![image](https://github.com/netbox-community/netbox/assets/20492819/b3bc148b-8e78-4d04-ac3e-aa65a695c8fd) ### Observed Behavior No results found when searching ![image](https://github.com/netbox-community/netbox/assets/20492819/adf111ef-d14a-4d1f-9fed-f4b50ba6de8b)
adam closed this issue 2025-12-29 20:35:17 +01:00
adam commented 2025-12-29 20:35:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 10, 2023):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch commented on GitHub (Jul 10, 2023): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
adam commented 2025-12-29 20:35:18 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Jul 11, 2023):

Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v3.5.6. 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.

@abhi1693 commented on GitHub (Jul 11, 2023): Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v3.5.6. 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:35:18 +01:00
Author
Owner
Copy Link

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

Closing as there has been no response. The likely culprit would be the index haven been cleared but not regenerated. This can be fixed by running the manage.py reindex command.

@kkthxbye-code commented on GitHub (Jul 23, 2023): Closing as there has been no response. The likely culprit would be the index haven been cleared but not regenerated. This can be fixed by running the `manage.py reindex` command.
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
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#8318
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?