Added an SRU template to this bug and an MP here https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/405967
** Description changed: + [Impact] + + * On copy-storage-all migration for certain combinations one + expects the creation of the target storage (it is known to not + work in all cases) + + * That regressed in Focal and was fixed later via upstream bug + https://bugzilla.redhat.com/show_bug.cgi?id=1793263 + + * This is backporting the same changes to Focal's libvirt + + [Test Plan] + + 1. .The same pool in the both source and target host: + # virsh pool-list + Name State Autostart + ------------------------------- + default active yes + pool0 active yes + + # virsh pool-dumpxml pool0 + <pool type='dir'> + <name>pool0</name> + <uuid>a66e307a-cd3c-4164-95f5-7809392912cb</uuid> + <capacity unit='bytes'>13886460059648</capacity> + <allocation unit='bytes'>1855581720576</allocation> + <available unit='bytes'>12030878339072</available> + <source> + </source> + <target> + <path>/opt/kvm/pool0</path> + <permissions> + <mode>0775</mode> + <owner>64055</owner> + <group>116</group> + </permissions> + </target> + </pool> + + 2.Show the image of the guest: + # virsh domblklist ubuntu-minimal-18.04 + Target Source + ------------------------------------------------------------- + vda /opt/kvm/pool0/ubuntu-minimal-18.04.hd-system.img + + 3.Do storage migration: + # virsh migrate --live --persistent --copy-storage-all --verbose ubuntu-minimal-18.04 qemu+ssh://10.10.10.10/system + error: Cannot access storage file '/opt/kvm/pool0/ubuntu-minimal-18.04.hd-system.img': No such file or directory + + + [Where problems could occur] + + * This is a series that also does some cleanups. It is upstream + and in EL8 for a while now and seems to be stable, but still + it changes plenty of code around qemu migration. + Therefore the area to look out for are all kind of migrations + done with qemu/kvm. + + * I have considered to backport a smaller subset with less cleanups, but + it becomes a mess and will eventually be more error prone and less + reliable. + + [Other Info] + + * TBD: I need to check myself how that really looked in Bionic (out + of curiosity) + + + --- + [System Info] Description: Ubuntu 20.04.2 LTS Release: 20.04 Linux hv1 5.4.0-70-generic #78-Ubuntu SMP Fri Mar 19 13:29:52 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux [Package Info] libvirt0: - Installed: 6.0.0-0ubuntu8.8 - Candidate: 6.0.0-0ubuntu8.8 - Version table: - *** 6.0.0-0ubuntu8.8 500 - 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 6.0.0-0ubuntu8.3 500 - 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages - 6.0.0-0ubuntu8 500 - 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages + Installed: 6.0.0-0ubuntu8.8 + Candidate: 6.0.0-0ubuntu8.8 + Version table: + *** 6.0.0-0ubuntu8.8 500 + 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 6.0.0-0ubuntu8.3 500 + 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages + 6.0.0-0ubuntu8 500 + 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages Steps to Reproduce: 1.The same pool in the both source and target host: # virsh pool-list - Name State Autostart + Name State Autostart ------------------------------- - default active yes - pool0 active yes + default active yes + pool0 active yes - # virsh pool-dumpxml pool0 + # virsh pool-dumpxml pool0 <pool type='dir'> - <name>pool0</name> - <uuid>a66e307a-cd3c-4164-95f5-7809392912cb</uuid> - <capacity unit='bytes'>13886460059648</capacity> - <allocation unit='bytes'>1855581720576</allocation> - <available unit='bytes'>12030878339072</available> - <source> - </source> - <target> - <path>/opt/kvm/pool0</path> - <permissions> - <mode>0775</mode> - <owner>64055</owner> - <group>116</group> - </permissions> - </target> + <name>pool0</name> + <uuid>a66e307a-cd3c-4164-95f5-7809392912cb</uuid> + <capacity unit='bytes'>13886460059648</capacity> + <allocation unit='bytes'>1855581720576</allocation> + <available unit='bytes'>12030878339072</available> + <source> + </source> + <target> + <path>/opt/kvm/pool0</path> + <permissions> + <mode>0775</mode> + <owner>64055</owner> + <group>116</group> + </permissions> + </target> </pool> 2.Show the image of the guest: # virsh domblklist ubuntu-minimal-18.04 - Target Source + Target Source ------------------------------------------------------------- - vda /opt/kvm/pool0/ubuntu-minimal-18.04.hd-system.img + vda /opt/kvm/pool0/ubuntu-minimal-18.04.hd-system.img 3.Do storage migration: # virsh migrate --live --persistent --copy-storage-all --verbose ubuntu-minimal-18.04 qemu+ssh://10.10.10.10/system error: Cannot access storage file '/opt/kvm/pool0/ubuntu-minimal-18.04.hd-system.img': No such file or directory Actual results: As step 3,migration failed. Expected results: Migrate successfully with pre-creating the image on target pool. Similar bug in rhel: https://bugzilla.redhat.com/show_bug.cgi?id=1793263 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929202 Title: [Ubuntu 20.04] Libvirtd will not pre-create images on the target host during migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1929202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
