On a network, "neutron port-list --network_id <net-id> --device_owner 'network:dhcp'" shows there are two ports. However, the "neutron dhcp-agent-list-hosting-net <net-id> shows only one DHCP-server running. This problem is observed in an environment with 4 nodes running dhcp-agents. The neutron API server and the DHCP agents are running on the same node.
What happened is that error occurred when the DHCP server is being "moved" from DHCP-agentA running on nodeA to DHCP-agentB running on nodeB. The sequence is
Right before or during the time step 1 is done, nodeA was rebooted. So the DHCP-port ws never removed. When nodeA came back and the DHCP-agent restarted, it didn't do the unplug of the dhcp port device. THe DHCP agent also failed to make the release_dhcp_port RPC call to the API-server to have the port deleted from mysql.
On a network, "neutron port-list --network_id <net-id> --device_owner 'network:dhcp'" shows there are two ports. However, the "neutron dhcp-agent- list-hosting- net <net-id> shows only one DHCP-server running. This problem is observed in an environment with 4 nodes running dhcp-agents. The neutron API server and the DHCP agents are running on the same node.
What happened is that error occurred when the DHCP server is being "moved" from DHCP-agentA running on nodeA to DHCP-agentB running on nodeB. The sequence is
neutron dhcp-agent- network- remove <agentA> <net-id> (1) network- add <agentB> <net-id> (2)
neutron dhcp-agent-
Right before or during the time step 1 is done, nodeA was rebooted. So the DHCP-port ws never removed. When nodeA came back and the DHCP-agent restarted, it didn't do the unplug of the dhcp port device. THe DHCP agent also failed to make the release_dhcp_port RPC call to the API-server to have the port deleted from mysql.