InterfaceModeChoices.MODE_TAGGED not working in 4.0.5 #16537
Unanswered
balpoint
asked this question in
Help Wanted!
Replies: 1 comment 1 reply
-
This is not a bug, there is nothing wrong with the Interface.mode setting in the UI, API or python API. This appears to be a problem with your script. As such, I have converted this to a discussion. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Deployment Type
Self-hosted
NetBox Version
v4.0.5
Python Version
3.10
Steps to Reproduce
Hi i have a script within Netbox and one of the things i do with the script is let my team fill out a form to configure specific interface parameters. One of these paramaters is interface mode, i do that as followed (cutdown version for lenght and clarity purposes):
Downgrading Netbox from 4.0.5 to 4.0.2 and everything works as it always has, cannot find any change related to this behavior.
Expected Behavior
The expected behavior is that 802.1Q Mode for the selected interface changes to tagged, for access this works fine.
Observed Behavior
The observed behavior is that whenever tagged is selected the script completes succesful but no change is made on the selected interface. No errors, even in debug mode there is no indication that anything is wrong, it simply does not do anything.
Downgrading Netbox from 4.0.5 to 4.0.2 and everything works as it always has, cannot find any change related to this behavior.
Beta Was this translation helpful? Give feedback.
All reactions