Cable API endpoint refuses a null length_unit #2434

Closed
opened 2025-12-29 17:26:04 +01:00 by adam · 0 comments
Owner

Originally created by @aruhier on GitHub (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.']}

Originally created by @aruhier on GitHub (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 did you expect to happen? --> 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.']}`
adam added the type: bugstatus: accepted labels 2025-12-29 17:26:04 +01:00
adam closed this issue 2025-12-29 17:26:04 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2434