-
Notifications
You must be signed in to change notification settings - Fork 263
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
Device Rackposition not changeable #81
Comments
Confirmed! Thanks for the bug report. |
https://github.com/nautobot/nautobot/blob/develop/nautobot/dcim/api/serializers.py#L346
|
We should also add a regression test for this. Seems to me more detailed filter testing should have caught this. |
Turns out it's not a filter but a query serializer that is being used as if it were a filter by |
This particular case is unique because it's a "query serializer" used to parse the query params for the `RackViewSet.elevation` method which was previously untested in this waty. - Swapped `nautobot.dcim.api.serializers.RackElevationDetailFilterSerializer.exclude` from `IntegerField` to `UUIDField` - Added a new test `nautobot.dcim.tests.test_api.RackTest.test_filter_rack_elevation` - Also revised validation of this serializer to raise an exception if invalid instead of returning a `Response` with status code 400. Functionally equivalent, but operationally it's more correct to let the serializer raise an exception. - Made the same fixes in `nautobot.ipam.api.views` and `nautobot.extras.api.views`
Fix #81 - Device Rack Position now changeable
Thanks @mkrsn ! :) |
Thanks for fixing / Nautobot! :) |
Environment
Steps to Reproduce
Expected Behavior
When opening the List it should display the Units of the assigned Rack.
Observed Behavior
It just shows: "The results could not be loaded"
It is only possible to assigne a Device to a Rack position while creating it. After the Device was created it's not possible to edit the position anymore. I've cross checked it with https://demo.nautobot.com/ - same Behavior.
The text was updated successfully, but these errors were encountered: