Q: "vdsm-client Host getAllTasksInfo" Fails (Removing frozen task)
by Andrei Verovski
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 year, 8 months
Host certificate expired
by Rob B
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
1 year, 8 months
HostedEngine Restore woes
by simon＠justconnect.ie
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
1 year, 8 months
Re: Six node HCI
by Strahil Nikolov
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: <!--#yiv2856725588 _filtered {} _filtered {} _filtered {}#yiv2856725588 #yiv2856725588 p.yiv2856725588MsoNormal, #yiv2856725588 li.yiv2856725588MsoNormal, #yiv2856725588 div.yiv2856725588MsoNormal {margin:0cm;font-size:11.0pt;font-family:"Calibri", sans-serif;}#yiv2856725588 span.yiv2856725588EmailStyle17 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv2856725588 .yiv2856725588MsoChpDefault {font-family:"Calibri", sans-serif;} _filtered {}#yiv2856725588 div.yiv2856725588WordSection1 {}-->
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/S7KBUPG2KPX...
1 year, 8 months
Moving raw/sparse disk from NFS to iSCSI fails on oVirt 4.5.1
by Guillaume Pavese
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 year, 8 months
The node host enters emergency mode
by BJ一哥
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 year, 8 months
