August 2022 - Users - oVirt List Archives

Q: "vdsm-client Host getAllTasksInfo" Fails (Removing frozen task)
by Andrei Verovski 04 Aug '22

04 Aug '22

Hi, I have frozen task (creating snapshot) on one of my oVirt nodes, and trying to kill it. However, # sudo vdsm-client Host getAllTasksInfo vdsm-client: Command Host.getAllTasksInfo with args {} failed: However, sudo "vdsm-client Host getVMList” and "sudo vdsm-client Host getVMFullList" working fine. # /usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -v -Z select exists (select * from information_schema.tables where table_schema = 'public' and table_name = 'command_entities'); t SELECT command_id,command_type,root_command_id,command_parameters,command_params_class,created_at,status,return_value,return_value_class,executed FROM GetAllCommandsWithZombieTasks(); So only letter “t” is printed and it is not clear what does it mean. I can run "/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh -vR” but not sure its not too destructive. What is the problem with "vdsm-client Host getAllTasksInfo” ? Thanks in advance. Andrei

1 1

Re: Single Peer in Gluster Cluster Failure caused Storage Domain outage
by Simon Scott 04 Aug '22

04 Aug '22

Typo - the server would only boot into ‘emergency’ mode.

2 1

Host certificate expired
by Rob B 04 Aug '22

04 Aug '22

Hi, We have a ovirt host in a 'Unassigned' state because its certificate has expired. The ovirt events show... VDSM host1 command Get Host Capabilities failed: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed This is the only host in the cluster, and has local storage so I don't have any options to start the single VM elsewhere. Is there a way to renew the certificate on this host? I have no option to put the host in maintenance mode and 'Enroll Certificate' as its in the unassigned state. The oVirt manager is running version: 4.4.10.7-1.el8 The oVirt host in the bad state is running: ovirt-host-4.4.9-2, vdsm-4.40.100.2-1. Please let me know if you need any more info, and thanks in advance. Rob

2 2

HostedEngine Restore woes
by simon＠justconnect.ie 04 Aug '22

04 Aug '22

Hi All, I've been asked to test the HE restore process but after taking a look at the documentation I'm afraid I'm none the wiser. I thought there would be a simple 'restore in situ' option but it appears not. My environments were build using ansible with a hostedengine .json answer file. From what I've read so far it appears that a new HE VM needs to be built with new engine storage etc

2 4

Re: Six node HCI
by Strahil Nikolov 03 Aug '22

03 Aug '22

It would make more sense to odentify the root cause.Can you check if all oVirt nodes are in the TSP:gluster pool listAlso, check that the Engine's volume is available from all nodes -> should be mounted and listable:ls -l /rhev/data-center/mnt/glusterSD/<host>:_<volume name> Best Regards,Strahil Nikolov On Tue, Aug 2, 2022 at 8:45, Gaurang Patel<gaurang.patel(a)allotgroup.com> wrote:  Hi, I am very new to Ovirt 6 Node Gluster. We can create three node cluster successfully with the 4.5.1 version but after expanding the gluster cluster with additional 3 nodes, Ovirt-engine is going to not responding mode. If you can help me with step by step document would be very greatful to us. Thank in advance. Gaurang Patel DISCLAIMER : The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future._______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/S7KBUPG2KPX65…

1 1

[ANN] oVirt 4.5.2 First Release Candidate is now available for testing
by Lev Veyde 03 Aug '22

03 Aug '22

oVirt 4.5.2 First Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.5.2 First Release Candidate for testing, as of August 3rd, 2022. This update is the second in a series of stabilization updates to the 4.5 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: - CentOS Stream 8 - RHEL 8.6 and derivatives This release supports Hypervisor Hosts on x86_64: - oVirt Node NG (based on CentOS Stream 8) - CentOS Stream 8 - RHEL 8.6 and derivatives Builds are also available for ppc64le and aarch64. Experimental builds for CentOS Stream 9 are also provided for Hypervisor Hosts. 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.5.2 pre-release highlights: http://www.ovirt.org/release/4.5.2/ * 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.5.1/ [2] http://resources.ovirt.org/pub/ovirt-4.5-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

Moving raw/sparse disk from NFS to iSCSI fails on oVirt 4.5.1
by Guillaume Pavese 03 Aug '22

