Neutron port bulk creation procedure ignores binding:vnic_type parameter
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Bulk port creation does not honor binding:vnic_type field. It implicitly uses
binding:vnic_type: normal
Example of bulk creation API call:
curl -v --location --request POST 'https://<neutron_
"ports" : [ {
"name" : "port1",
"admin_
"network_id" : "c2a3464a-
"binding:
}, {
"name" : "port2",
"admin_
"network_id" : "27dd162f-
"binding:
}]
}'
At the same time vnic_type is honored in 'single port' mode of this API, f.e. with payload like
"port" : {
"name" : "port_single",
"admin_
"network_id" : "c2a3464a-
"binding:
}
}'
Seems that binding:vnic_type from port parameters is not passed thru inside create_port_bulk() function. I've found a workaround. The following line should be added after
https:/
Thx Andrey for bug report. Are You going to push Your fix to review?