New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
virt: Fix long VNC passwords in vm_libvirt_hook.py #226
Conversation
Newer versions of libvirt accept VNC passwords of the maximum length 8, because QEMU uses only the first 8 characters anyway. We have already fixed the password length in Engine but if we migrate VMs created by older Engines they may fail to start on the destination due to the long VNC password. Let’s make those VMs migratable to newer hosts by fixing the password in the libvirt hook. We can simply remove the extra unused characters from the password to make libvirt happy. Bug-Url: https://bugzilla.redhat.com/2090156
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Horrible, but seems that we have no other way :-)
We don't -- we cannot fix all old hosts running the VMs with incompatible passwords without being able to migrate the VMs to newer hosts. |
We can't lookup the password somewhere and reset it on upgrade? |
/ost |
Responded in BZ (briefly, the solution in this patch is much safer and easier). |
Newer versions of libvirt accept VNC passwords of the maximum length 8,
because QEMU uses only the first 8 characters anyway. We have already
fixed the password length in Engine but if we migrate VMs created by
older Engines they may fail to start on the destination due to the
long VNC password.
Let’s make those VMs migratable to newer hosts by fixing the password
in the libvirt hook. We can simply remove the extra unused characters
from the password to make libvirt happy.
Bug-Url: https://bugzilla.redhat.com/2090156