I first set up plucky (should show the problem we fix) and noble (reference to not get broken by the change) guests that were up and running just fine on hosts being of F/J/N/O release.
The interesting bit here is that we test "against" guest releases and the host would not matter that much. It runs the wait script, by default /usr/share/uvtool/libvirt/remote-wait.sh against the guest and it needs to return when it is ready. Functionally they are all the same in all releases, prior to the update: root@f-sru:~# md5sum /usr/share/uvtool/libvirt/remote-wait.sh 3bf4076b196e49e6cae83968d5b67cca /usr/share/uvtool/libvirt/remote-wait.sh (same in J/N/O) After upgrade on all releases root@j-sru:~# md5sum /usr/share/uvtool/libvirt/remote-wait.sh a373cc413dd803557a077b38f0cf5b09 /usr/share/uvtool/libvirt/remote-wait.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
