Bug 1917262

Created attachment 1748389 [details]
volume-cannot-detach-after-v2v-conversion

Description of problem:
The volume can't be detached from v2v appliance automatically after v2v converting guest to OSP16.2

Version-Release number of selected component (if applicable):
virt-v2v-1.42.0-7.module+el8.4.0+9398+f376ac33.x86_64
libguestfs-1.44.0-1.module+el8.4.0+9398+f376ac33.x86_64
libvirt-libs-7.0.0-1.module+el8.4.0+9464+3e71831a.x86_64
qemu-kvm-5.2.0-2.module+el8.4.0+9186+ec44380f.x86_64
nbdkit-1.24.0-1.module+el8.4.0+9341+96cf2672.x86_64
python3-openstackclient-4.0.1-2.20201217180131.bff556c.el8ost.1.noarch
RHOS-16.2-RHEL-8-20210113.n.0


How reproducible:
100%

Steps to Reproduce:
1. Prepare a guest which has installed virt-v2v on OSP16.2 environment, we call the guest as 'v2v-appliance'
$ openstack server list
+--------------------------------------+----------------------+--------+------------------------------------+--------------------------------------+--------+
| ID                                   | Name                 | Status | Networks                           | Image                                | Flavor |
+--------------------------------------+----------------------+--------+------------------------------------+--------------------------------------+--------+
| 381a9246-ddd7-4236-8d19-27868e360380 | v2v-appliance-latest | ACTIVE | private=192.168.0.112, 10.73.224.2 | RHEL-8.4.0-20210107.n.0-x86_64.qcow2 |        |
+--------------------------------------+----------------------+--------+------------------------------------+--------------------------------------+--------+


2.Convert a guest from VMware to OSP16.2 by virt-v2v
(overcloud) [root@localhost ~]# virt-v2v -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 -o openstack -oo server-id=v2v-appliance-latest  -ip /home/passwd esx7.0-rhel8.3-x86_64-efi
[   1.6] Opening the source -i libvirt -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 esx7.0-rhel8.3-x86_64-efi -it vddk  -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78
[   3.7] Creating an overlay to protect the source from being modified
[   4.6] Opening the overlay
[  11.7] Inspecting the overlay
[  32.0] Checking for sufficient free disk space in the guest
[  32.0] Estimating space required on target for each disk
[  32.0] Converting Red Hat Enterprise Linux 8.3 Beta (Ootpa) to run on KVM
virt-v2v: This guest has virtio drivers installed.
[ 120.7] Mapping filesystem data to avoid copying unused and blank areas
virt-v2v: warning: fstrim on guest filesystem /dev/sda1 failed.  Usually 
you can ignore this message.  To find out more read "Trimming" in 
virt-v2v(1).

Original message: fstrim: fstrim: /sysroot/: the discard operation is not 
supported
[ 121.7] Closing the overlay
[ 122.0] Assigning disks to buses
[ 122.0] Checking if the guest needs BIOS or UEFI to boot
virt-v2v: This guest requires UEFI on the target to boot.
[ 122.0] Initializing the target -o openstack
Failed to set volume read-only access mode flag: Invalid volume: Volume 8254e656-8ac6-409d-b0ab-7205f368be09 status must be available to update readonly flag, but current status is: creating. (HTTP 400) (Request-ID: req-8a69287f-7c37-47ac-baf6-73af9443757d)
[ 136.9] Copying disk 1/1 to /dev/disk/by-id/virtio-8254e656-8ac6-409d-b (raw)
    (100.00/100%)
[ 670.4] Creating output metadata
[ 676.2] Finishing off


3.Try to launch the volume as instance on OSP16.2 dashboard after v2v conversion, but found the status of volume is in-use, the volume can't be detach from v2v appliance automatically, pls refer to screenshot"volume-cannot-detach-after-v2v-conversion"


Actual result:
As above description

Expected results:
The volume should be detached from v2v appliance automatically after v2v converting guest to OSP16.2

Additional info：
1.Can't reproduce the bug on OSP16.1