update /etc/hosts resolve
restart nova_compute, nova_libvirt container
Live migration Error : Failed to connect to remote libvirt URI qemu tcp://compute1-VirtualBox/system: Unable to resolve address service '16509': Name or service not known
Hmm, that was not fixed because it is docker that manages /etc/hosts. It seems to be copying this on container restart indeed. Interesting. I run my deploy with DNS so never experienced this but this surely looks like an issue to be aware of when users report their problems. We might want to think about a possible workaround. Maybe start mounting /etc/hosts ro in all containers so it follows host's - we don't do docker networking so it does not matter that docker cannot add new entries this way.
0, the error instance log show:
1, check the /var/log/nova/nova-compute.log, the log show:
maybe the device cannot support the kvm or not have the modue
reference from :
2, install the qemu-kvm
3, restart the nova-compute container
and relaunch a new instance, it still show the same err:"Exeeded maximum number of retries", but the nova-compute.log show difference, there is no permission access kvm character device
reference from: "https://serverfault.com/questions/1002043/libvirt-has-no-kvm-capabilities-even-though-qemu-kvm-works"
4, and the change the permission to 666 /dev/kvm
5, relaunch the instance and it works
restart deploy and will get the image and run the container
rm all before containers and volumes(fernet, mariadb, rabitmq etc.),and restart the deploy
update the task yaml:
to resolve this error:
kolla-ansible bootstrap-server get err:"Unable to restart service docker"
check docker status
mimic the execute command, check the result
backup and move the twe conflict configures
restart the bootstrap-server and it work