September 2019 - Users - Ovirt List Archives

by smidhunraj＠gmail.com

Hi, I tried to take incremental backup of a vm using this script. public function downloadDiskIncremental(){ $data=array(); $xmlStr = "<disk_attachment> <disk id='1371afdd-91d4-4bc7-9792-0efbf6bbd1c9'> <backup>incremental</backup> </disk> </disk_attachment>"; $curlParam=array( "url" => "vms/4044e014-7e20-4dbc-abe5-64690ec45f63/diskattachments", "method" => "POST", "data" =>$xmlStr, ); } But it is throwing me error as Array ( [status] => error [message] => For correct usage, see: https://ovirt.bobcares.com/ovirt-engine/api/v4/model#services/disk-attach... Please help me with this issue....

4 years, 6 months

2
1
0 / 0

change connection string in db

by olaf.buitelaar＠gmail.com

Dear oVirt users, I'm currently migrating our gluster setup, so i've done a gluster replace brick to the new machines. Now i'm trying to update the connection strings of the related storage domains including the one hosting the ovirt-engine (which i believe cannot be brought down for maintenance). At the same time i'm trying to disable the "Use managed gluster volume" feature. i've had tested this in a lab setup, but somehow i'm running into issues on the actual setup. On the lab setup it was enough to run a query like this; UPDATE public.storage_server_connections SET "connection"='10.201.0.6:/ovirt-kube',gluster_volume_id=NULL,mount_options='backup-volfile-servers=10.201.0.1:10.201.0.2:10.201.0.3:10.201.0.5:10.201.0.4:10.201.0.7:10.201.0.8:10.201.0.9' WHERE id='29aae3ce-61e4-4fcd-a8f2-ab0a0c07fa48'; on the live setup i also seem to run a query like this; UPDATE public.gluster_volumes SET task_id=NULL WHERE id='9a552d7a-8a0d-4bae-b5a2-1cb8a7edf5c9'; i couldn't really find where this task_id relates to, but it does make the checkbox for "Use managed gluster volume" being unchecked in the web interface. in the lab setup it was enough to run within the hosted engine; - service ovirt-engine restart and then bring an ovirt-host machine to maintenance, and active it again. and the changed connection string was being mounted in the /rhev/data-center/mnt/glusterSD/ directory. Also the vm's after being shutdown and brought up again, started using the new connection string. But now on the production instance, when i restart the engine the connection string is restored to the original values in the storage_server_connections table. I don't really understand where the engine gathers this information from. Any advice on how to actually change the connection strings would by highly appreciated. Thanks Olaf

4 years, 6 months

1
3
0 / 0

Creating vm from snapshot via API

by Aleksei Ivanovich

Hi. I'm trying to create vm from a snapshot using API. If I just provide the new vm name, source snapshot ID and cluster name the new vm is been created successfully on the same storage domain. But if I additionally provide diskattachments to create it on another storage I get error: "Cannot add VM. One or more provided storage domains are either not in active status or of an illegal type for the requested operation". I can't find the reason why I can't create vm on another storage via API while I can do the same via web-portal. My oVirt Engine version is 4.1.1.8-1.el7.centos. Here is my code: curl.exe -k -u "user@domain.suffix:*************" -H "Content-Type: application/xml" -H "Accept: application/xml" -X POST https://192.168.0.1/ovirt-engine/api/vms -d "<vm><name>vm-Test1</name><snapshots><snapshot id=\"4b73c79b-efed-4362-8843-91f5cc2d9775\"/></snapshots><cluster><name>MyCluster</name></cluster><disk_attachments><disk_attachment><disk><image_id>6525c157-4e73-440b-adc8-596f1d03ef3c</image_id><storage_domains><storage_domain id=\"52a003d7-cec1-473e-b521-1a551f55abd1\"/></storage_domains></disk></disk_attachment></disk_attachments></vm>" The answer is: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <fault> <detail>[Cannot add VM. One or more provided storage domains are either not in active status or of an illegal type for the requested operation.]</detail> <reason>Operation Failed</reason> </fault>

4 years, 6 months

1
2
0 / 0

Re: Ovirt 4.2.7 won't start and drops to emergency console

by Strahil

What happens when it complain that there is no VGs ? When you run 'vgs' what is the output? Also, take a look into https://www.redhat.com/archives/linux-lvm/2016-February/msg00012.html I have the feeling that you need to disable all lvs - not only the thin pool, but also the thin LVs (first). Best Regards, Strahil NikolovOn Sep 29, 2019 23:00, jeremy_tourville(a)hotmail.com wrote: > > Yes, I can take the downtime. Actually, I don't have any choice at the moment because it is a single node setup. :) I think this is a distributed volume from the research I have performed. I posted the lvchange command in my last post, this was the result- I ran the command lvchange -an /dev/gluster_vg1/lv_datadisks When I do this I get the message "Volume group "gluster_vg1" not found. Cannot process volume group gluster_vg1". I also tried the command the way you specified with just the LV and get the same results. > > I had placed the system in Global maintenance mode prior to the reboot. Upon reboot I got the messages about the various gluster volumes not being able to be mounted because of timeout issues. That is what started my OP. I think we are both thinking along the same lines regarding the issue. I think the question is how do you fix a volume that the system won't mount? It does seem likely that the thinpool needs to be repaired but what do you do if you can't even perform the first step in the procedure? > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/2X73CAASB4U...

4 years, 6 months

2
1
0 / 0

Re: How should ovirt-engine be repaired if it is hung up

by Strahil

1. Open VNC console and check the situation. Just like any other VM. 2. You can get the config via checking the vdsm log on the host where the system has started properly last time (as current situation is bad, check previous power up event). You can save the xml and use that to define the VM in virsh, but you also need to define ovirtmgmt network -> check in the web , as I don't have access to my systems right now. If virsh complaints about the disks - check that the storage domains' link is properly set to your storage. Best Regards, Strahil NikolovOn Sep 30, 2019 05:49, wangyu13476969128(a)126.com wrote: > > 1. How should ovirt-engine be repaired if it is hung up? > 2. How do I export the ovirt-engine configuration file? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XNY4GUISXGC...

4 years, 6 months

1
0
0 / 0

How should ovirt-engine be repaired if it is hung up

by wangyu13476969128＠126.com

1. How should ovirt-engine be repaired if it is hung up? 2. How do I export the ovirt-engine configuration file?

4 years, 6 months

2
2
0 / 0

Re: Ovirt 4.2.7 won't start and drops to emergency console

by Strahil

Can you suffer downtime ? You can try something like this (I'm improvising): Set to global maintenance (either via UI or hosted-engine --set-maintenance --mode=global) Stop the engine. Stop ovirt-ha-agent ovirt-ha-broker vdsmd supervdsmd sanlock glusterd. Stop all gluster processes via thr script in /usr/share/gluster*..../something-named-kill Disable all LVs in the vg via: lvchange -an LV If it doesn't work try disabling the VG: vgchange -an VG and then enabling it again: vgchange -ay VG Last try to repair the thinpool via: lvchange --repair VG/thinpool Last disable the VG and give the system a reboot to verify everything works. Best Regards, Strahil NikolovOn Sep 29, 2019 14:39, jeremy_tourville(a)hotmail.com wrote: > > Thank you for the reply. Please pardon my ignorance, I'm not very good with GlusterFS. I don't think this is a replicated volume (though I could be wrong) I built a single node hyperconverged hypervisor. I was reviewing my gdeploy file from when I originally built the system. I have the following values: > PV = /dev/sda > VG1= gluster_vg1 > LV1= engine_lv (thick) > LV2 = gluster_vg1 thinpool > LV3 = lv_vmdisks (thinpooll) > LV4 = lv_datadisks (thinpool) > > So according to the article I read in my OP, it says to deactivate the volumes under the thin pool as the first step. I ran the command lvchange -an /dev/gluster_vg1/lv_datadisks When I do this I am told Volume group "gluster_vg1" not found. Cannot process volume group gluster_vg1. > > That seems consistent with the timeout error message. How do you fix this if you can't access the volumes? Thoughts? > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/HZXE3NCSFWC...

4 years, 6 months

2
1
0 / 0

Cannot enable maintenance mode

by Bruno Martins

Hello guys, I am being unable to put a host from a two nodes cluster into maintenance mode in order to remove it from the cluster afterwards. This is what I see in engine.log: 2019-09-27 16:20:58,364 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-45) [4cc251c9] Correlation ID: 4cc251c9, Job ID: 65731fbb-db34-49a9-ab56-9fba59bc0ee0, Call Stack: null, Custom Event ID: -1, Message: Host CentOS-H1 cannot change into maintenance mode - not all Vms have been migrated successfully. Consider manual intervention: stopping/migrating Vms: Non interactive user (User: admin). Host has been rebooted multiple times. vdsClient shows no VM's running. What else can I do? Kind regards, Bruno Martins

4 years, 6 months

1
0
0 / 0

Re: Ovirt 4.2.7 won't start and drops to emergency console

by Strahil

If it's a replicated volume - then you can safely rebuild your bricks and don't even tryhto repair. There is no guarantee that the issue will not reoccur. Best Regards, Strahil NikolovOn Sep 29, 2019 00:22, jeremy_tourville(a)hotmail.com wrote: > > I see evidence that appears to be a problem with gluster. /var/log/messages has multiple occurrences of: WARNING: /dev/gluster_vg1/lv_<name>: Thin's tihin-pool needs inspection. Also, if I run vgs I am returned info for my other volume groups but not gluster_vg1. Lastly, when reviewing journalctl -xb | grep -i timed I see messages from systemd > Job dev-gluster_vg1-lv_vmdisks.device/start timed.out. > Timed out waiting for device dev-glustet_vg1-lv_vmdisks.device > > Thses messages are happening for both > /dev/gluster_vg1/lv_datadisks > /dev/gluster_vg1/lv_vmdisks > > I did review the article here but I am unable to change to VG1. > https://mellowhost.com/billing/index.php?rp=/knowledgebase/65/How-to-Repa... > > Can anyone assist with a procedure on how to repair? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VCHU2Q4RD5Q...

4 years, 6 months

2
1
0 / 0

Ovirt 4.2.7 won't start and drops to emergency console

by jeremy_tourville＠hotmail.com

I see evidence that appears to be a problem with gluster. /var/log/messages has multiple occurrences of: WARNING: /dev/gluster_vg1/lv_<name>: Thin's tihin-pool needs inspection. Also, if I run vgs I am returned info for my other volume groups but not gluster_vg1. Lastly, when reviewing journalctl -xb | grep -i timed I see messages from systemd Job dev-gluster_vg1-lv_vmdisks.device/start timed.out. Timed out waiting for device dev-glustet_vg1-lv_vmdisks.device Thses messages are happening for both /dev/gluster_vg1/lv_datadisks /dev/gluster_vg1/lv_vmdisks I did review the article here but I am unable to change to VG1. https://mellowhost.com/billing/index.php?rp=/knowledgebase/65/How-to-Repa... Can anyone assist with a procedure on how to repair?

4 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users September 2019