Skip to content

POST dcim_interfaces_create via API - rf_channel: "This field may not be blank." #8465

@Sebas1337

Description

@Sebas1337

NetBox version

v3.1.6

Python version

3.8? (Using the container: netboxcommunity/netbox:v3.1.6-ldap-1.5.1)

Steps to Reproduce

When trying to use the dcim_create_interface trough the API I get an error about the field rf_channel. It says it cannot be blank. The interface I am trying to create is not even a wireless interface. When I try to fill in a dummy rf_channel it complains it is not needed. Tested in version 3.1.6 and 3.1.0.

Post URL:
https://<NETBOX URL>/api/dcim/interfaces/

Post Body (JSON):

{
  "device": 159,
  "name": "Ethernet1/1",
  "label": "",
  "type": "10gbase-t",
  "enabled": true,
  "parent": null,
  "bridge": null,
  "lag": null,
  "mtu": null,
  "mac_address": null,
  "wwn": null,
  "mgmt_only": false,
  "description": "***Link to Router***",
  "mode": "",
  "rf_role": null,
  "rf_channel": null,
  "rf_channel_frequency": "",
  "rf_channel_width": null,
  "tx_power": null,
  "untagged_vlan": null,
  "tagged_vlans": [],
  "mark_connected": false,
  "cable": {
    "label": null
  },
  "wireless_link": 0,
  "wireless_lans": [],
  "tags": [],
  "custom_fields": {}
}

Response:

{
    "rf_channel": [
        "This field may not be blank."
    ]
}

When I try to fill in a valid value for the rf_channel, it compains that it is not needed:
"rf_channel": "2.4g-1-2412-22"

Response:

{
    "rf_channel": [
        "Channel may be set only on wireless interfaces."
    ]
}

Expected Behavior

Expected is that the interface will be created in netbox at the specified devices without any wireless settings.

Observed Behavior

Hitting an error:

{
    "rf_channel": [
        "This field may not be blank."
    ]
}

Metadata

Metadata

Assignees

Labels

status: acceptedThis issue has been accepted for implementationtype: bugA confirmed report of unexpected behavior in the application

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions