starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

role field cannot be null when changing ip address via API #1906

New Issue
Closed
opened 2025-12-29 17:20:16 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:20:16 +01:00
Owner
Copy Link

Originally created by @orgito on GitHub (Aug 7, 2018).

Environment

  • Python version: 3.4.8
  • NetBox version: 2.4.0

Steps to Reproduce

Change an IP address with the role field as null.

Expected Behavior

Should save the IP address

Observed Behavior

Fails with the errror:

{"role":["This field may not be null."]}

Adding allow_null=True to f59682a7c9/netbox/ipam/api/serializers.py (L261) solves the issue

Originally created by @orgito on GitHub (Aug 7, 2018). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.4.8 * NetBox version: 2.4.0 <!-- Describe in detail the steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). --> ### Steps to Reproduce Change an IP address with the role field as null. <!-- What did you expect to happen? --> ### Expected Behavior Should save the IP address <!-- What happened instead? --> ### Observed Behavior Fails with the errror: ```python {"role":["This field may not be null."]} ``` Adding `allow_null=True` to https://github.com/digitalocean/netbox/blob/f59682a7c955baa6b336ebe927d69c26f725ad67/netbox/ipam/api/serializers.py#L261 solves the issue
adam added the type: bugstatus: accepted labels 2025-12-29 17:20:16 +01:00
adam closed this issue 2025-12-29 17:20:16 +01:00
adam commented 2025-12-29 17:20:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 7, 2018):

I've found this same issue in several places where ChoiceField is used on a nullable field.

@jeremystretch commented on GitHub (Aug 7, 2018): I've found this same issue in several places where ChoiceField is used on a nullable field.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1906
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?