When creating a new prefix and selecting a site VLANs are not filtered #8592

Closed
opened 2025-12-29 20:38:34 +01:00 by adam · 2 comments
Owner

Originally created by @patrickfnielsen on GitHub (Sep 8, 2023).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.6.1

Python version

3.11

Steps to Reproduce

  • Create two new sites with the following names, and mark them active: site1 and site2
  • On both sites create the following VLANs:
    • VID: 10, Name: Test
    • VID: 20, Name: Test2
  • Create a new prefix
    • Any prefix will do
    • Select site1
    • Notice that when selecting VLAN's you can select VLAN's from both sites

Expected Behavior

Before the new selector widget was added VLANs would be filtered when you selected a site, that is not the case anymore. When you select a site all VLANs are still shown, and you have to use the new selector widget to select the site once again.

Observed Behavior

VLANs are not filtered, instead all VLANs are shown

Originally created by @patrickfnielsen on GitHub (Sep 8, 2023). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.6.1 ### Python version 3.11 ### Steps to Reproduce - Create two new sites with the following names, and mark them active: site1 and site2 - On both sites create the following VLANs: - VID: 10, Name: Test - VID: 20, Name: Test2 - Create a new prefix - Any prefix will do - Select site1 - Notice that when selecting VLAN's you can select VLAN's from both sites ### Expected Behavior Before the new selector widget was added VLANs would be filtered when you selected a site, that is not the case anymore. When you select a site all VLANs are still shown, and you have to use the new selector widget to select the site once again. ### Observed Behavior VLANs are not filtered, instead all VLANs are shown
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 20:38:34 +01:00
adam closed this issue 2025-12-29 20:38:34 +01:00
Author
Owner

@jeremystretch commented on GitHub (Sep 8, 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 (Sep 8, 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.
Author
Owner

@patrickfnielsen commented on GitHub (Sep 11, 2023):

I have updated the issue.

@patrickfnielsen commented on GitHub (Sep 11, 2023): I have updated the issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8592