You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VLAN group configured with specified parameters. Code 201 returned with return data as in the API definition.
Observed Behavior
API throws code 500 'Error: Internal Server Error'
In the response body I can see:
<pre><strong><class 'AttributeError'></strong><br/>
'UniqueTogetherValidator' object has no attribute 'set_context'</pre>
Additional information
When reference to site ID (8) is ommited the VLAN group is created correctly.
After that, when trying to do a PATCH call to add the site to the just created vlan-group, the same error is thrown.
The same thing happens when I'm trying to create a VLAN (with site and/or group).
However, there seems to be no issues in the DCIM module as I was able to create a LAG (ref. to device id), then PATCH interface to add it to the LAG (ref. to LAG id) and finally create an IP and assign it to the interface.
Same behaviour is observed using different tools for making API requests.
The text was updated successfully, but these errors were encountered:
Environment
Steps to Reproduce
PLUGINS
setting inconfiguration.py
.Site 'Development' has been predefined:
No VLAN-groups had been defined.
Expected Behavior
VLAN group configured with specified parameters. Code 201 returned with return data as in the API definition.
Observed Behavior
API throws code 500 'Error: Internal Server Error'
In the response body I can see:
Additional information
When reference to site ID (8) is ommited the VLAN group is created correctly.
After that, when trying to do a PATCH call to add the site to the just created vlan-group, the same error is thrown.
The same thing happens when I'm trying to create a VLAN (with site and/or group).
However, there seems to be no issues in the DCIM module as I was able to create a LAG (ref. to device id), then PATCH interface to add it to the LAG (ref. to LAG id) and finally create an IP and assign it to the interface.
Same behaviour is observed using different tools for making API requests.
The text was updated successfully, but these errors were encountered: