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, 7 months
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, 7 months
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, 7 months