Comment 3 for bug 1462107

While verifying this workaround:

[ml2_mech_cisco_nexus:10.86.7.59]
compute-1=1/1,1/2
compute-2=1/1,1/3
ssh_port=22
username=admin
password=cisco123

I came across another issue.

When the DHCP namespace is automatically created after the network node reboot, there is a port binding failure for the corresponding DHCP neutron port:

[root@bxb-ds-46 ~]# ip netns
qdhcp-d1e57ac4-b775-4dd1-ab4d-c901ebb04c98
qrouter-3b3f07ff-f530-4cfb-8a4b-f85ea0d4441c
[root@bxb-ds-46 ~]# neutron port-list
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| id | name | mac_address | fixed_ips |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| 036acf84-a5c2-4789-a742-bc049d0d2dff | | fa:16:3e:72:c2:8e | {"subnet_id": "768ea98d-3b7e-43a5-b18a-d3a1a284c193", "ip_address": "10.86.7.239"} |
| 52a2db1a-1929-4c2c-8720-c08b0706b4cb | | fa:16:3e:d1:43:a6 | {"subnet_id": "e7ec9460-b1aa-4801-a128-345955a38467", "ip_address": "192.168.1.2"} |
| 7a4610d4-9a63-4eee-88ea-8086cb5702fc | | fa:16:3e:fb:98:0d | {"subnet_id": "e7ec9460-b1aa-4801-a128-345955a38467", "ip_address": "192.168.1.1"} |
+--------------------------------------+------+-------------------+——————————————————————————————————————————+
[root@bxb-ds-46 ~]# neutron port-show 52a2db1a-1929-4c2c-8720-c08b0706b4cb
+-----------------------+------------------------------------------------------------------------------------+
| Field | Value |
+-----------------------+------------------------------------------------------------------------------------+
| admin_state_up | True |
| allowed_address_pairs | |
| binding:host_id | bxb-ds-46 |
| binding:profile | {} |
| binding:vif_details | {} |
| binding:vif_type | binding_failed | <<<<<ERROR
| binding:vnic_type | normal |
| device_id | dhcpc63a1974-ca08-50bd-9dfd-34e0a562acaf-d1e57ac4-b775-4dd1-ab4d-c901ebb04c98 |
| device_owner | network:dhcp |
| extra_dhcp_opts | |
| fixed_ips | {"subnet_id": "e7ec9460-b1aa-4801-a128-345955a38467", "ip_address": "192.168.1.2"} |
| id | 52a2db1a-1929-4c2c-8720-c08b0706b4cb |
| mac_address | fa:16:3e:d1:43:a6 |
| name | |
| network_id | d1e57ac4-b775-4dd1-ab4d-c901ebb04c98 |
| security_groups | |
| status | DOWN |
| tenant_id | 0ed5462240e54aceb67800e18c20251b |
+-----------------------+------------------------------------------------------------------------------------+

As a result, any VM launched for this network won’t get any IP address from DHCP.