03 Aug '22

On a 4.5.1 DC, I have imported a vm and its disk from an old 4.3 DC (through an export domain if that's relevant) The DC/Cluster compat level is 4.7 and the vm was upgraded to it. "Original custom compatibility version 4.3 of imported VM xxx is not supported. Changing it to the lowest supported version: 4.7." The disk is raw and sparse : <format>raw</format> <sparse>true</sparse> I initially put the VM's disks on an NFS storage domain, but I want to move the disks to an iSCSI one However, after copying data for a while the task fails "User has failed to move disk VM-TEMPLATE-COS7_Disk1 to domain iSCSI-STO-FR-301" in engine.log : qemu-img: error while writing at byte xxx: No space left on device 2022-07-21 08:58:23,240+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHostJobsVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-48) [65fed1dc-e33b-471e-bc49-8b9662400e5f] FINISH, GetHostJobsVDSCommand, return: {0aa2d519-8130-4e2f-bc4f-892e5f7b5206=HostJobInfo:{id='0aa2d519-8130-4e2f-bc4f-892e5f7b5206', type='storage', description='copy_data', status='failed', progress='79', error='VDSError:{code='GeneralException', message='General Exception: ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f', 'raw', '-O', 'qcow2', '-o', 'compat=1.1', '/rhev/data-center/mnt/svc-int-prd-sto-fr-301.hostics.fr:_volume1_ovirt-int-2_data/1ce95c4a-2ec5-47b7-bd24-e540165c6718/images/d3c33cc7-f2c3-4613-84d0-d3c9fa3d5ebd/2c4a0041-b18b-408f-9c0d-971c19a552ea', '/rhev/data-center/mnt/blockSD/b5dc9c01-3749-4326-99c5-f84f683190bd/images/d3c33cc7-f2c3-4613-84d0-d3c9fa3d5ebd/2c4a0041-b18b-408f-9c0d-971c19a552ea'] failed with rc=1 out=b'' err=bytearray(b'qemu-img: error while writing at byte 13639873536: No space left on device\\n')",)'}'}}, log id: 73f77495 2022-07-21 08:58:23,241+02 INFO [org.ovirt.engine.core.bll.StorageJobCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-48) [65fed1dc-e33b-471e-bc49-8b9662400e5f] Command CopyData id: '521bdf57-8379-40ce-a682-af859fb0cad7': job '0aa2d519-8130-4e2f-bc4f-892e5f7b5206' execution was completed with VDSM job status 'failed' I do want the conversion from raw/sparse to qcow2/sparse to happen, as I want to activate incremental backups. I think that it may fail because the virtual size is bigger than the initial size, as I think someone as explained on this list earlier? Can anybody confirm? It seems to be a pretty common use case to support though? Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group -- Ce message et toutes les pièces jointes (ci-après le “message”) sont établis à l’intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d’en avertir immédiatement l’expéditeur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L’internet ne permettant pas d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales) décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse ou il aurait été modifié. IT, ES, UK. <https://interactiv-group.com/disclaimer.html>

1 2

The node host enters emergency mode
by BJ一哥 02 Aug '22

02 Aug '22

ovirt 4.5.1 After the kernel SR-IOV is started and the host is restarted, the host will enter emergency mode. When journalctl -xb is used, the engine mount fails mount:/gluster_bricks/engine:mount(2)system call failed:structure needs cleaning You need to manually annotate /etc/fstab to mount the engine volume to enter the system normally. https://s1.328888.xyz/2022/08/03/OomMy.png

1 0

Issue with oVirt 4.5 and Data Warehouse installed on a Separate Machine
by Igor Davidoff 02 Aug '22

02 Aug '22

Hi Didi, the logfile is attached. Best Regards, Igor

2 6

Questions about old plan for engine-vdsm communication
by Hyunwoo Kim 02 Aug '22

02 Aug '22

hello, I have some questions about the old plan ( https://www.ovirt.org/develop/release-management/features/infra/jsonrpc.html ) 1. any reason ovirt stays on phase 2 for years? (please reason for the cancellation if canceled) 2. In the final plan (phase 5), what was the purpose of separating the VDSM subsystems? Is it for performance or any other reason?? 3. any special reason like openstack integration the AMQP was adopted as the main messaging protocol in the plan? Thanks,

1 0