Create of VLAN using the API and /available-vlans/ fails when role or tenant is present

[einaram]

NetBox version

v3.6-beta1

Python version

3.10

Steps to Reproduce

1. Create a tenant and note the ID
2. Create a VLAN group and note the ID
3. Run a POST to `api/ipam/vlan-groups//available-vlans/ like:

curl -X 'POST' \
  'https://demo.netbox.dev/api/ipam/vlan-groups/2/available-vlans/' \
  -d '{
  "name": "a_VLAN_name",
  "tenant": 2
}'

Expected Behavior

A new VLAN should be created

Observed Behavior

Bad request is returned with an error message that indicates that the deserialization used the tenant object instead of the ID:

  "tenant": [
    "Related objects must be referenced by numeric ID or by dictionary of attributes. Received an unrecognized value: Strickland Propane"
  ]
}

[einaram]

I have tested possible solution by not deserializing requested_vlans and instead adding vid to the raw data. This, and tests modified to test this behavoir is available here:
develop...einaram:netbox:13440-fix-available-vlan-post

[jeremystretch]

This and similar API endpoints were refactored recently in feature to use the new common AvailableObjectsView (see #12180), however the bug does still exist. Testing shows that tenant assignment works as expected when provisioning available IPs, but not for available VLANs. This is due to a difference between the serializers: CreateAvailableVLANSerializer defines a tenant field whereas AvailableIPSerializer does not.

Further investigation is needed to determine the appropriate fix. We need to ensure that all serializers that enable the automatic creation of "available" objects operate in a consistent manner.

[jeremystretch]

@arthanson this may be related to #13746

[arthanson]

This is fixed by #13746

[jeremystretch]

Confirmed that this has been resolved by PR #13889. Thanks @arthanson!