12:52 p.m.
Hi,
Check out https://access.redhat.com/solutions/6529691.
I would say that you have done a few hacks that are in 'vicinity' of correct
approach, but the correct approach is a bit simpler than you what you tried to come up
with.
The idea of procedure is that you should 'forget' about the original eg. image
files and to a significant extent
The procedure is "launch a brand new hosted-engine, but actually use a database
backup "
Your answerfile should correspond to what you need (or you just not provide it and answer
questions interactively) - obviously you should not use glusterfs as domainType but
instead
OVEHOSTED_STORAGE/domainType=str:nfs
and also the essential thing
OVEHOSTED_STORAGE/storageDomainConnection=str:<IP of nfs server>:/<name of NFS
volume>
Maybe the owner/group of NFS directory was not changed to vdsm/kvm, the solution above
contains reference to that.
BR,
Konstantin
On 17.01.23, 09:48, "Diego Ercolani" <diego.ercolani(a)ssis.sm
<mailto:diego.ercolani@ssis.sm>> wrote:
ovirt-engine-appliance-4.5-20221206133948
Hello,
I have some trouble with my Gluster instance where there is hosted-engine. I would like to
copy data from that hosted engine and reverse to another hosted-engine storage (I will try
NFS).
I think the main method is to put ovirt in global-management mode, stop the hosted-engine
instance, unmount the hosted-engine storage
systemctl stop {vdsmd;supervdsmd;ovirt-ha-broker;ovirt-ha-agent};
hosted-engine --disconnect-storage
umount /rhev/data-center/mnt/glusterSD/localhost:_glen/
and then redeploy the hosted engine with the current backup:
method 1: [doesn't work; it fail the ansible script after the pause]
ovirt-hosted-engine-setup --4
--config-append=/var/lib/ovirt-hosted-engine-setup/answers/answers-20230116184834.conf
--restore-from-file=230116-backup.tar.gz
--ansible-extra-vars=he_pause_before_engine_setup=true
but it doesn't work
method 2: [I cannot find the glitch]
I saw in every node there is a configuration under
/etc/ovirt-hosted-engine/hosted-engine.conf where there are some interessant entry:
vm_disk_id=0a1a501c-fc45-430f-bfd3-076172cec406
vm_disk_vol_id=f65dab86-67f1-46fa-87c0-f9076f479741
storage=localhost:/glen
domainType=glusterfs
metadata_volume_UUID=4e64e155-ee11-4fdc-b9a0-a7cbee5e4181
metadata_image_UUID=20234090-ea40-4614-ae95-8f91b339ba3e
lockspace_volume_UUID=6a975f46-4126-4c2a-b444-6e5a34872cf6
lockspace_image_UUID=893a1fc1-9a1d-44fc-a02f-8fdac19afc18
conf_volume_UUID=206e505f-1bb8-4cc4-abd9-942654c47612
conf_image_UUID=9871a483-8e7b-4f52-bf71-a6a8adc2309b
so, the conf_volume under conf_image dir is a TAR archive:
/rhev/data-center/mnt/glusterSD/localhost:_glen/3577c21e-f757-4405-97d1-0f827c9b4e22/images/9871a483-8e7b-4f52-bf71-a6a8adc2309b/206e505f-1bb8-4cc4-abd9-942654c47612:
POSIX tar archive (GNU)
That I think is the common configuration. I copied the structure (from
3577c21e-f757-4405-97d1-0f827c9b4e22 directory) in the new storage (nfs), changed the
entries under local configuration and "shared configuration":
from storage=localhost:/glen to storage=<server>:/directory (writable by vdsm user
and kvm group)
from domainType=glusterfs to domainType=nfs
and issued:
1. hosted-engine --connect-storage <- work
2. hosted-engine --vm-start <- doesn't work because there is a complain about the
not-starting ovirt-ha-agent
What can I do?
Is there any documentation somewhere?
Diego
_______________________________________________
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://www.ovirt.org/privacy-policy.html>
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
<https://www.ovirt.org/community/about/community-guidelines/>
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org
<mailto:users@ovirt.org>/message/QOJYO43SVOMCX6NHDP2N6PF3EIXDTRLP/