The issue was with dhcp not coming up on e195eaf6-9ccd-485d-a03c-bddc05fa9a96(tenant1-mgmt-net). e195eaf6-9ccd-485d-a03c-bddc05fa9a96 was scheduled to the dhcp agent on compute-1, but the dhcp agent was not being updated with this information, so did not launch a dnsmasq process for this port. There was a namespace for that e195eaf6-9ccd-485d-a03c-bddc05fa9a96, indicating that the network had previously been on that compute node, and was probably rescheduled away from it, and then back to it.
The issue was with dhcp not coming up on e195eaf6- 9ccd-485d- a03c-bddc05fa9a 96(tenant1- mgmt-net) . e195eaf6- 9ccd-485d- a03c-bddc05fa9a 96 was scheduled to the dhcp agent on compute-1, but the dhcp agent was not being updated with this information, so did not launch a dnsmasq process for this port. There was a namespace for that e195eaf6- 9ccd-485d- a03c-bddc05fa9a 96, indicating that the network had previously been on that compute node, and was probably rescheduled away from it, and then back to it.
How frequently is this occuring?