I believe I was able to reproduce this on my setup. If I observed what I think I observed, it's definitely not a duplicate of bug 1271344 - that bug talks about re-assigning an IP from one VM to a new VM, but in my case even the existing VMs were not getting a response when they rebooted.
After restarting neutron-dhcp-agent, the VMs started getting responses and came back on the network.
I'm not sure what triggered the error state in my case - I left my setup for ~18 hours, came back, and it was in the error state. Next step is to dig into the logs to see if I can see likely problems, and see if I'm able to trigger the error condition.
I believe I was able to reproduce this on my setup. If I observed what I think I observed, it's definitely not a duplicate of bug 1271344 - that bug talks about re-assigning an IP from one VM to a new VM, but in my case even the existing VMs were not getting a response when they rebooted.
After restarting neutron-dhcp-agent, the VMs started getting responses and came back on the network.
I'm not sure what triggered the error state in my case - I left my setup for ~18 hours, came back, and it was in the error state. Next step is to dig into the logs to see if I can see likely problems, and see if I'm able to trigger the error condition.