Skip to content
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

Cable API endpoint refuses a null length_unit #2966

Closed
aruhier opened this issue Mar 5, 2019 · 0 comments · Fixed by #2967
Closed

Cable API endpoint refuses a null length_unit #2966

aruhier opened this issue Mar 5, 2019 · 0 comments · Fixed by #2967
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@aruhier
Copy link
Contributor

aruhier commented Mar 5, 2019

Environment

  • Python version: 3.6.7
  • NetBox version: 2.5.7

Steps to Reproduce

  1. Get a cable with no length/length_unit (None for both) through the API
  2. PUT the exact cable data you received

What should happen: Nothing, the cable should be updated with the same data it had before.

What happens: 400 error, {'length_unit': ['This field may not be null.']}

@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application status: accepted This issue has been accepted for implementation labels Mar 5, 2019
jeremystretch added a commit that referenced this issue Mar 5, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants