New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add site specific vlans to bulk editing of interfaces #4523
Comments
I am not able to recreate this on https://master.netbox.dansheps.com/ Could you please test on there and then revise your steps. You need to include: Device:
Interface:
VLAN:
For both test cases. |
Well you are running 2.8.0 on there, could it be that it's the same issue as this? #4474 |
Possible but unlikely as it wouldn't work on your second case. You can attempt to upgrade to 2.8 and see if it still persists. |
Alright, so it isn't that there are no sites showing, it is that there are only global sites showing. Which right now is to be expected as bulk edit has no concept of being in a site (mainly because you can bulk edit across many devices). We can try changing this, but we would have to find a good balance. Do we only show site vlans when bulk editing devices in the same site? Do we allow bulk editing of any site a device is currently in and silently ignore invalid site vlan assignments? Do we throw an error? Do we attempt to map if the same VID's exist? A lot of options and each might be perfectly viable. |
@DanSheps any progress on this? |
I have gotten this working and chosen the following approach: If the site matches for all interfaces, the site-specific interfaces will display. If the site does not match, only global vlans will display. I think this is a nice balanced approach which does not require a lot of further coding to be workable (existing validation logic is still valid). What we get is this: Same Device: Shows site vlans |
Environment
Attempt to bulk edit interfaces and add vlans;
If i edit the interfaces in the same way but select the interfaces from the device page under /dcim/devices it works correctly and shows the vlans.
Steps to Reproduce
Expected Behavior
VLAN are shown for the tenant
Observed Behavior
No results are found and global vlans are shown when only tenant ones should be
The text was updated successfully, but these errors were encountered: