Incorrect prefix status shown when quick search from Aggregates -> Prefixes view #11182

Closed
opened 2025-12-29 21:41:37 +01:00 by adam · 3 comments
Owner

Originally created by @Toosaman on GitHub (May 15, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.3.1

Python Version

3.11

Steps to Reproduce

  1. Click on "Aggregates" in left menu.
  2. Choose aggregate network.
  3. Click on "Prefixes" tab of chosen aggregate.
  4. Enter search keyword (ex. part of some prefix) in "quick search" field.

Expected Behavior

Keyword matched prefixes and its actual status shown

Observed Behavior

Unmatched prefixes shown with incorrect status ("Available" instead of "Active")

Image Image
Originally created by @Toosaman on GitHub (May 15, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.3.1 ### Python Version 3.11 ### Steps to Reproduce 1. Click on "Aggregates" in left menu. 2. Choose aggregate network. 3. Click on "Prefixes" tab of chosen aggregate. 4. Enter search keyword (ex. part of some prefix) in "quick search" field. ### Expected Behavior Keyword matched prefixes and its actual status shown ### Observed Behavior Unmatched prefixes shown with incorrect status ("Available" instead of "Active") <img width="231" alt="Image" src="https://github.com/user-attachments/assets/46b6e3a6-cb86-49de-a308-aec46dcecd18" /> <img width="245" alt="Image" src="https://github.com/user-attachments/assets/9962f3ed-97c3-4890-8fae-3068fa371284" />
adam added the type: bugstatus: needs ownerpending closureseverity: low labels 2025-12-29 21:41:37 +01:00
adam closed this issue 2025-12-29 21:41:37 +01:00
Author
Owner

@GoepiGB commented on GitHub (Jun 12, 2025):

The same happens when you filter the child prefixes of a prefix via quick search.

@GoepiGB commented on GitHub (Jun 12, 2025): The same happens when you filter the child prefixes of a prefix via quick search.
Author
Owner

@github-actions[bot] commented on GitHub (Sep 11, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Sep 11, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Oct 12, 2025):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Oct 12, 2025): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11182