This bug does not occur if you deploy a centos environment. Using image-based deployment, I deployed a single controller and single compute node on a linux server (nodes running under KVM). After I validated the environment is working fine by launching a VM and ensuring network connectivity between the nodes, I rebooted the compute node. After reboot, the compute node WAS able to reach the controller, and had the network was working fine. I also tried rebooting the controller node and after reboot there were no problems with the network.
This bug does not occur if you deploy a centos environment. Using image-based deployment, I deployed a single controller and single compute node on a linux server (nodes running under KVM). After I validated the environment is working fine by launching a VM and ensuring network connectivity between the nodes, I rebooted the compute node. After reboot, the compute node WAS able to reach the controller, and had the network was working fine. I also tried rebooting the controller node and after reboot there were no problems with the network.