- Users - oVirt List Archives

Cannot delete pvc attached to pod using ovirt-csi in kubernetes
by ssarang520＠gmail.com 24 Aug '21

24 Aug '21

Hi all, I deployed ovirt-csi in the k8s by applying yaml manually. I used the latest version of the container image. (https://github.com/openshift/ovirt-csi-driver-operator/tree/master/assets) After successfully creating pvc and pod, I tried to delete it. And the pod is deleted, but the pvc is not deleted. This is because deleting a pod does not unmap /dev/rbd0 attached to the ovirt vm. How can I delete the pvc successfully? oVirt engine version is 4.4.7.6-1.el8. Here is the engine log when deleting the pod: 2021-08-20 17:40:35,385+09 INFO [org.ovirt.engine.core.sso.service.AuthenticationService] (default task-149) [] User admin@internal-authz with profile [internal] successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2021-08-20 17:40:35,403+09 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-149) [68ee3182] Running command: CreateUserSessionCommand internal: false. 2021-08-20 17:40:35,517+09 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-149) [68ee3182] EVENT_ID: USER_VDC_LOGIN(30), User admin@internal-authz connecting from '192.168.7.169' using session 'XfDgNkmAGnPiZahK5itLhHQTCNHZ3JwXMMzOiZrYL3C32+1TTys3xcjrAmCIKPu02hgN1sdVpfZXWd0FznaPCQ==' logged in. 2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:35,520+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:35,663+09 INFO [org.ovirt.engine.core.bll.storage.disk.DetachDiskFromVmCommand] (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] Running command: DetachDiskFromVmCommand internal: false. Entities affected : ID: 59a7461c-72fe-4e01-86a7-c70243f31596 Type: VMAction group CONFIGURE_VM_STORAGE with role type USER 2021-08-20 17:40:35,664+09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand] (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] START, HotUnPlugDiskVDSCommand(HostName = host, HotPlugDiskVDSParameters:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094', vmId='59a7461c-72fe-4e01-86a7-c70243f31596', diskId='63a64445-1659-4d5f-8847-e7266e64b09e'}), log id: 506ff4a4 2021-08-20 17:40:35,678+09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand] (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] Disk hot-unplug: <?xml version="1.0" encoding="UTF-8"?><hotunplug> <devices> <disk> <alias name="ua-63a64445-1659-4d5f-8847-e7266e64b09e"/> </disk> </devices> </hotunplug> 2021-08-20 17:40:35,749+09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand] (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] FINISH, HotUnPlugDiskVDSCommand, return: , log id: 506ff4a4 2021-08-20 17:40:35,842+09 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] EVENT_ID: USER_DETACH_DISK_FROM_VM(2,018), Disk pvc-9845a0ff-e94c-497c-8c65-fc6a1e26db20 was successfully detached from VM centos by admin@internal-authz. 2021-08-20 17:40:35,916+09 ERROR [org.ovirt.engine.core.sso.service.SsoService] (default task-150) [] OAuthException invalid_grant: The provided authorization grant for the auth code has expired. 2021-08-20 17:40:35,917+09 ERROR [org.ovirt.engine.core.aaa.filters.SsoRestApiAuthFilter] (default task-149) [] Cannot authenticate using authentication Headers: invalid_grant: The provided authorization grant for the auth code has expired. 2021-08-20 17:40:36,029+09 INFO [org.ovirt.engine.core.sso.service.AuthenticationService] (default task-149) [] User admin@internal-authz with profile [internal] successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2021-08-20 17:40:36,046+09 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-149) [4c4bf441] Running command: CreateUserSessionCommand internal: false. 2021-08-20 17:40:36,114+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:36,114+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:36,114+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:36,114+09 WARN [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't find relative path for class "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will return null 2021-08-20 17:40:49,241+09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DumpXmlsVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-27) [] START, DumpXmlsVDSCommand(HostName = host, Params:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094', vmIds='[59a7461c-72fe-4e01-86a7-c70243f31596]'}), log id: 7eb54202 2021-08-20 17:40:49,244+09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DumpXmlsVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-27) [] FINISH, DumpXmlsVDSCommand, return: {59a7461c-72fe-4e01-86a7-c70243f31596=<domain type='kvm' id='1' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>centos</name> <uuid>59a7461c-72fe-4e01-86a7-c70243f31596</uuid> <metadata xmlns:ns1="http://ovirt.org/vm/tune/1.0" xmlns:ovirt-vm="http://ovirt.org/vm/1.0"> <ns1:qos/> <ovirt-vm:vm xmlns:ovirt-vm="http://ovirt.org/vm/1.0"> <ovirt-vm:balloonTarget type="int">4194304</ovirt-vm:balloonTarget> <ovirt-vm:ballooningEnabled>true</ovirt-vm:ballooningEnabled> <ovirt-vm:clusterVersion>4.6</ovirt-vm:clusterVersion> <ovirt-vm:destroy_on_reboot type="bool">False</ovirt-vm:destroy_on_reboot> <ovirt-vm:launchPaused>false</ovirt-vm:launchPaused> <ovirt-vm:memGuaranteedSize type="int">4096</ovirt-vm:memGuaranteedSize> <ovirt-vm:minGuaranteedMemoryMb type="int">4096</ovirt-vm:minGuaranteedMemoryMb> <ovirt-vm:resumeBehavior>auto_resume</ovirt-vm:resumeBehavior> <ovirt-vm:startTime type="float">1628558564.8754532</ovirt-vm:startTime> <ovirt-vm:device alias="ua-7c9f38e9-8889-46c8-83bb-92efb9272de9" mac_address="56:6f:16:a8:00:07"> <ovirt-vm:network>ovirtmgmt</ovirt-vm:network> <ovirt-vm:custom> <ovirt-vm:queues>2</ovirt-vm:queues> </ovirt-vm:custom> </ovirt-vm:device> <ovirt-vm:device devtype="disk" name="sda"> <ovirt-vm:domainID>6ce3b498-532e-4dc0-9e22-15d0bb24166a</ovirt-vm:domainID> <ovirt-vm:guestName>/dev/sda</ovirt-vm:guestName> <ovirt-vm:imageID>bee44276-234f-4ed7-8a8a-d90a5e3cb5b3</ovirt-vm:imageID> <ovirt-vm:managed type="bool">False</ovirt-vm:managed> <ovirt-vm:poolID>4ca6e0e8-e3a4-11eb-8830-480fcf63834f</ovirt-vm:poolID> <ovirt-vm:volumeID>a93c6e11-6c7c-4efb-8c93-4ed5712ce7e4</ovirt-vm:volumeID> <ovirt-vm:volumeChain> <ovirt-vm:volumeChainNode> <ovirt-vm:domainID>6ce3b498-532e-4dc0-9e22-15d0bb24166a</ovirt-vm:domainID> <ovirt-vm:imageID>bee44276-234f-4ed7-8a8a-d90a5e3cb5b3</ovirt-vm:imageID> <ovirt-vm:leaseOffset type="int">0</ovirt-vm:leaseOffset> <ovirt-vm:leasePath>/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/4425404b-17f0-4519-812f-b09a952a9003.lease</ovirt-vm:leasePath> <ovirt-vm:path>/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/4425404b-17f0-4519-812f-b09a952a9003</ovirt-vm:path> <ovirt-vm:volumeID>4425404b-17f0-4519-812f-b09a952a9003</ovirt-vm:volumeID> </ovirt-vm:volumeChainNode> <ovirt-vm:volumeChainNode> <ovirt-vm:domainID>6ce3b498-532e-4dc0-9e22-15d0bb24166a</ovirt-vm:domainID> <ovirt-vm:imageID>bee44276-234f-4ed7-8a8a-d90a5e3cb5b3</ovirt-vm:imageID> <ovirt-vm:leaseOffset type="int">0</ovirt-vm:leaseOffset> <ovirt-vm:leasePath>/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/a93c6e11-6c7c-4efb-8c93-4ed5712ce7e4.lease</ovirt-vm:leasePath> <ovirt-vm:path>/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/a93c6e11-6c7c-4efb-8c93-4ed5712ce7e4</ovirt-vm:path> <ovirt-vm:volumeID>a93c6e11-6c7c-4efb-8c93-4ed5712ce7e4</ovirt-vm:volumeID> </ovirt-vm:volumeChainNode> </ovirt-vm:volumeChain> </ovirt-vm:device> <ovirt-vm:device devtype="disk" name="sdc"> <ovirt-vm:managed type="bool">False</ovirt-vm:managed> </ovirt-vm:device> </ovirt-vm:vm> </metadata> <maxMemory slots='16' unit='KiB'>16777216</maxMemory> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu placement='static' current='2'>16</vcpu> <resource> <partition>/machine</partition> </resource> <sysinfo type='smbios'> <system> <entry name='manufacturer'>oVirt</entry> <entry name='product'>RHEL</entry> <entry name='version'>8.4-1.2105.el8</entry> <entry name='serial'>83e66af8-0500-11e6-9c43-bc00007c0000</entry> <entry name='uuid'>59a7461c-72fe-4e01-86a7-c70243f31596</entry> <entry name='family'>oVirt</entry> </system> </sysinfo> <os> <type arch='x86_64' machine='pc-q35-rhel8.4.0'>hvm</type> <boot dev='hd'/> <smbios mode='sysinfo'/> </os> <features> <acpi/> </features> <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>Skylake-Client-noTSX-IBRS</model> <topology sockets='16' dies='1' cores='1' threads='1'/> <feature policy='require' name='ssbd'/> <feature policy='require' name='md-clear'/> <feature policy='disable' name='mpx'/> <feature policy='require' name='hypervisor'/> <numa> <cell id='0' cpus='0-15' memory='4194304' unit='KiB'/> </numa> </cpu> <clock offset='variable' adjustment='0' basis='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <pm> <suspend-to-mem enabled='no'/> <suspend-to-disk enabled='no'/> </pm> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='file' device='cdrom'> <driver name='qemu' error_policy='report'/> <source startupPolicy='optional'/> <target dev='sdc' bus='sata'/> <readonly/> <alias name='ua-df0ac774-3623-4868-8bd3-45c8f2aa3dc4'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk' snapshot='no'> <driver name='qemu' type='qcow2' cache='none' error_policy='stop' io='threads'/> <source file='/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/a93c6e11-6c7c-4efb-8c93-4ed5712ce7e4' index='8'> <seclabel model='dac' relabel='no'/> </source> <backingStore type='file' index='1'> <format type='qcow2'/> <source file='/rhev/data-center/mnt/192.168.7.18:_home_tmax_nfs/6ce3b498-532e-4dc0-9e22-15d0bb24166a/images/bee44276-234f-4ed7-8a8a-d90a5e3cb5b3/4425404b-17f0-4519-812f-b09a952a9003'> <seclabel model='dac' relabel='no'/> </source> <backingStore/> </backingStore> <target dev='sda' bus='scsi'/> <serial>bee44276-234f-4ed7-8a8a-d90a5e3cb5b3</serial> <alias name='ua-bee44276-234f-4ed7-8a8a-d90a5e3cb5b3'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x16'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0x17'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0x18'/> <alias name='pci.9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='10' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='10' port='0x19'/> <alias name='pci.10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> </controller> <controller type='pci' index='11' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='11' port='0x1a'/> <alias name='pci.11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x2'/> </controller> <controller type='pci' index='12' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='12' port='0x1b'/> <alias name='pci.12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x3'/> </controller> <controller type='pci' index='13' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='13' port='0x1c'/> <alias name='pci.13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x4'/> </controller> <controller type='pci' index='14' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='14' port='0x1d'/> <alias name='pci.14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x5'/> </controller> <controller type='pci' index='15' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='15' port='0x1e'/> <alias name='pci.15'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x6'/> </controller> <controller type='pci' index='16' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='16' port='0x1f'/> <alias name='pci.16'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x7'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='virtio-serial' index='0' ports='16'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </controller> <controller type='scsi' index='0' model='virtio-scsi'> <alias name='ua-82c49f93-c4e8-460b-bb7d-95db0e9d87a0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='8'> <alias name='ua-ad56daea-edb1-45c7-a1ab-2a7db3aaeee2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='56:6f:16:a8:00:07'/> <source bridge='ovirtmgmt'/> <target dev='vnet0'/> <model type='virtio'/> <driver name='vhost' queues='2'/> <filterref filter='vdsm-no-mac-spoofing'/> <link state='up'/> <mtu size='1500'/> <alias name='ua-7c9f38e9-8889-46c8-83bb-92efb9272de9'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channels/59a7461c-72fe-4e01-86a7-c70243f31596.ovirt-guest-agent.0'/> <target type='virtio' name='ovirt-guest-agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channels/59a7461c-72fe-4e01-86a7-c70243f31596.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel1'/> <address type='virtio-serial' controller='0' bus='0' port='2'/> </channel> <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0' state='disconnected'/> <alias name='channel2'/> <address type='virtio-serial' controller='0' bus='0' port='3'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5900' autoport='yes' listen='192.168.7.18' keymap='en-us' passwdValidTo='1970-01-01T00:00:01'> <listen type='network' address='192.168.7.18' network='vdsm-ovirtmgmt'/> </graphics> <graphics type='spice' port='5901' tlsPort='5902' autoport='yes' listen='192.168.7.18' passwdValidTo='1970-01-01T00:00:01'> <listen type='network' address='192.168.7.18' network='vdsm-ovirtmgmt'/> <channel name='main' mode='secure'/> <channel name='display' mode='secure'/> <channel name='inputs' mode='secure'/> <channel name='cursor' mode='secure'/> <channel name='playback' mode='secure'/> <channel name='record' mode='secure'/> <channel name='smartcard' mode='secure'/> <channel name='usbredir' mode='secure'/> </graphics> <video> <model type='qxl' ram='65536' vram='8192' vgamem='16384' heads='1' primary='yes'/> <alias name='ua-799f065a-b2b9-4e37-a502-f86c7cc8dc51'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <stats period='5'/> <alias name='ua-c2bfe0b9-065a-46b7-9b0b-ef7e0f699611'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </memballoon> <rng model='virtio'> <backend model='random'>/dev/urandom</backend> <alias name='ua-fa110e6b-5eed-4b4b-93d8-0ac5de08aa2e'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </rng> </devices> <seclabel type='dynamic' model='selinux' relabel='yes'> <label>system_u:system_r:svirt_t:s0:c437,c650</label> <imagelabel>system_u:object_r:svirt_image_t:s0:c437,c650</imagelabel> </seclabel> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+107:+107</label> <imagelabel>+107:+107</imagelabel> </seclabel> <qemu:capabilities> <qemu:add capability='blockdev'/> <qemu:add capability='incremental-backup'/> </qemu:capabilities> </domain> }, log id: 7eb54202 Here is the engine log when deleting the pvc: 2021-08-20 17:43:12,964 - cinder.volume.driver - INFO - Driver hasn't implemented _init_vendor_properties() 2021-08-20 17:43:12,990 - cinderlib-client - INFO - Deleting volume '63a64445-1659-4d5f-8847-e7266e64b09e' [feefc62f-e7cb-435d-ae21-4b52b53fbdfa] 2021-08-20 17:43:28,856 - cinder.volume.drivers.rbd - WARNING - ImageBusy error raised while deleting rbd volume. This may have been caused by a connection from a client that has crashed and, if so, may be resolved by retrying the delete after 30 seconds has elapsed. 2021-08-20 17:43:28,900 - cinderlib-client - ERROR - Failure occurred when trying to run command 'delete_volume': ImageBusy error raised while deleting rbd volume. This may have been caused by a connection from a client that has crashed and, if so, may be resolved by retrying the delete after 30 seconds has elapsed. [feefc62f-e7cb-435d-ae21-4b52b53fbdfa] 2021-08-20 17:43:28,901 - cinder - CRITICAL - Unhandled error Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 1195, in delete_volume _try_remove_volume(client, volume_name) File "/usr/lib/python3.6/site-packages/cinder/utils.py", line 683, in _wrapper return r.call(f, *args, **kwargs) File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 409, in call do = self.iter(retry_state=retry_state) File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 368, in iter raise retry_exc.reraise() File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 186, in reraise raise self.last_attempt.result() File "/usr/lib64/python3.6/concurrent/futures/_base.py", line 425, in result return self.__get_result() File "/usr/lib64/python3.6/concurrent/futures/_base.py", line 384, in __get_result raise self._exception File "/usr/lib/python3.6/site-packages/tenacity/__init__.py", line 412, in call result = fn(*args, **kwargs) File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 1190, in _try_remove_volume self.RBDProxy().remove(client.ioctx, volume_name) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 190, in doit result = proxy_call(self._autowrap, f, *args, **kwargs) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 148, in proxy_call rv = execute(f, *args, **kwargs) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 129, in execute six.reraise(c, e, tb) File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise raise value File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 83, in tworker rv = meth(*args, **kwargs) File "rbd.pyx", line 767, in rbd.RBD.remove rbd.ImageBusy: [errno 16] RBD image is busy (error removing image) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./cinderlib-client.py", line 170, in main args.command(args) File "./cinderlib-client.py", line 218, in delete_volume vol.delete() File "/usr/local/lib/python3.6/site-packages/cinderlib/objects.py", line 494, in delete self._raise_with_resource() File "/usr/local/lib/python3.6/site-packages/cinderlib/objects.py", line 222, in _raise_with_resource six.reraise(*exc_info) File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise raise value File "/usr/local/lib/python3.6/site-packages/cinderlib/objects.py", line 487, in delete self.backend.driver.delete_volume(self._ovo) File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 1205, in delete_volume raise exception.VolumeIsBusy(msg, volume_name=volume_name) cinder.exception.VolumeIsBusy: ImageBusy error raised while deleting rbd volume. This may have been caused by a connection from a client that has crashed and, if so, may be resolved by retrying the delete after 30 seconds has elapsed. During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./cinderlib-client.py", line 390, in <module> sys.exit(main(sys.argv[1:])) File "./cinderlib-client.py", line 176, in main sys.stderr.write(traceback.format_exc(e)) File "/usr/lib64/python3.6/traceback.py", line 167, in format_exc return "".join(format_exception(*sys.exc_info(), limit=limit, chain=chain)) File "/usr/lib64/python3.6/traceback.py", line 121, in format_exception type(value), value, tb, limit=limit).format(chain=chain)) File "/usr/lib64/python3.6/traceback.py", line 498, in __init__ _seen=_seen) File "/usr/lib64/python3.6/traceback.py", line 509, in __init__ capture_locals=capture_locals) File "/usr/lib64/python3.6/traceback.py", line 338, in extract if limit >= 0: TypeError: '>=' not supported between instances of 'VolumeIsBusy' and 'int'

4 13

what difference between the Cloud-Init Network Protocol options ?
by Tommy Sway 24 Aug '21

24 Aug '21

What is the difference between Openstack MateData and ENI in the cloud-init Network Protocol option? Or what kind of scenarios do they apply to?

3 12

OVA Export to local storage failes
by David White 24 Aug '21

24 Aug '21

I have an unused 200GB partition that I'd like to use to copy / export / backup a few VMs onto, so I mounted it to one of my oVirt hosts as /ova-images/, and then ran "chown 36:36" on ova-images. From the engine, I then tried to export an OVA to that directory. Watching the directory with "ls", I see a filename.ova.tmp eventually appear, and it grows to the size I would expect for the image... and then a few seconds later, it disappears. What am I missing? Here's what I see in the Event Manager inside the Engine: Aug 21, 2021, 8:35:26 PM Failed to export Vm server.example.org as a Virtual Appliance to path /ova-images/server.example.org.ova on Host cha2-storage.mgt.example.com Aug 21, 2021, 8:34:33 PM Pack OVA. Retrieving the temporary path for the OVA file. Aug 21, 2021, 8:34:33 PM Pack OVA. Allocating the temporary path for the OVA file. Aug 21, 2021, 8:34:33 PM Pack OVA. Removing the temporary file. Aug 21, 2021, 8:34:33 PM Pack OVA. Examine target directory. Aug 21, 2021, 8:34:33 PM Pack OVA. Set facts. Aug 21, 2021, 8:34:33 PM Pack OVA. Run import yaml on py3. Aug 21, 2021, 8:34:21 PM Image measure. Measure an image. Aug 21, 2021, 8:33:56 PM Starting to export Vm server.example.org as a Virtual Appliance Aug 21, 2021, 8:33:52 PM Export OVA. Examine target directory. Aug 21, 2021, 8:33:49 PM Export OVA. Set facts. Aug 21, 2021, 8:33:49 PM Export OVA. Run import yaml on py3. Sent with ProtonMail Secure Email.

2 3

Resize iSCSI LUN and Storage Domain
by Shantur Rathore 24 Aug '21

24 Aug '21

Hi all, I have an iSCSI Storage Domain for VMs and need to increase storage. To do this, I increased the size of LUN on iscsi storage server and tried to refresh the size of Storage Domain as per https://www.ovirt.org/documentation/administration_guide/index.html#Increas… "*Refreshing the LUN Size" section* I cannot see the "Additional Storage Size" column or any other option to refresh the LUN size. What am I missing here? Kind regards, Shantur

6 7

about the network name rules on CentOS/Redhat 8 and the cloud-init network interface name
by Tommy Sway 24 Aug '21

24 Aug '21

Everybody is good! As you all know, to use the client's network card name in cloud-init, you must fill in the exact name of the network card interface. This was easy in version 7 and before, which usually started with EN0. After version 8, however, the naming conventions for network cards changed a lot. In my own test environment, for example, I started with ENS3. I'm not sure what naming convention it uses, which would make it impossible to specify nic information using cloud-init. Could you help me explain how to deal with this problem? Thank you very much!

3 4

Backup to tape
by duparchy＠esrf.fr 24 Aug '21

24 Aug '21

Hi, Part of our Disaster Recovery Plan we do tape backup. Our previous infrastructure was Oracle VM and VMs fisk were files (.img) we could apply filters to our tar and backup to tape only required files. Now preparing the migration to Oracle flavor of oVirt (OLVM). VMs disks are LVM partitions, within an iSCSI LUNs. I've tested "dd" to backup the entire iSCSI LUN to the tape. Seems OK ,providing the right block size we achieve reasonable performances. Though I don't quite see how to have that granular backup we had, in a simple manner, which a goal too. Although there is compression at the LTO level, the dd conv=sparse parameter may speed-up things. To be tested. I'm just wondering if conv=sparse may breaks things at the LVM / qcow2 containers ?

3 3

Impossible to move disk after a previous disk move failed
by James Wadsworth 24 Aug '21

24 Aug '21

This is the log of when it fails 2021-08-23 21:24:10,667+0200 WARN (tasks/0) [storage.LVM] Command with specific filter failed or returned no data, retrying with a wider filter: LVM command failed: 'cmd=[\'/sbin/lvm\', \'lvcreate\', \'--config\', \'devices { preferred_names=["^/dev/mapper/"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter=["a|^/dev/mapper/36001405299f83b19569473f9c580660c$|", "r|.*|"] hints="none" obtain_device_list_from_udev=0 } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 use_lvmetad=0 use_lvmpolld=1 } backup { retain_min=50 retain_days=0 }\', \'--autobackup\', \'n\', \'--contiguous\', \'n\', \'--size\', \'40960m\', \'--wipesignatures\', \'n\', \'--addtag\', \'OVIRT_VOL_INITIALIZING\', \'--name\', \'432ceb20-efb7-4a40-8431-1b5c825a6168\', \'c23a5bef-48e0-46c7-9d5b-93c97f0240c0\'] rc=5 out=[] err=[\' Logical Volume "432ceb20-efb7-4a40-8431-1b5c825a6168" already exists in volume group "c23a5bef-48e0-46c7-9d5b-93c97f0240c0"\']' (l vm:534) 2021-08-23 21:24:10,859+0200 WARN (tasks/0) [storage.LVM] All 2 tries have failed: LVM command failed: 'cmd=[\'/sbin/lvm\', \'lvcreate\', \'--config\', \'devices { preferred_names=["^/dev/mapper/"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter=["a|^/dev/mapper/36001405299f83b19569473f9c580660c$|^/dev/mapper/36001405cdf35411dd040d4121d9326d1$|^/dev/mapper/36001405df393063de6f0d4451d8a61d3$|", "r|.*|"] hints="none" obtain_device_list_from_udev=0 } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 use_lvmetad=0 use_lvmpolld=1 } backup { retain_min=50 retain_days=0 }\', \'--autobackup\', \'n\', \'--contiguous\', \'n\', \'--size\', \'40960m\', \'--wipesignatures\', \'n\', \'--addtag\', \'OVIRT_VOL_INITIALIZING\', \'--name\', \'432ceb20-efb7-4a40-8431-1b5c825a6168\', \'c23a5bef-48e0-46c7-9d5b-93c97f0240c0\'] rc=5 out=[] err=[\' Logical Volume "432ceb20-efb7-4a40-8431-1b5c825a6168" already exists in volume group "c23a5bef-4 8e0-46c7-9d5b-93c97f0240c0"\']' (lvm:561) 2021-08-23 21:24:10,859+0200 ERROR (tasks/0) [storage.Volume] Failed to create volume /rhev/data-center/mnt/blockSD/c23a5bef-48e0-46c7-9d5b-93c97f0240c0/images/2172a4ac-6992-4cc2-be1b-6b9290bc9798/432ceb20-efb7-4a40-8431-1b5c825a6168: Cannot create Logical Volume: 'vgname=c23a5bef-48e0-46c7-9d5b-93c97f0240c0 lvname=432ceb20-efb7-4a40-8431-1b5c825a6168 err=[\' Logical Volume "432ceb20-efb7-4a40-8431-1b5c825a6168" already exists in volume group "c23a5bef-48e0-46c7-9d5b-93c97f0240c0"\']' (volume:1257) 2021-08-23 21:24:10,860+0200 ERROR (tasks/0) [storage.Volume] Unexpected error (volume:1293) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/volume.py", line 1254, in create add_bitmaps=add_bitmaps) File "/usr/lib/python3.6/site-packages/vdsm/storage/blockVolume.py", line 508, in _create initialTags=(sc.TAG_VOL_UNINIT,)) File "/usr/lib/python3.6/site-packages/vdsm/storage/lvm.py", line 1633, in createLV raise se.CannotCreateLogicalVolume(vgName, lvName, err) vdsm.storage.exception.CannotCreateLogicalVolume: Cannot create Logical Volume: 'vgname=c23a5bef-48e0-46c7-9d5b-93c97f0240c0 lvname=432ceb20-efb7-4a40-8431-1b5c825a6168 err=[\' Logical Volume "432ceb20-efb7-4a40-8431-1b5c825a6168" already exists in volume group "c23a5bef-48e0-46c7-9d5b-93c97f0240c0"\']' 2021-08-23 21:24:10,860+0200 ERROR (tasks/0) [storage.TaskManager.Task] (Task='55a4e8dc-9408-4969-b0ba-b9a556bccba1') Unexpected error (task:877) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 884, in _run return fn(*args, **kargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 350, in run return self.cmd(*self.argslist, **self.argsdict) File "/usr/lib/python3.6/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/sp.py", line 1945, in createVolume initial_size=initialSize, add_bitmaps=addBitmaps) File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 1216, in createVolume initial_size=initial_size, add_bitmaps=add_bitmaps) File "/usr/lib/python3.6/site-packages/vdsm/storage/volume.py", line 1254, in create add_bitmaps=add_bitmaps) File "/usr/lib/python3.6/site-packages/vdsm/storage/blockVolume.py", line 508, in _create initialTags=(sc.TAG_VOL_UNINIT,)) File "/usr/lib/python3.6/site-packages/vdsm/storage/lvm.py", line 1633, in createLV raise se.CannotCreateLogicalVolume(vgName, lvName, err) vdsm.storage.exception.CannotCreateLogicalVolume: Cannot create Logical Volume: 'vgname=c23a5bef-48e0-46c7-9d5b-93c97f0240c0 lvname=432ceb20-efb7-4a40-8431-1b5c825a6168 err=[\' Logical Volume "432ceb20-efb7-4a40-8431-1b5c825a6168" already exists in volume group "c23a5bef-48e0-46c7-9d5b-93c97f0240c0"\']' The logical volume it is trying to create already exists in the volume group. Can anyone help me get out of this situation? Thanks, James

2 1

Re: [External] : Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use?
by Tommy Sway 24 Aug '21

24 Aug '21

Thank you! From: Marcos Sungaila <marcos.sungaila(a)oracle.com> Sent: Monday, August 23, 2021 11:39 PM To: Tommy Sway <sz_cuitao(a)163.com>; 'wodel youchi' <wodel.youchi(a)gmail.com> Cc: 'users' <users(a)ovirt.org> Subject: RE: [ovirt-users] Re: [External] : Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use? Tommy, I remember I used the doc from Debian page as a starting point and adapted to Fedora. I deactivated the NetworkManager on the WLAN interface and prepared many commands to add to rc.local. I remember I had issues with routing when using NAT network (it was a KVM host only, not an oVirt instance) despite it woked fine with bridge connections. I will look if I have a copy in my old backups. It was a long time ago. Marcos From: Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > Sent: segunda-feira, 23 de agosto de 2021 12:05 To: Marcos Sungaila <marcos.sungaila(a)oracle.com <mailto:marcos.sungaila@oracle.com> >; 'wodel youchi' <wodel.youchi(a)gmail.com <mailto:wodel.youchi@gmail.com> > Cc: 'users' <users(a)ovirt.org <mailto:users@ovirt.org> > Subject: [ovirt-users] Re: [External] : Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use? Thank you! Could you give me some guide doc ? Moreover, my use environment is only for testing functions and does not involve security issues. I just want to make full use of physical resources. From: users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org> <users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org> > On Behalf Of Marcos Sungaila Sent: Monday, August 23, 2021 9:13 PM To: wodel youchi <wodel.youchi(a)gmail.com <mailto:wodel.youchi@gmail.com> >; Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > Cc: users <users(a)ovirt.org <mailto:users@ovirt.org> > Subject: [ovirt-users] Re: [External] : Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use? Hi Tommy, Two comments for your appreciation: 1st: Technically, it is possible. You can configure your wireless network as a bridge and use it as you wish. I did it in my laptop a long time ago to test KVM instances. 2nd: Taking security in focus, it is not a recommendation to use wireless cards in servers. Wireless connections can be easily attacked since there is no need for someone to have logical access to your server. Regards, Marcos From: wodel youchi <wodel.youchi(a)gmail.com <mailto:wodel.youchi@gmail.com> > Sent: domingo, 22 de agosto de 2021 07:13 To: Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > Cc: users <users(a)ovirt.org <mailto:users@ovirt.org> > Subject: [External] : [ovirt-users] Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use? Hi, In my little experience, no you can't, I tried that a while ago it didn't work, there is some old tutorial on Debian but it didn't work for me. May be what you can do is share you wireless connexion with your wired connexion (where you can create your bridge). And play with the firewall to expose the ovirt webadmin-ui to your external network. Regards. Le dim. 22 août 2021 à 07:18, Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > a écrit : Thanks! _______________________________________________ Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://urldefense.com/v3/__https:/www.ovirt.org/privacy-policy.html__;!!AC…> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://urldefense.com/v3/__https:/www.ovirt.org/community/about/community-…> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FRZB5SQD4NOLU… <https://urldefense.com/v3/__https:/lists.ovirt.org/archives/list/users@ovir…>

1 0

Re: [External] : Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use?
by Tommy Sway 23 Aug '21

23 Aug '21

Thank you! Could you give me some guide doc ? Moreover, my use environment is only for testing functions and does not involve security issues. I just want to make full use of physical resources. From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of Marcos Sungaila Sent: Monday, August 23, 2021 9:13 PM To: wodel youchi <wodel.youchi(a)gmail.com>; Tommy Sway <sz_cuitao(a)163.com> Cc: users <users(a)ovirt.org> Subject: [ovirt-users] Re: [External] : Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use? Hi Tommy, Two comments for your appreciation: 1st: Technically, it is possible. You can configure your wireless network as a bridge and use it as you wish. I did it in my laptop a long time ago to test KVM instances. 2nd: Taking security in focus, it is not a recommendation to use wireless cards in servers. Wireless connections can be easily attacked since there is no need for someone to have logical access to your server. Regards, Marcos From: wodel youchi <wodel.youchi(a)gmail.com <mailto:wodel.youchi@gmail.com> > Sent: domingo, 22 de agosto de 2021 07:13 To: Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > Cc: users <users(a)ovirt.org <mailto:users@ovirt.org> > Subject: [External] : [ovirt-users] Re: Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use? Hi, In my little experience, no you can't, I tried that a while ago it didn't work, there is some old tutorial on Debian but it didn't work for me. May be what you can do is share you wireless connexion with your wired connexion (where you can create your bridge). And play with the firewall to expose the ovirt webadmin-ui to your external network. Regards. Le dim. 22 août 2021 à 07:18, Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> > a écrit : Thanks! _______________________________________________ Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://urldefense.com/v3/__https:/www.ovirt.org/privacy-policy.html__;!!AC…> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://urldefense.com/v3/__https:/www.ovirt.org/community/about/community-…> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FRZB5SQD4NOLU… <https://urldefense.com/v3/__https:/lists.ovirt.org/archives/list/users@ovir…>

2 1

Is it possible to configure the wireless network card on the Linux host as the bridge to provide oVirt for use?
by Tommy Sway 23 Aug '21

23 Aug '21

Thanks!

3 2

Moving datacenters & IP addresses with minimal downtime
by David White 23 Aug '21

23 Aug '21

So it looks like I'm going to move to a new datacenter. I went into somewhere cheap on a month-to-month contract earlier this year, and they've been a pain to deal with. At the same time, I've grown a lot faster than expected, so I've decided to move into a better, more reputable datacenter sooner rather than later. I currently have HCI with 3 servers. Within the cluster, I can tolerate a host "failure", so I can run on 2 servers. I have a 4th server that I haven't really been doing anything yet, but I think will be a good asset to me as I move, to keep things to a minimum. One of my production nodes, as well as my 4th server don't have the right storage, so if/when I move things, I'll need to configure Gluster to run on a single node for a time. I'd like to ask about best practices here. Before I move any hardware, I'm thinking about removing 1 of my 3 production servers from the existing HCI cluster, and installing a NEW hyperconverged single node onto this production server with Gluster storage. Then, add my 4th server to that new oVirt environment. Once I did that, I'm wondering if I could clone 100% of the VMs from the 1 environment over to the other. Once that was done, I could move one of my oVirt clusters to the new datacenter, update DNS for the virtual servers, run a final rsync, and I'm done -- then I would just move the other two servers, do a fresh install of oVirt, and add them to the new cluster. Is this possible? Is there a better way to do this move? Thanks,David Sent with ProtonMail Secure Email.

2 1

Unable to change Mail Recipient for Event Notifications
by Rodrigo G. López 23 Aug '21

23 Aug '21

Hello all, There seems to be a problem with oVirt 4.4.7.7 when modifying the Mail Recipient field in the Add Event Notification modal with the `admin' user. It defaults to `root@localhost' and I can't change it no matter what I try. It happens whether I check some Events for Notification or not, and the ovirt-engine-notifier service is also running healthily. Is this known behavior? What am I missing? I'm following §21 of the Administration Guide. Best, -rodri

2 3

I can't download console.rdp on VM Portal with Firefox
by Dominique D 20 Aug '21

20 Aug '21

I am testing the lastest version of ovirt-engine 4.4.7.7-1 before updating. when I log into the VM portal and want to download the Remote Destop file (console.rdp) from a Windows VM, the file I receive is console.vv instead of console.rdp. So I have to rename the file to console.rdp. This problem is only with firefox. Edge and google chrome don't have this problem. Do you know why ?

2 1

Faster local disk for VM
by Shantur Rathore 20 Aug '21

20 Aug '21

Hi Users, Does oVirt support node local disk cache or scratch / transient disk for faster disk access? The idea is similar to options we get on cloud where one can attach fast node local scratch disk/ssd to the VM which gets deleted when VM dies. Thanks in advance. Kind Regards, Shantur

2 1

oVirt keeps crashing
by Staniforth, Paul 20 Aug '21

20 Aug '21

Hello, today we have a server that is repeatedly crashing after a few minutes after startup. the output of systemctl status ovirt-engine.service ● ovirt-engine.service - oVirt Engine Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2021-08-20 11:52:47 BST; 30s ago Process: 6606 ExecStart=/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py --redirect-output --systemd=notify $EXTRA_ARGS start (code=exited, status=1/FAILURE) Main PID: 6606 (code=exited, status=1/FAILURE) Aug 20 11:47:12 hostname systemd[1]: Starting oVirt Engine... Aug 20 11:47:12 hostname systemd[1]: Started oVirt Engine. Aug 20 11:47:13 hostname ovirt-engine.py[6606]: 2021-08-20 11:47:13,760+0100 ovirt-engine: INFO _detectJBossVersion:186 Detecting JBoss version. Running: /usr/lib/jvm/jre-11-openjdk-11.0.11.0.> Aug 20 11:47:14 hostname ovirt-engine.py[6606]: 2021-08-20 11:47:14,676+0100 ovirt-engine: INFO _detectJBossVersion:206 Return code: 0, | stdout: '['WildFly Full 23.0.2.Final (WildFly Core 15> Aug 20 11:52:47 histname ovirt-engine.py[6606]: 2021-08-20 11:52:47,434+0100 ovirt-engine: ERROR run:542 Error: process terminated with status code 1 Aug 20 11:52:47 hostname systemd[1]: ovirt-engine.service: Main process exited, code=exited, status=1/FAILURE Aug 20 11:52:47 hostname systemd[1]: ovirt-engine.service: Failed with result 'exit-code'. Thanks for any help, Regards, Paul S. To view the terms under which this email is distributed, please go to:- https://leedsbeckett.ac.uk/disclaimer/email

1 0

Ovirt-4.4.7 Adding host to existing cluster will attempt to run ovirt-hosted-engine-setup
by Paul-Erik Törrönen 15 Aug '21

15 Aug '21

I have an existing oVirt-installation to which I want to add a new host (from the UI). However the adding fails because oVirt tries to then install the ovirt-hosted-engine-setup despite the fact that in the New host-dialog I left the Choose hosted engine deployment action as None. As a result the installation then aborts: 2021-08-15 13:17:37 EEST - TASK [ovirt-host-deploy-vdsm : Install ovirt-hosted-engine-setup package] ****** 2021-08-15 13:17:37 EEST - 2021-08-15 13:17:37 EEST - fatal: [new.host]: FAILED! => {"changed": false, "failures": ["No package ovirt-hosted-engine-setup available."], "msg": "Failed to install some of the specified packages", "rc": 1, "results": []} 2021-08-15 13:17:37 EEST - { "status" : "OK", "msg" : "", "data" : { "uuid" : "98a244fb-15da-4192-a8fc-b23a5e5b7594", "counter" : 55, "stdout" : "fatal: [new.host]: FAILED! => {\"changed\": false, \"failures\": [\"No package ovirt-hosted-engine-setup available.\"], \"msg\": \"Failed to install some of the specified packages\", \"rc\": 1, \"results\": []}", "start_line" : 47, "end_line" : 48, "runner_ident" : "fe710372-fdb1-11eb-81f0-ecf4bb63099f", "event" : "runner_on_failed", "pid" : 24931, "created" : "2021-08-15T10:17:35.963320", "parent_uuid" : "ecf4bb63-099f-2448-1b83-0000000001a7", "event_data" : { "playbook" : "ovirt-host-deploy.yml", "playbook_uuid" : "8f70f945-4008-4159-b469-7ff04c9c242b", "play" : "all", "play_uuid" : "ecf4bb63-099f-2448-1b83-000000000006", "play_pattern" : "all", "task" : "Install ovirt-hosted-engine-setup package", "task_uuid" : "ecf4bb63-099f-2448-1b83-0000000001a7", "task_action" : "yum", "task_args" : "", "task_path" : "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/packages.yml:6", "role" : "ovirt-host-deploy-vdsm", "host" : "new.host", "remote_addr" : "new.host", "res" : { "msg" : "Failed to install some of the specified packages", "failures" : [ "No package ovirt-hosted-engine-setup available." ], "results" : [ ], "rc" : 1, "invocation" : { "module_args" : { "name" : [ "ovirt-hosted-engine-setup" ], "state" : "present", "allow_downgrade" : false, "autoremove" : false, "bugfix" : false, "disable_gpg_check" : false, "disable_plugin" : [ ], "disablerepo" : [ ], "download_only" : false, "enable_plugin" : [ ], "enablerepo" : [ ], ... Poltsi

1 0

about the clonetype of the vm disk when vm is cloned from template
by Tommy Sway 14 Aug '21

14 Aug '21

There are some options for clone disk for other platform like oVirt. --clonetype [thin|full] A thin clone uses copy-on-write (COW) reflinked clone meaning it is dependent on the base template, but enables rapid cloning. Full clone will make a full physical copy hence not be dependent on the base template. Thin clone uses less space and will not be as performant as full clone, especially under heavy write workloads. By default a thin clone is created, great for testing; should be avoided in production environments. I want to know which type is oVirt using when we clone vm from template ?

2 2

Hosted engine on HCI cluster is not running
by David White 14 Aug '21

14 Aug '21

Hello, It appears that my Manager / hosted-engine isn't working, and I'm unable to get it to start. I have a 3-node HCI cluster, but right now, Gluster is only running on 1 host (so no replication). I was hoping to upgrade / replace the storage on my 2nd host today, but aborted that maintenance when I found that I couldn't even get into the Manager. The storage is mounted, but here's what I see: > [root@cha2-storage dwhite]# hosted-engine --vm-statusThe hosted engine configuration has not been retrieved from shared storage. Please ensure that ovirt-ha-agent is running and the storage server is reachable. > > [root@cha2-storage dwhite]# systemctl status ovirt-ha-agent● ovirt-ha-agent.service - oVirt Hosted Engine High Availability Monitoring Agent > Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-agent.service; enabled; vendor preset: disabled) > Active: active (running) since Fri 2021-08-13 11:10:51 EDT; 2h 44min ago > Main PID: 3591872 (ovirt-ha-agent) > Tasks: 1 (limit: 409676) > Memory: 21.5M > CGroup: /system.slice/ovirt-ha-agent.service > └─3591872 /usr/libexec/platform-python /usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent > > Aug 13 11:10:51 cha2-storage.mgt.barredowlweb.com systemd[1]: Started oVirt Hosted Engine High Availability Monitoring Agent. Any time I try to do anything like connect the engine storage, disconnect the engine storage, or connect to the console, it just sits there, and doesn't do anything, and I eventually have to ctl-c out of it. Maybe I have to be patient? When I ctl-c, I get a trackback error: > [root@cha2-storage dwhite]# hosted-engine --console^CTraceback (most recent call last): > File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main > > "__main__", mod_spec) > File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code > exec(code, run_globals) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/vdsm_helper.py", line 214, in <module> > [root@cha2-storage dwhite]# args.command(args) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/vdsm_helper.py", line 42, in func > f(*args, **kwargs) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/vdsm_helper.py", line 91, in checkVmStatus > cli = ohautil.connect_vdsm_json_rpc() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/util.py", line 472, in connect_vdsm_json_rpc > __vdsm_json_rpc_connect(logger, timeout) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/util.py", line 395, in __vdsm_json_rpc_connect > timeout=timeout) > File "/usr/lib/python3.6/site-packages/vdsm/client.py", line 154, in connect > outgoing_heartbeat=outgoing_heartbeat, nr_retries=nr_retries) > File "/usr/lib/python3.6/site-packages/yajsonrpc/stompclient.py", line 426, in SimpleClient > nr_retries, reconnect_interval) > File "/usr/lib/python3.6/site-packages/yajsonrpc/stompclient.py", line 448, in StandAloneRpcClient > client = StompClient(utils.create_connected_socket(host, port, sslctx), > File "/usr/lib/python3.6/site-packages/vdsm/utils.py", line 379, in create_connected_socket > sock.connect((host, port)) > File "/usr/lib64/python3.6/ssl.py", line 1068, in connect > self._real_connect(addr, False) > File "/usr/lib64/python3.6/ssl.py", line 1059, in _real_connect > self.do_handshake() > File "/usr/lib64/python3.6/ssl.py", line 1036, in do_handshake > self._sslobj.do_handshake() > File "/usr/lib64/python3.6/ssl.py", line 648, in do_handshake > self._sslobj.do_handshake() This is what I see in /var/log/ovirt-hosted-engine-ha/broker.log: > MainThread::WARNING::2021-08-11 10:24:41,596::storage_broker::100::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: Connection to storage server failed > MainThread::ERROR::2021-08-11 10:24:41,596::broker::69::ovirt_hosted_engine_ha.broker.broker.Broker::(run) Failed initializing the broker: Connection to storage server failed > MainThread::ERROR::2021-08-11 10:24:41,598::broker::71::ovirt_hosted_engine_ha.broker.broker.Broker::(run) Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 64, in run > self._storage_broker_instance = self._get_storage_broker() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 143, in _get_storage_broker > return storage_broker.StorageBroker() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", line 97, in __init__ > self._backend.connect() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 375, in connect > sserver.connect_storage_server() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_server.py", line 451, in connect_storage_server > 'Connection to storage server failed' > RuntimeError: Connection to storage server failed > > MainThread::ERROR::2021-08-11 10:24:41,599::broker::72::ovirt_hosted_engine_ha.broker.broker.Broker::(run) Trying to restart the broker > MainThread::INFO::2021-08-11 10:24:42,439::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run) ovirt-hosted-engine-ha broker 2.4.7 started > MainThread::INFO::2021-08-11 10:24:44,442::monitor::45::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Searching for submonitors in /usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/submonitors > MainThread::INFO::2021-08-11 10:24:44,443::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > MainThread::INFO::2021-08-11 10:24:44,449::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > MainThread::INFO::2021-08-11 10:24:44,450::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > MainThread::INFO::2021-08-11 10:24:44,451::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free > MainThread::INFO::2021-08-11 10:24:44,451::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge > MainThread::INFO::2021-08-11 10:24:44,452::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network > MainThread::INFO::2021-08-11 10:24:44,452::monitor::62::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain > MainThread::INFO::2021-08-11 10:24:44,452::monitor::63::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Finished loading submonitors And I see this in /var/log/vdsm/vdsm.log: > 2021-08-13 14:08:10,844-0400 ERROR (Reactor thread) [ProtocolDetector.AcceptorImpl] Unhandled exception in acceptor (protocoldetector:76) > Traceback (most recent call last): > File "/usr/lib64/python3.6/asyncore.py", line 108, in readwrite > File "/usr/lib64/python3.6/asyncore.py", line 417, in handle_read_event > File "/usr/lib/python3.6/site-packages/yajsonrpc/betterAsyncore.py", line 57, in handle_accept > File "/usr/lib/python3.6/site-packages/yajsonrpc/betterAsyncore.py", line 173, in _delegate_call > File "/usr/lib/python3.6/site-packages/vdsm/protocoldetector.py", line 53, in handle_accept > File "/usr/lib64/python3.6/asyncore.py", line 348, in accept > File "/usr/lib64/python3.6/socket.py", line 205, in accept > OSError: [Errno 24] Too many open files Can anyone help? Sent with ProtonMail Secure Email.

2 3

[ANN] oVirt 4.4.8 Fifth Release Candidate is now available for testing
by Lev Veyde 13 Aug '21

13 Aug '21

oVirt 4.4.8 Fifth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.8 Fifth Release Candidate for testing, as of August 13th, 2021. This update is the eighth in a series of stabilization updates to the 4.4 series. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 * oVirt Node 4.4 based on CentOS Stream 8 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available based on CentOS Stream 8 - oVirt Node NG is already available based on CentOS Stream 8 Additional Resources: * Read more about the oVirt 4.4.8 release highlights: http://www.ovirt.org/release/4.4.8/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.8/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Unable to connect to the Graphic server
by Gangi Reddy 13 Aug '21

13 Aug '21

We are receiving below error while attempt to connect SPICE console. No block in network firewall. Version: Software Version:4.4.6.7-1.el8 Error: Unable to connect to the Graphic server .vv

1 1

Automigration of VMs from other hypervisors
by KK CHN 11 Aug '21

11 Aug '21

Hi list, I am in the process of migrating 150+ VMs running on Rhevm4.1 to KVM based OpenStack installation ( Ussuri with KVm and glance as image storage.) What I am doing now, manually shutdown each VM through RHVM GUI and export to export domain and scp those image files of each VM to our OpenStack controller node and uploading to glance and creating each VM manually. query 1. Is there a better way to automate this migration by any utility or scripts ? Any one done this kind of automatic migration before what was your approach? Or whats the better approach instead of doing manual migration ? Or only manually I have to repeat the process for all 150+ Virtual machines? ( guest VMs are CentOS7 and Redhat Linux 7 with LVM data partitions attached) Kindly share your thoughts.. Query 2. other than this 150+ VMs Redhat Linux 7 and Centos VMs on Rhevm 4.1, I have to migrate 50+ VMs which hosted on hyperV. What the method / approach for exporting from HyperV and importing to OpenStack Ussuri version with glance with KVM hpervisor ? ( This is the ffirst time I am going to use hyperV, no much idea about export from hyperv and Import to KVM) Will the images exported form HyperV(vhdx image disks with single disk and multiple disk(max 3 disk) VMs) can be directly imported to KVM ? does KVM support this or need to modify vhdx disk images to any other format ? What is the best approach should be in case of HyperV hosted VMs( Windows 2012 guest machines and Linux guest machines ) to be imported to KVM based OpenStack(Ussuri version with glance as image storage ). Thanks in advance Kris

1 0

Ubuntu 20.04 cloud-init
by Pavel Šipoš 11 Aug '21

11 Aug '21

Hi. We are using oVirt version 4.3.10.4-1.el7 I am trying to use clod-init function in ovirt to set password and add ssh keys for VM on first boot. It is working perfectly on Centos7, Centos8, but not with Ubuntu 20.04.02 . On VM Cloud-init package and quemu-guest-agent are installed, services are running - I checked that and then used Run once to test further but no luck. It looks like its not even trying to set anything. I am open to suggestions how to debug this. I see no errors if I look into /var/log/cloud-init logs on VM. Did anyone else had similar problem? Can anyone confirm that cloud-init function in ovirt should work with ubuntu 20.04? Packages used: cloud-init 21.2-3-g899bfaa9-0ubuntu2~20.04.1 qemu-guest-agent 1:4.2-3ubuntu6.17 I made ovirt template myself using packer (qemu) that also uses cloud-init for bootstrapping. Thank you in advance! Pavel -- -- Pavel Sipos, Arnes <pavel.sipos(a)arnes.si> ARNES, p.p. 7, SI-1001 Ljubljana, Slovenia T: +386 1 479 88 00 W: www.arnes.si, aai.arnes.si

2 2

low iscsi storage space
by Leonardo Costa 10 Aug '21

10 Aug '21

Hello. I'm having a problem that I can't solve, I have 20Tb of space on Ovirt but on my DELL SCV 3000 storage, only 5Tb free on the volume. It seems to me that the deleted machines are not removing the disks in the storage iscsi. Could anyone help?

2 1

Major network issue with 4.4.7
by Andrea Chierici 10 Aug '21

10 Aug '21

Dear all, I've been using ovirt for at least 6 years and only lately I've stepped into a weird problem that I hope someone will be able to give help. My hardware is: - blade lenovo for hosts, with dual switch - dell equallogic for iscsi storage, directly connected to the blade switches - The two host network cards are configured with bonding and all the vlans are accessed from it (mtu 9000) - all the hosts and ovirt engine have firewalld service disabled) My engine is hosted on a separate vmware vm (I will evaluate the self hosted engine later...). I want to stress the fact that for years this setup worked smoothly without any significant issue (and all the minor updates were completed flawlessly). A few weeks ago I started the update from the rock solid 4.3 to the latest 4.4.7. I began with the manager, following the docs, installing a new centos8 vm and importing the backup: everything went smootly and I was able to get access to the manager without any problem, all the machines still there :) I then began updating the hosts, from centos7 to centos8 stream, one by one. Immediately I noticed network issues, with the VMs hosted on the first updated host. Migrating VMs from centos8 host to other centos8 quite often fails, but the main issue is this: *if I start one of the VMs on the centos8 host, they have no network connectivity. If I migrate them to a centos7 hosts the network starts to work, and if I migrate the VMs back to the centos8 host, the network keeps working.* I am puzzled and can't understand what's going on. Generally speaking all the centos8 hosts (I have 6 in my cluster, and now 3 are centos8 while the rest is still centos7) seem to be very unstable, meaning that the VMs they host are quite often showing network issues and temporary glitches. Can someone give a hint on how to solve this weird issue? Thanks, Andrea -- Andrea Chierici - INFN-CNAF Viale Berti Pichat 6/2, 40127 BOLOGNA Office Tel: +39 051 2095463 SkypeID ataruz --

3 4

live merge of snapshots failed
by g.vasilopoulos＠uoc.gr 10 Aug '21

10 Aug '21

Hello I have a situation with a vm in which I cannot delete the snapshot. The whole thing is quite strange because I can delete the snapshot when I create and delete it from the web interface but when I do it with a python script through the API it failes. The script does create snapshot-> download snapshot-> delete snapshot and I used the examples from ovirt python sdk on githab to create it ,in general it works prety well. But on a specific machine (so far) it cannot delete the live snapshot Ovirt is 4.3.10 and the guest is a windows 10 pc. Windows 10 guest has 2 disks attached both on different fc domains one on an ssd emc and the other on an hdd emc. Both disks are prealocated. I cannot figure out what the problem is so far the related engine log: 2021-08-03 15:51:00,385+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-61) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Comma nd 'RemoveSnapshotSingleDiskLive' (id: '80dc4609-b91f-4e93-bc12-7b2083933e5a') waiting on child command id: '74c83880-581b-4774-ae51-8c4af0c92c53' type:'Merge' to complete 2021-08-03 15:51:00,385+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-61) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on merge command to complete ( jobId = 62bf8c83-cd78-42a5-b57d-d67ddfdee8ee) 2021-08-03 15:51:00,387+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-61) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '87bc90c7-2aa5-4a1b-b58c-54296518658a') waiting on child command id: 'ec806ac6-929f-42d9-a86e-98d6a39a4718' type:'Merge' to complete 2021-08-03 15:51:01,388+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-30) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on merge command to complete (jobId = c57fb3e5-da20-4838-8db3-31655ba76c1f) 2021-08-03 15:51:07,491+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-38) [b929fd4a-8ce7-408f-927d-ab0169879c4e] Command 'MoveImageGroup' (id: '1de1b800-873f-405f-805b-f44397740909') waiting on child command id: 'd1136344-2888-4d63-8fe1-b506426bc8aa' type:'CopyImageGroupWithData' to complete 2021-08-03 15:51:11,513+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-41) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshot' (id: '04e9d61e-28a2-4ab0-9bb7-5c805ee871e9') waiting on child command id: '87bc90c7-2aa5-4a1b-b58c-54296518658a' type:'RemoveSnapshotSingleDiskLive' to complete 2021-08-03 15:51:12,522+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '80dc4609-b91f-4e93-bc12-7b2083933e5a') waiting on child command id: '74c83880-581b-4774-ae51-8c4af0c92c53' type:'Merge' to complete 2021-08-03 15:51:12,523+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on merge command to complete (jobId = 62bf8c83-cd78-42a5-b57d-d67ddfdee8ee) 2021-08-03 15:51:12,527+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '87bc90c7-2aa5-4a1b-b58c-54296518658a') waiting on child command id: 'ec806ac6-929f-42d9-a86e-98d6a39a4718' type:'Merge' to complete 2021-08-03 15:51:13,528+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-37) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on merge command to complete (jobId = c57fb3e5-da20-4838-8db3-31655ba76c1f) 2021-08-03 15:51:21,635+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-58) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshot' (id: '04e9d61e-28a2-4ab0-9bb7-5c805ee871e9') waiting on child command id: '87bc90c7-2aa5-4a1b-b58c-54296518658a' type:'RemoveSnapshotSingleDiskLive' to complete 2021-08-03 15:51:22,655+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '80dc4609-b91f-4e93-bc12-7b2083933e5a') waiting on child command id: '74c83880-581b-4774-ae51-8c4af0c92c53' type:'Merge' to complete 2021-08-03 15:51:22,661+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Merge command (jobId = 62bf8c83-cd78-42a5-b57d-d67ddfdee8ee) has completed for images '7611ebcf-5323-45ca-b16c-9302d0bdedc6'..'17618ba1-4ab8-49eb-a991-fc3d602ced14' 2021-08-03 15:51:22,664+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '87bc90c7-2aa5-4a1b-b58c-54296518658a') waiting on child command id: 'ec806ac6-929f-42d9-a86e-98d6a39a4718' type:'Merge' to complete 2021-08-03 15:51:23,664+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-41) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on merge command to complete (jobId = c57fb3e5-da20-4838-8db3-31655ba76c1f) 2021-08-03 15:51:24,672+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-6) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Executing Live Merge command step 'MERGE_STATUS' 2021-08-03 15:51:24,699+03 INFO [org.ovirt.engine.core.bll.MergeStatusCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Running command: MergeStatusCommand internal: true. Entities affected : ID: 96000ec9-e181-44eb-893f-e0a36e3a6775 Type: Storage 8-03 15:51:24,749+03 INFO [org.ovirt.engine.core.bll.MergeStatusCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Successfully removed volume 17618ba1-4 ab8-49eb-a991-fc3d602ced14 from the chain 2021-08-03 15:51:24,749+03 INFO [org.ovirt.engine.core.bll.MergeStatusCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Volume merge type 'COMMIT' 2021-08-03 15:51:25,691+03 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-5) [b929fd4a-8ce7-408f-927d-ab0169879c4e] Command 'CopyImageGroup WithData' (id: 'd1136344-2888-4d63-8fe1-b506426bc8aa') waiting on child command id: 'b40aeec9-b7cf-4ee5-9683-54d98f4307d5' type:'CopyImageGroupVolumesData' to complete 2021-08-03 15:51:26,692+03 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-35) [b929fd4a-8ce7-408f-927d-ab0169879c4e] Command 'CopyImageGrou pVolumesData' (id: 'b40aeec9-b7cf-4ee5-9683-54d98f4307d5') waiting on child command id: 'f46d65cb-32d9-4269-982e-6e19331b8a27' type:'CopyData' to complete 2021-08-03 15:51:26,711+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-35) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Executing Liv e Merge command step 'DESTROY_IMAGE' 2021-08-03 15:51:26,726+03 INFO [org.ovirt.engine.core.bll.storage.disk.image.DestroyImageCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Running command: DestroyImageCommand internal: true. Entities affected : ID: 96000ec9-e181-44eb-893f-e0a36e3a6775 Type: Storage 2021-08-03 15:51:26,747+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DestroyImageVDSCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] START, DestroyIma geVDSCommand( DestroyImageVDSCommandParameters:{storagePoolId='5da76866-7b7d-11eb-9913-00163e1f2643', ignoreFailoverLimit='false', storageDomainId='96000ec9-e181-44eb-893f-e0a36e3a6775', imageGroupId='205a30a3-f c06-4ceb-8ef2-018f16d4ccbb', imageId='00000000-0000-0000-0000-000000000000', imageList='[17618ba1-4ab8-49eb-a991-fc3d602ced14]', postZero='false', force='false'}), log id: 307a3fb1 2021-08-03 15:51:26,834+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DestroyImageVDSCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] FINISH, DestroyIm ageVDSCommand, return: , log id: 307a3fb1 2021-08-03 15:51:26,846+03 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] CommandAsyncTask::Adding CommandM ultiAsyncTasks object for command 'baaa5254-261c-452a-84b4-0a8b397cdb62' 2021-08-03 15:51:26,847+03 INFO [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] CommandMultiAsyncTasks::attachTas k: Attaching task 'ae2e80a4-d224-4fc3-a84b-859042811525' to command 'baaa5254-261c-452a-84b4-0a8b397cdb62'. 2021-08-03 15:51:26,857+03 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Adding task 'ae2e80a4-d224-4fc3-a 84b-859042811525' (Parent Command 'DestroyImage', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling hasn't started yet.. 2021-08-03 15:51:26,858+03 INFO [org.ovirt.engine.core.bll.storage.disk.image.DestroyImageCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Successfully star ted task to remove orphaned volumes 2021-08-03 15:51:26,863+03 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] BaseAsyncTask::startPollingTask: Star ting to poll task 'ae2e80a4-d224-4fc3-a84b-859042811525'. 2021-08-03 15:51:26,863+03 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-commandCoordinator-Thread-10) [3bf9345d-fab2-490f-ba44-6aa014bbb743] BaseAsyncTask::startPollingTask: Star ting to poll task 'ae2e80a4-d224-4fc3-a84b-859042811525'. 2021-08-03 15:51:28,799+03 INFO [org.ovirt.engine.core.bll.storage.disk.image.DestroyImageCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-88) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on destroy image command to complete the task (taskId = ae2e80a4-d224-4fc3-a84b-859042811525) 2021-08-03 15:51:30,805+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-48) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '80dc4609-b91f-4e93-bc12-7b2083933e5a') waiting on child command id: 'baaa5254-261c-452a-84b4-0a8b397cdb62' type:'DestroyImage' to complete 2021-08-03 15:51:31,824+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-97) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshot' (id: '04e9d61e-28a2-4ab0-9bb7-5c805ee871e9') waiting on child command id: '87bc90c7-2aa5-4a1b-b58c-54296518658a' type:'RemoveSnapshotSingleDiskLive' to complete 2021-08-03 15:51:32,825+03 INFO [org.ovirt.engine.core.bll.storage.disk.image.DestroyImageCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Waiting on destroy image command to complete the task (taskId = ae2e80a4-d224-4fc3-a84b-859042811525) 2021-08-03 15:51:32,831+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' (id: '87bc90c7-2aa5-4a1b-b58c-54296518658a') waiting on child command id: 'ec806ac6-929f-42d9-a86e-98d6a39a4718' type:'Merge' to complete 2021-08-03 15:51:33,594+03 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'DestroyImage' completed, handling the result. 2021-08-03 15:51:33,594+03 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'DestroyImage' succeeded, clearing tasks. 2021-08-03 15:51:33,594+03 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] SPMAsyncTask::ClearAsyncTask: Attempting to clear task 'ae2e80a4-d224-4fc3-a84b-859042811525' 2021-08-03 15:51:33,595+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='5da76866-7b7d-11eb-9913-00163e1f2643', ignoreFailoverLimit='false', taskId='ae2e80a4-d224-4fc3-a84b-859042811525'}), log id: 6225ae22 2021-08-03 15:51:33,596+03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] START, HSMClearTaskVDSCommand(HostName = ovirt2-7.vmmgmt-int.uoc.gr, HSMTaskGuidBaseVDSCommandParameters:{hostId='10599b78-5f45-48d2-bfe0-028f3dae69eb', taskId='ae2e80a4-d224-4fc3-a84b-859042811525'}), log id: 45b18a8a 2021-08-03 15:51:33,611+03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] FINISH, HSMClearTaskVDSCommand, return: , log id: 45b18a8a 2021-08-03 15:51:33,611+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] FINISH, SPMClearTaskVDSCommand, return: , log id: 6225ae22 2021-08-03 15:51:33,614+03 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] BaseAsyncTask::removeTaskFromDB: Removed task 'ae2e80a4-d224-4fc3-a84b-859042811525' from DataBase 2021-08-03 15:51:33,614+03 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1481337) [3bf9345d-fab2-490f-ba44-6aa014bbb743] CommandAsyncTask::HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks object for entity 'baaa5254-261c-452a-84b4-0a8b397cdb62' 2021-08-03 15:51:33,839+03 INFO [org.ovirt.engine.core.bll.MergeCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-95) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Merge command (jobId = c57fb3e5-da20-4838-8db3-31655ba76c1f) has completed for images '84c005da-cbec-4ace-8619-5a8e2ae5ea75'..'b43b7c33-5b53-4332-a2e0-f950debb919b' 2021-08-03 15:51:34,847+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Executing Live Merge command step 'MERGE_STATUS' 2021-08-03 15:51:34,917+03 ERROR [org.ovirt.engine.core.bll.MergeStatusCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Failed to live merge. Top volume b43b7c33-5b53-4332-a2e0-f950debb919b is still in qemu chain [b43b7c33-5b53-4332-a2e0-f950debb919b, 84c005da-cbec-4ace-8619-5a8e2ae5ea75] 2021-08-03 15:51:35,866+03 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-41) [b929fd4a-8ce7-408f-927d-ab0169879c4e] Command 'CopyImageGroupWithData' (id: 'd1136344-2888-4d63-8fe1-b506426bc8aa') waiting on child command id: 'b40aeec9-b7cf-4ee5-9683-54d98f4307d5' type:'CopyImageGroupVolumesData' to complete 2021-08-03 15:51:36,867+03 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-50) [b929fd4a-8ce7-408f-927d-ab0169879c4e] Command 'CopyImageGroupVolumesData' (id: 'b40aeec9-b7cf-4ee5-9683-54d98f4307d5') waiting on child command id: 'f46d65cb-32d9-4269-982e-6e19331b8a27' type:'CopyData' to complete 2021-08-03 15:51:36,873+03 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-50) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command id: '87bc90c7-2aa5-4a1b-b58c-54296518658a failed child command status for step 'MERGE_STATUS' 2021-08-03 15:51:36,873+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-50) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' id: '87bc90c7-2aa5-4a1b-b58c-54296518658a' child commands '[a7de75fe-e94c-4795-9310-2c8fc3d6d3fc, ec806ac6-929f-42d9-a86e-98d6a39a4718, 6443529c-d753-48f6-8a9e-af1f9f09dfb5]' executions were completed, status 'FAILED' 2021-08-03 15:51:37,982+03 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-22) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Merging of snapshot '1cd4985b-b0c0-40d6-bbde-54451e43bef6' images '84c005da-cbec-4ace-8619-5a8e2ae5ea75'..'b43b7c33-5b53-4332-a2e0-f950debb919b' failed. Images have been marked illegal and can no longer be previewed or reverted to. Please retry Live Merge on the snapshot to complete the operation. 2021-08-03 15:51:37,985+03 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-22) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand' with failure. 2021-08-03 15:51:39,014+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Executing Live Merge command step 'REDUCE_IMAGE' 2021-08-03 15:51:39,029+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [3bf9345d-fab2-490f-ba44-6aa014bbb743] No need to execute reduce image command, skipping its execution. Storage Type: 'FCP', Disk: 'anova.admin.uoc.gr_Disk2' Snapshot: 'anova.admin.uoc.gr-2021-08-03' 2021-08-03 15:51:39,034+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshotSingleDiskLive' id: '80dc4609-b91f-4e93-bc12-7b2083933e5a' child commands '[18653ea6-166c-41a3-b335-84525871b9e6, 74c83880-581b-4774-ae51-8c4af0c92c53, 92e92d8e-b099-47dd-ba8c-e3db907f9a62, baaa5254-261c-452a-84b4-0a8b397cdb62]' executions were completed, status 'SUCCEEDED' 2021-08-03 15:51:39,040+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-23) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshot' (id: '04e9d61e-28a2-4ab0-9bb7-5c805ee871e9') waiting on child command id: '80dc4609-b91f-4e93-bc12-7b2083933e5a' type:'RemoveSnapshotSingleDiskLive' to complete 2021-08-03 15:51:40,046+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] START, GetImageInfoVDSCommand( GetImageInfoVDSCommandParameters:{storagePoolId='5da76866-7b7d-11eb-9913-00163e1f2643', ignoreFailoverLimit='false', storageDomainId='96000ec9-e181-44eb-893f-e0a36e3a6775', imageGroupId='205a30a3-fc06-4ceb-8ef2-018f16d4ccbb', imageId='7611ebcf-5323-45ca-b16c-9302d0bdedc6'}), log id: 4c98e4db 2021-08-03 15:51:40,047+03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] START, GetVolumeInfoVDSCommand(HostName = ovirt2-7.vmmgmt-int.uoc.gr, GetVolumeInfoVDSCommandParameters:{hostId='10599b78-5f45-48d2-bfe0-028f3dae69eb', storagePoolId='5da76866-7b7d-11eb-9913-00163e1f2643', storageDomainId='96000ec9-e181-44eb-893f-e0a36e3a6775', imageGroupId='205a30a3-fc06-4ceb-8ef2-018f16d4ccbb', imageId='7611ebcf-5323-45ca-b16c-9302d0bdedc6'}), log id: 4aca5f83 2021-08-03 15:51:40,084+03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] FINISH, GetVolumeInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.DiskImage@70097e6, log id: 4aca5f83 2021-08-03 15:51:40,084+03 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] FINISH, GetImageInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.DiskImage@70097e6, log id: 4c98e4db 2021-08-03 15:51:40,283+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Successfully merged snapshot '1cd4985b-b0c0-40d6-bbde-54451e43bef6' images '17618ba1-4ab8-49eb-a991-fc3d602ced14'..'7611ebcf-5323-45ca-b16c-9302d0bdedc6' 2021-08-03 15:51:40,287+03 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand' successfully. 2021-08-03 15:51:40,296+03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Command 'RemoveSnapshot' id: '04e9d61e-28a2-4ab0-9bb7-5c805ee871e9' child commands '[87bc90c7-2aa5-4a1b-b58c-54296518658a, 80dc4609-b91f-4e93-bc12-7b2083933e5a]' executions were completed, status 'FAILED' 2021-08-03 15:51:41,322+03 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-65) [3bf9345d-fab2-490f-ba44-6aa014bbb743] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand' with failure. 2021-08-03 15:51:41,353+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-65) [3bf9345d-fab2-490f-ba44-6aa014bbb743] EVENT_ID: USER_REMOVE_SNAPSHOT_FINISHED_FAILURE(357), Failed to delete snapshot 'anova.admin.uoc.gr-2021-08-03' for VM 'anova.admin.uoc.gr'. Any help would be highly appreciated

3 8