[ovirt-users] Re: TPM 2.0 Support in Ovirt

[Bob Franzke via Users]

I have tried that. I don’t have the options listed showing in the document for 
the VM edit dialog. I am assuming this is because the hosts do not have the TPM 
module enabled in BIOS? I don’t know if that’s the case or not.  Would the TPM 
setting need to be enabled in hardware on the hosts themselves for this to show 
up in the settings dialog?

 

From: hunter86...@yahoo.com (Strahil Nikolov)  
Sent: Thursday, October 21, 2021 2:04 PM
To: bob.fran...@mdaemon.com; bob.franzke--- via Users 
Subject: Re: [ovirt-users] TPM 2.0 Support in Ovirt

 

Have you tried 
https://www.ovirt.org/documentation/virtual_machine_management_guide/#Adding_TPM_devices
 ?

 

Best Regards,

Strahil Nikolov

On Thu, Oct 21, 2021 at 19:21, bob.franzke--- via Users

mailto:users@ovirt.org> > wrote:

Need to deploy a VM of a Windows 11 guest. Windows 11 requires TPM 2.0 support 
for it to be able to install. Does Ovirt support TPM devices somehow and if so 
how do I present the VM with a TPM device that can be detected by the Windows 
11 setup installer? Thanks in advance for any help here.

___

Users mailing list -- users@ovirt.org  

To unsubscribe send an email to users-le...@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/ORXF2PISPI2I63HBAAHUE2I6IRS46QWG/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/XVB232GDJN5ESMXYC26H544RTNFROSWE/

[ovirt-users] Re: Cannot Start VM After Pausing due to Storage I/O Error

[Bob Franzke via Users]

Sorry here, after some further investigation, this is not using a Gluster 
share. These particular VMs were set up using an NFS share on a NAS device we 
have. I don’t know why this was used for these particular devices. Maybe it was 
a temporary thing and the idea was to move these into the gluster setup 
eventually. Not sure. At any rate, the paused VMs don’t appear to be using 
gluster mounts for storage. 

 

From: jean-lo...@dupond.be (Jean-Louis Dupond)  
Sent: Monday, September 13, 2021 1:52 AM
To: Strahil Nikolov ; marcel d'heureuse 
; bob.fran...@mdaemon.com; users@ovirt.org
Subject: Re: [ovirt-users] Re: Cannot Start VM After Pausing due to Storage I/O 
Error

 

Which Qemu version are you using?
Cause it might be related to https://bugzilla.redhat.com/show_bug.cgi?id=1994494

Jean-Louis

On 10/09/2021 19:59, Strahil Nikolov via Users wrote:

Can you provide the output from all nodes: 

 

gluster pool list

gluster peer status

gluster volume status

 

 

Best Regards,

Strahil Nikolov

On Fri, Sep 10, 2021 at 0:50, marcel d'heureuse

   wrote:

___
Users mailing list -- users@ovirt.org  
To unsubscribe send an email to users-le...@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/ZNXYN2N2EAVKDTLJJJYGJLGG4ZAMZBEG/
 

 





___
Users mailing list -- users@ovirt.org  
To unsubscribe send an email to users-le...@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/O3AO7BB6NGEBHJPV322RSIY3EDNANMYE/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/YVGFTM5ATR6HBBOGDTG2KWIULE5ACQ3P/

[ovirt-users] Re: Cannot Start VM After Pausing due to Storage I/O Error

[Bob Franzke via Users]

Incidentally, I also did find this in the OVIRT logs:

 

MainProcess|jsonrpc/7::DEBUG::2021-09-09 
15:36:32,791::commands::219::root::(execCmd) FAILED:  = 'mount.nfs: No 
route to host\n';  = 32

MainProcess|jsonrpc/7::DEBUG::2021-09-09 
15:36:32,792::logutils::319::root::(_report_stats) ThreadedHandler is ok in the 
last 125 seconds (max pending: 0)

MainProcess|jsonrpc/7::ERROR::2021-09-09 
15:36:32,793::supervdsm_server::103::SuperVdsm.ServerCallback::(wrapper) Error 
in mount

 

Not sure what it means. ‘No route to host’ is not accurate as the host the NFS  
mount is hosted on was completely accessible from a network perspective. Not 
sure if this is relevant or not, but thought I would include it.

 

From: mar...@deheureu.se (marcel d'heureuse)  
Sent: Thursday, September 9, 2021 4:49 PM
To: bob.fran...@mdaemon.com; users@ovirt.org
Subject: Re: [ovirt-users] Re: Cannot Start VM After Pausing due to Storage I/O 
Error

 

Moin,

Normally you can use virsh to start vm which are in pause.


https://www.google.com/amp/s/www.cyberciti.biz/faq/linux-list-a-kvm-vm-guest-using-virsh-command/


You have to use saslpasswd2 -a libvirt username to get access on comandline.

It is importand that you Resum that vm on the same host where it was paused.

Good luck...

Br
Marcel

Am 9. September 2021 22:10:52 MESZ schrieb "bob.franzke--- via Users" 
mailto:users@ovirt.org> >:

OK looking into this further, it seems that I was incorrect about the Gluster 
situation on these hosts. There are three hosts which form a replicated 
arbitrated gluster volume between them. There is a second gluster volume which 
is distributed but only seems to exist on the 4 host (the one the failed VMs 
are running on. I am not sure why this was set up this way. 

After all that I looked closer and realized there is an NFS share which these 
VMs disks are located on. I can access and write to this NFS share from the 
host itself so I am not sure what the story is as to why I cannot get this VM 
to come up. Seems like everything is there for it to do so. The error I get 
when trying to start up the VM is the following:

  has been paused due to storage I/O problem.

How can I determine what this I/O problem actually is? IS the disk file 
corrupted somehow? Both VMs that won;t start are using this NFS share. Others 
that are running also use it so I am  ot sure what the problem here is or where 
to start looking for an answer. Thanks in advance for your help.


  _  

Users mailing list -- users@ovirt.org  
To unsubscribe send an email to users-le...@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/EX7TAYPEKKVEXQ275UNRRA473CBHB6JI/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/2IACJWBMH7URUCM62MCYTDGPZWPUUGFM/

[ovirt-users] Re: Cannot Start VM After Pausing due to Storage I/O Error

[Bob Franzke via Users]

Thanks for the reply.

 

I ended up moving the disk for another VM that was also paused and using the 
same NFS share for storage. I moved the disk to a different share, and then 
moved it back. Then to my surprise, the VM would start up. I then tried to 
start the VM this thread opened on and it also started up. So this appears to 
be due to some transient network error not being able to access the NFS share 
the VM was stored on. I am not sure what sort of checks Ovirt does to determine 
of the share is accessible, but we have seen this before with our OVIRT setup. 
Rebooting switches for maintenance for example would pause VMs in our setup. 
Rebooting the manager server after the network is stabilized seems to fix 
everything. I looked through the network logs to see what would have caused 
this but didn’t see any issue with the devices hosting this NFS share. So 
couldn’t be sure what caused this. It seems OVIRT is very intolerant of ANY 
network issues whatsoever, even ones designed to improve network stability and 
availability (spanning tree, failover mechanisms, etc.). In the event of a 
network situation, why wouldn’t OVIRT try accessing the share again once the 
network was stabilized. Perhaps this is simply due to poor design of our 
particular OVIRT installation, but it seems really finicky with ANYTHING 
changing on the network. If we were to design this again, I wouldn’t rely on 
any network storage to run VMs and put everything on gluster mounts local to 
the hosts. would appreciate any ideas on why this might have happened. 

 

Thanks for the reply. I’ll keep this link handy for the future on running VMs 
via command line. Thanks.

 

Bob

 

From: mar...@deheureu.se (marcel d'heureuse)  
Sent: Thursday, September 9, 2021 4:49 PM
To: bob.fran...@mdaemon.com; users@ovirt.org
Subject: Re: [ovirt-users] Re: Cannot Start VM After Pausing due to Storage I/O 
Error

 

Moin,

Normally you can use virsh to start vm which are in pause.


https://www.google.com/amp/s/www.cyberciti.biz/faq/linux-list-a-kvm-vm-guest-using-virsh-command/


You have to use saslpasswd2 -a libvirt username to get access on comandline.

It is importand that you Resum that vm on the same host where it was paused.

Good luck...

Br
Marcel

Am 9. September 2021 22:10:52 MESZ schrieb "bob.franzke--- via Users" 
mailto:users@ovirt.org> >:

OK looking into this further, it seems that I was incorrect about the Gluster 
situation on these hosts. There are three hosts which form a replicated 
arbitrated gluster volume between them. There is a second gluster volume which 
is distributed but only seems to exist on the 4 host (the one the failed VMs 
are running on. I am not sure why this was set up this way. 

After all that I looked closer and realized there is an NFS share which these 
VMs disks are located on. I can access and write to this NFS share from the 
host itself so I am not sure what the story is as to why I cannot get this VM 
to come up. Seems like everything is there for it to do so. The error I get 
when trying to start up the VM is the following:

  has been paused due to storage I/O problem.

How can I determine what this I/O problem actually is? IS the disk file 
corrupted somehow? Both VMs that won;t start are using this NFS share. Others 
that are running also use it so I am  ot sure what the problem here is or where 
to start looking for an answer. Thanks in advance for your help.


  _  

Users mailing list -- users@ovirt.org  
To unsubscribe send an email to users-le...@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/EX7TAYPEKKVEXQ275UNRRA473CBHB6JI/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/VG433NBFHFY2YZ4DAX57IEEJ4SW3GM67/

[ovirt-users] Re: [Bulk Email] Re: Re-creating ISO Storage Domain after Manager Rebuild

[Bob Franzke via Users]

OK thanks for the reply here. As you said I, and because its all I seem to be 
able to do with this through the UI, I will try and destroy this domain. 

I noticed I also have another domain, labeled "ovirt-image-repository". That 
shows as 'unattached' and I cannot do anything with it in the UI at all. No 
manage, no attach, no destroy even. Looking at the contents of this, it shows a 
bunch of what look to be ISO images for various Linux distros on an Openstack 
Glance FS of some kind. No path is given so not sure where this is hosted in 
this setup. Its listed as an 'image' domain type. Maybe this was set up to be 
used as mentioned loading ISO images to be used for CD-ROM attachment for 
booting. Any idea what this might be?

And how can I 'upload' an ISO to be used for booting VMs. I have two Gluster 
domains which store actual VM disk files. Is this where I would upload an ISO 
to boot a VM off of? Sorry for the idiot questions here. Any help is 
appreciated.

-Original Message-
From: d...@redhat.com (Yedidyah Bar David)  
Sent: Tuesday, August 18, 2020 1:51 AM
To: Alex K 
Cc: Bob Franzke ; Strahil ; 
users 
Subject: [Bulk Email] [ovirt-users] Re: Re-creating ISO Storage Domain after 
Manager Rebuild

On Sat, Aug 15, 2020 at 9:24 AM Alex K  wrote:
>
>
>
> On Fri, Aug 14, 2020, 16:50 Bob Franzke via Users  wrote:
>>
>> OK thanks for the reply. As you can perhaps tell I am a complete noob with 
>> Ovirt. The fact its working now at all is a complete miracle.
>>
>> >>> I see 2 approaches on fixing the broken storage domain:
>> >>> - log to engine, switch to postgresql and start searching in the DB for 
>> >>> the uuid.
>>
>> I am not sure what is meant here by 'switch to postgresql'. Can you clarify?
>>
>> >>> Then create the share, create the dir inside and then oVirt should be 
>> >>> happy.
>> >>> Yet it will start complaining for the ISOs that are also missing 
>> >>> (and also unique uuids)
>> >>> - Another approach is to try to remove the ISO domain. Have you tried to 
>> >>> set the domain in maintenance first and then to remove it ?
>>
>> I am not sure how this is done. I don’t seem to have any options in the 
>> Ovirt admin portal to do anything other than destroy the domain. I don’t see 
>> a maintenance mode option in the Admin UI.
>>
>> >>>> Check your VMs , if any has an ISO attached to it.
>>
>> We have templates that were created by someone else. All the VMs seem to be 
>> built off of those templates, which I assume were built initially  by 
>> booting off DVD ISOs and installing the OS's for the template VMs. Maybe I 
>> am missing how VMs get OS's on them in Ovirt. I think the only thing the iso 
>> domain did was allow us to use the virtio drivers for booting off of ISO 
>> images. I am not sure if that’s accurate or makes sense here. I understood 
>> that when the ISO domain is created that those VirtIO drivers for CD booting 
>> are created as part of the ISO domain creation.
>
> When an iso domain is created it is empty. The virtio iso images are not 
> automatically created, need to be uploaded.

Actually, in the past, we used to have such a feature:

https://bugzilla.redhat.com/show_bug.cgi?id=1026933

Creation of iso domain was done by engine-setup, defaulted to Yes, and if the 
windows-guest-tools (WGT) iso rpm was installed, it was copied to it, all 
"automagically". At the time, WGT was available only on/for RHV, and for oVirt 
one had to manually copy the drivers/tools. Since then, two parallel processes 
developed, leading to today's situation:

1. WGT was also created for oVirt, based on NSIS (RHV's was based on 
InstallShield), and later reimplemented (a new 4.4 change) using WIX, OGA was 
deprecated, and the tools ISO is now part of the OS (as part of virtio-win 
project), since basically nothing in it is now oVirt-specific.

2. We realized that having the ISO domain on the engine machine is problematic, 
for various reasons, and gradually made it harder to use.
We still kept it over upgrades, if existing, but didn't (want to) create it on 
new setups. Last relevant change here is:

https://bugzilla.redhat.com/1332813

https://gerrit.ovirt.org/74409

>>
>> This would then give you an option of attaching an uploaded ISO as a CD-ROM 
>> which you can use to boot a VM off of. I have a CentOS VM which has a 
>> corrupted XFS filesystem that I would like to boot off of a Rescue CD to 
>> repair the FS. The only way I know this can be done is by having the rescue 
>> disk ISO uploaded to an ISO domain. Perhaps there is a different way to do 
>> t

[ovirt-users] Re: Re-creating ISO Storage Domain after Manager Rebuild

[Bob Franzke via Users]

OK thanks for the reply. As you can perhaps tell I am a complete noob with 
Ovirt. The fact its working now at all is a complete miracle.

>>> I see 2 approaches on fixing the broken storage domain:
>>> - log to engine, switch to postgresql and start searching in the DB for the 
>>> uuid.

I am not sure what is meant here by 'switch to postgresql'. Can you clarify?

>>> Then create the share, create the dir inside and then oVirt should be happy.
>>> Yet it will start complaining for the ISOs that are also missing (and also 
>>> unique uuids)
>>> - Another approach is to try to remove the ISO domain. Have you tried to 
>>> set the domain in maintenance first and then to remove it ?

I am not sure how this is done. I don’t seem to have any options in the Ovirt 
admin portal to do anything other than destroy the domain. I don’t see a 
maintenance mode option in the Admin UI.

 Check your VMs , if any has an ISO attached to it.

We have templates that were created by someone else. All the VMs seem to be 
built off of those templates, which I assume were built initially  by booting 
off DVD ISOs and installing the OS's for the template VMs. Maybe I am missing 
how VMs get OS's on them in Ovirt. I think the only thing the iso domain did 
was allow us to use the virtio drivers for booting off of ISO images. I am not 
sure if that’s accurate or makes sense here. I understood that when the ISO 
domain is created that those VirtIO drivers for CD booting are created as part 
of the ISO domain creation. This would then give you an option of attaching an 
uploaded ISO as a CD-ROM which you can use to boot a VM off of. I have a CentOS 
VM which has a corrupted XFS filesystem that I would like to boot off of a 
Rescue CD to repair the FS. The only way I know this can be done is by having 
the rescue disk ISO uploaded to an ISO domain. Perhaps there is a different way 
to do that. In any case, it would be good to get the ISO domain working. Right 
now when I try and attach a CD to a VM for booting, there are no options to 
choose and I am assuming its because the VirtIO drivers needed to do such a 
thing are missing because the ISO domain is broken. Sound right?

 Also,  you can upload  an ISO to a data domain and use that to install VMs.

Can this be used to boot off a CD in a situation where I need to boot off a CD 
ISO like you would need to do to boot off a CentOS rescue CD?

Thanks very much for the help. This was a system I inherited from someone else 
and I have really no idea what I am doing with it (I am not a virtualization 
expert and have a Network Engineering background). 

-Original Message-
From: hunter86...@yahoo.com (Strahil Nikolov)  
Sent: Friday, August 14, 2020 4:25 AM
To: bob.fran...@mdaemon.com; users@ovirt.org
Subject: Re: [ovirt-users] Re-creating ISO Storage Domain after Manager Rebuild

When oVirt creates a storage domain , it assigns an unique id (in the engine 
DB) and a single directory, named as the uuid , is created there.

As you lost the dir, your storage domain is gone but as it's an iso domain - it 
shouldn't be critical.

I see 2 approaches on fixing the broken storage domain:
- log to engine, switch to postgresql and start searching in the DB for the 
uuid.
Then create the share, create the dir inside and then oVirt should be happy.
Yet it will start complaining for the ISOs that are also missing (and also 
unique uuids)
- Another approach is to try to remove the ISO domain. Have you tried to set 
the domain in maintenance first and then to remove it ?

Check your VMs , if any has an ISO attached to it.

Also,  you can upload  an ISO to a data domain and use that to install VMs.

Best  Regards,
Strahil Nikolov

На 13 август 2020 г. 22:21:10 GMT+03:00, "bob.franzke--- via Users" 
 написа:
>Hi All,
>
>Late last year I had a disk issue with my Ovirt Manager Server that 
>required I rebuild it and restored from backups. While this worked 
>mostly, one thing that did not get put back correctly was the physical 
>storage location of an ISO domain on the manager server. I believe this 
>was previously set up as an NFS share being hosted on the Manager 
>Server itself. The physical disk path and filesystem were not 
>re-created on the manager server's local disk. So after the restore, 
>the ISO domain shows up in the Ovirt Admin portal but shows the as 
>down, and inactive. If I go into the domain, the 'Manage Domain' and 
>'Remove' buttons are not available. The only option I have for this is 
>'Destroy'. I right now have no ability to do things like boot a VM from 
>a CD and am assuming its because the ISO domain that the images for 
>this would be stored on is not available. How can I recreate this ISO 
>domains to be able to upload ISO images that VM machines can boot 
>from.The original path on the manager server was /gluster:
>
>sdc 8:32   0 278.9G
> 0 disk
>├─sdc1  8:33  

[ovirt-users] Orphaned ISO Storage Domain

[bob . franzke]

Greetings all,

Full disclosure, complete OVIRT novice here. I inherited an OVIRT system and 
had a complete ovirt-engine back in December-January. Because of time and my 
inexperience with OVIRT, I had to resort to hiring consultants to rebuild my 
OVIRT engine from backups. That’s a situation I never want to repeat.

Anyway, we were able to piece it together and at least get most functionality 
back. The previous setup had a ISO storage domain called ‘ISO-COLO’ that seems 
to have been hosted on the engine server itself. The engine hostname is 
‘mydesktop’. We restored the engine from backups I had taken of the SQL DB and 
various support files using the built in OVIRT backup tool. 

So now when looking into the OVIRT console, I see the storage domain listed. It 
has a status of ‘inactive’ showing in the list of various storage domains we 
have setup for this. We tried to ‘activate’ it and it fails activation. The 
path listed for the domain is mydesktop:/gluster/colo-iso. On the host however 
there is no mountpoint that equates to that path:

[root@mydesktop ~]# df -h
Filesystem   Size  Used Avail Use% Mounted on
devtmpfs  47G 0   47G   0% /dev
tmpfs 47G   12K   47G   1% /dev/shm
tmpfs 47G  131M   47G   1% /run
tmpfs 47G 0   47G   0% /sys/fs/cgroup
/dev/mapper/centos-root   50G  5.4G   45G  11% /
/dev/sda2   1014M  185M  830M  19% /boot
/dev/sda1200M   12M  189M   6% /boot/efi
/dev/mapper/centos-home  224G   15G  210G   7% /home
tmpfs9.3G 0  9.3G   0% /run/user/0

The original layout looked like this on the broken engine:

[root@mydesktop ~]# df -h
FilesystemSize  Used Avail Use% Mounted on
/dev/mapper/centos_mydesktop-root  50G   27G   20G  58% /
devtmpfs   24G 0   24G   0% /dev
tmpfs  24G   28K   24G   1% /dev/shm
tmpfs  24G   42M   24G   1% /run
tmpfs  24G 0   24G   0% /sys/fs/cgroup
/dev/mapper/centos_mydesktop-home  25G   45M   24G   1% /home
/dev/sdc11014M  307M  708M  31% /boot
/dev/mapper/centos_mydesktop-gluster  177G  127G   42G  76% /gluster
tmpfs 4.7G 0  4.7G   0% /run/user/0

So it seems the orphaned storage domain is just point to a path that does not 
exist on the new Engine host. 

Also noticed some of the hosts are trying to aces this storage domain and 
getting errors:

The error message for connection mydesktop:/gluster/colo-iso returned by VDSM 
was: Problem while trying to mount target
3/17/2010:47:05 AM

Failed to connect Host vm-host-colo-2 to the Storage Domains ISO-Colo.
3/17/2010:47:05 AM

So it seems hosts are trying to be connected to this storage domain but cannot 
because its not there. Any of the files from the original path are not 
available so I am not even sure what we are missing if anything.

So what are my options here. Destroy the current ISO domain and recreate it, or 
somehow provide the correct path on the engine server? Currently the storage 
space I can use is mounted with /home, which is a different path than the 
original one. Not sure if anything can be done with the disk layout at this 
point to correct this on the engine server itself to get the gluster path back. 
Right now we cannot attach CDs to VMs for booting. No choices show up for use 
when doing a ‘run once’ on an existing VM so I would like to get this working 
so I can fix a broken VM that I need to boot off of ISO media.

Thanks in advance for any help you can provide.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/L45FJL7Q6OL65KYHSOAQFYDBJOOJKGTW/

[ovirt-users] Orphaned ISO Storage Domain

[Bob Franzke]

Greetings all,

 

Full disclosure, complete OVIRT novice here. I inherited an OVIRT system and
had a complete ovirt-engine back in December-January. Because of time and my
inexperience with OVIRT, I had to resort to hiring consultants to rebuild my
OVIRT engine from backups. That's a situation I never want to repeat.

 

Anyway, we were able to piece it together and at least get most
functionality back. The previous setup had a ISO storage domain called
'ISO-COLO' that seems to have been hosted on the engine server itself. The
engine hostname is 'mydesktop'. We restored the engine from backups I had
taken of the SQL DB and various support files using the built in OVIRT
backup tool. 

 

So now when looking into the OVIRT console, I see the storage domain listed.
It has a status of 'inactive' showing in the list of various storage domains
we have setup for this. We tried to 'activate' it and it fails activation.
The path listed for the domain is mydesktop:/gluster/colo-iso. On the host
however there is no mountpoint that equates to that path:

 

[root@mydesktop ~]# df -h

Filesystem   Size  Used Avail Use% Mounted on

devtmpfs  47G 0   47G   0% /dev

tmpfs 47G   12K   47G   1% /dev/shm

tmpfs 47G  131M   47G   1% /run

tmpfs 47G 0   47G   0% /sys/fs/cgroup

/dev/mapper/centos-root   50G  5.4G   45G  11% /

/dev/sda2   1014M  185M  830M  19% /boot

/dev/sda1200M   12M  189M   6% /boot/efi

/dev/mapper/centos-home  224G   15G  210G   7% /home

tmpfs9.3G 0  9.3G   0% /run/user/0

 

The original layout looked like this on the broken engine:

 

[root@mydesktop ~]# df -h

FilesystemSize  Used Avail Use% Mounted on

/dev/mapper/centos_mydesktop-root  50G   27G   20G  58% /

devtmpfs   24G 0   24G   0% /dev

tmpfs  24G   28K   24G   1% /dev/shm

tmpfs  24G   42M   24G   1% /run

tmpfs  24G 0   24G   0% /sys/fs/cgroup

/dev/mapper/centos_mydesktop-home  25G   45M   24G   1% /home

/dev/sdc11014M  307M  708M  31% /boot

/dev/mapper/centos_mydesktop-gluster  177G  127G   42G  76% /gluster

tmpfs 4.7G 0  4.7G   0% /run/user/0

 

So it seems the orphaned storage domain is just point to a path that does
not exist on the new Engine host. 

 

Also noticed some of the hosts are trying to aces this storage domain and
getting errors:

 

The error message for connection mydesktop:/gluster/colo-iso returned by
VDSM was: Problem while trying to mount target

3/17/2010:47:05 AM

 

Failed to connect Host vm-host-colo-2 to the Storage Domains ISO-Colo.

3/17/2010:47:05 AM

 

So it seems hosts are trying to be connected to this storage domain but
cannot because its not there. Any of the files from the original path are
not available so I am not even sure what we are missing if anything.

 

So what are my options here. Destroy the current ISO domain and recreate it,
or somehow provide the correct path on the engine server? Currently the
storage space I can use is mounted with /home, which is a different path
than the original one. Not sure if anything can be done with the disk layout
at this point to correct this on the engine server itself to get the gluster
path back. Right now we cannot attach CDs to VMs for booting. No choices
show up for use when doing a 'run once' on an existing VM so I would like to
get this working so I can fix a broken VM that I need to boot off of ISO
media.

 

Thanks in advance for any help you can provide.

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/XGH6FSSXVBG7MU6ZROURIZQALP7YCAFU/

[ovirt-users] Re: OVirt Engine Server Died - Steps for Rebuilding the Ovirt Engine System

[Bob Franzke]

Thanks for the reply. I looked at the VDSM logs and found these entries:


2020-01-07 08:10:43,107-0600 INFO  (vmrecovery) [vds] recovery: waiting for 
storage pool to go up (clientIF:709)
2020-01-07 08:10:48,112-0600 INFO  (vmrecovery) [vdsm.api] START 
getConnectedStoragePoolsList(options=None) from=in
ternal, task_id=680125a0-7986-438b-a42a-2612bde04006 (api:48)
2020-01-07 08:10:48,112-0600 INFO  (vmrecovery) [vdsm.api] FINISH 
getConnectedStoragePoolsList return={'poollist':
[]} from=internal, task_id=680125a0-7986-438b-a42a-2612bde04006 (api:54)
2020-01-07 08:10:48,113-0600 INFO  (vmrecovery) [vds] recovery: waiting for 
storage pool to go up (clientIF:709)

Looks like something is wrong with a storage pool maybe?

I am really in the dark here. Not sure what this means.

-Original Message-
From: Yedidyah Bar David (d...@redhat.com)  
Sent: Tuesday, January 7, 2020 12:06 AM
To: Bob Franzke 
Cc: users 
Subject: [ovirt-users] Re: OVirt Engine Server Died - Steps for Rebuilding the 
Ovirt Engine System

On Mon, Jan 6, 2020 at 6:01 PM Bob Franzke  wrote:
>
> I just had some VMs go offline over the weekend. I really cannot figure out 
> how to tell why without the engine working.

If you suspect that they failed, as opposed to being shut down from inside them 
(by an admin or whatever), then you can check vdsm logs on the host they ran 
on, and might find a clue.

> I don’t need to really 'control' the VMs but seems without the engine its not 
> just the control aspect. It’s the visibility it gives you into the state of 
> your environment. We used Ovirt as also a lab setup for users to access and 
> build VMs as needed. This is completely offline now without a working Engine. 
> Seems like having an engine available all the time would be pretty important 
> generally.
>
> I have never understood the idea of having the machine that controls VMs, 
> being in the same infrastructure its controlling. Seems very 'chicken or the 
> egg' sort of thing to me. If the engine decides to move itself from one host 
> to another, and it fails for some reason because the process of moving itself 
> caused a problem (stopping services, etc.)then not sure what you would end up 
> with there. Seems very iffy to me, but maybe I am reading too much into it. 
> Again I admittedly don’t know enough about Ovirt to know if this thinking is 
> off base or not. My own experience with networking systems means you would 
> never set things up like this. Each system is autonomous and can take over 
> for the other if one part fails. But then again, if Ovirt Engine had been set 
> up this way, maybe I wouldn't be in the position I am now with no working 
> engine. Lots to sort out. Thanks for the help.

Each host participating in the hosted-engine cluster has two small daemons, 
called agent and broker, in the package ovirt-hosted-engine-ha, that should 
take care of the engine VM.

You are right that this is a chicken-and-egg problem, and this is the solution 
that oVirt includes.

>
> -Original Message-----
> From: Yedidyah Bar David (d...@redhat.com) 
> Sent: Monday, January 6, 2020 8:26 AM
> To: Bob Franzke 
> Cc: users 
> Subject: [ovirt-users] Re: OVirt Engine Server Died - Steps for 
> Rebuilding the Ovirt Engine System
>
> On Mon, Jan 6, 2020 at 4:19 PM Bob Franzke  wrote:
> >
> > So I am getting the impression that without a working ovirt engine, you are 
> > sort of cooked from being able to control VMs such that your whole 
> > organization can potentially come down to the availability of a single 
> > machine? Is this really correct?
>
> Correct.
>
> This does not mean that the engine itself is necessarily critical - if it's 
> down, your VMs should still be ok. If _controlling_ VMs is considered 
> critical for you, then yes - you do need to make sure your engine is alive 
> and well.
>
> > Are there HA options available for the engine server itself?
>
> The standard option is using hosted-engine with several hosts - you get HA 
> out-of-the-box.
>
> I also heard about people using standalone active/standby clustering/HA 
> solutions for the engine.
>
> >
> > -Original Message-
> > From: Yedidyah Bar David (d...@redhat.com) 
> > Sent: Monday, January 6, 2020 12:57 AM
> > To: Bob Franzke 
> > Cc: users 
> > Subject: [ovirt-users] Re: OVirt Engine Server Died - Steps for 
> > Rebuilding the Ovirt Engine System
> >
> > On Mon, Jan 6, 2020 at 12:00 AM Bob Franzke  wrote:
> > >
> > > Thanks for the reply here. Still waiting on a server to rebuild this 
> > > with. Should be here tomorrow. The engine was running on bare metal 
> > > server, and was not a VM.
> > >
> > > In the mean t

[ovirt-users] Re: OVirt Engine Server Died - Steps for Rebuilding the Ovirt Engine System

[Bob Franzke]

I just had some VMs go offline over the weekend. I really cannot figure out how 
to tell why without the engine working. I don’t need to really 'control' the 
VMs but seems without the engine its not just the control aspect. It’s the 
visibility it gives you into the state of your environment. We used Ovirt as 
also a lab setup for users to access and build VMs as needed. This is 
completely offline now without a working Engine. Seems like having an engine 
available all the time would be pretty important generally.

I have never understood the idea of having the machine that controls VMs, being 
in the same infrastructure its controlling. Seems very 'chicken or the egg' 
sort of thing to me. If the engine decides to move itself from one host to 
another, and it fails for some reason because the process of moving itself 
caused a problem (stopping services, etc.)then not sure what you would end up 
with there. Seems very iffy to me, but maybe I am reading too much into it. 
Again I admittedly don’t know enough about Ovirt to know if this thinking is 
off base or not. My own experience with networking systems means you would 
never set things up like this. Each system is autonomous and can take over for 
the other if one part fails. But then again, if Ovirt Engine had been set up 
this way, maybe I wouldn't be in the position I am now with no working engine. 
Lots to sort out. Thanks for the help.

-Original Message-
From: Yedidyah Bar David (d...@redhat.com)  
Sent: Monday, January 6, 2020 8:26 AM
To: Bob Franzke 
Cc: users 
Subject: [ovirt-users] Re: OVirt Engine Server Died - Steps for Rebuilding the 
Ovirt Engine System

On Mon, Jan 6, 2020 at 4:19 PM Bob Franzke  wrote:
>
> So I am getting the impression that without a working ovirt engine, you are 
> sort of cooked from being able to control VMs such that your whole 
> organization can potentially come down to the availability of a single 
> machine? Is this really correct?

Correct.

This does not mean that the engine itself is necessarily critical - if it's 
down, your VMs should still be ok. If _controlling_ VMs is considered critical 
for you, then yes - you do need to make sure your engine is alive and well.

> Are there HA options available for the engine server itself?

The standard option is using hosted-engine with several hosts - you get HA 
out-of-the-box.

I also heard about people using standalone active/standby clustering/HA 
solutions for the engine.

>
> -Original Message-
> From: Yedidyah Bar David (d...@redhat.com) 
> Sent: Monday, January 6, 2020 12:57 AM
> To: Bob Franzke 
> Cc: users 
> Subject: [ovirt-users] Re: OVirt Engine Server Died - Steps for 
> Rebuilding the Ovirt Engine System
>
> On Mon, Jan 6, 2020 at 12:00 AM Bob Franzke  wrote:
> >
> > Thanks for the reply here. Still waiting on a server to rebuild this with. 
> > Should be here tomorrow. The engine was running on bare metal server, and 
> > was not a VM.
> >
> > In the mean time we had a few of the VMs go dark for some reason. I 
> > discovered the vdsm-client commands and tried figuring out what happened. 
> > Is there any way I can start a VM via command line on one of the VM hosts? 
> > Is the vdsm-client command the way to do this without a working engine?
>
> It is, in principle, but that's not supported and is risky - because the 
> engine will not know what you do.
>
> See also e.g.:
>
> https://www.ovirt.org/develop/release-management/features/integration/
> cockpit.html
>
> >
> > -Original Message-
> > From: Yedidyah Bar David (d...@redhat.com) 
> > Sent: Tuesday, December 24, 2019 1:50 AM
> > To: Bob Franzke 
> > Cc: users 
> > Subject: [ovirt-users] Re: OVirt Engine Server Died - Steps for 
> > Rebuilding the Ovirt Engine System
> >
> > On Mon, Dec 23, 2019 at 7:08 PM Bob Franzke  wrote:
> > >
> > > > Which nightly backups? Do they run engine-backup?
> > >
> > > Yes sorry. The backups are the backups created when running the 
> > > engine-backup script. So I have the files and the DB backed up and off 
> > > onto different storage. I just grabbed a copy of the entire /etc 
> > > directory as well just in case there was something needed in there that 
> > > is not included in the engine-backup solution.
> > >
> > > > In either case, assuming this is a production env, I suggest to first 
> > > > test on a separate env to see how it all looks like.
> > >
> > > This is a production environment. My plan is to get a new server ordered 
> > > and built, removing the old server from the equation (old server is old 
> > > and needs to be replaced anyway). Then rebuild the Ov

[ovirt-users] Re: OVirt Engine Server Died - Steps for Rebuilding the Ovirt Engine System

[Bob Franzke]

So I am getting the impression that without a working ovirt engine, you are 
sort of cooked from being able to control VMs such that your whole organization 
can potentially come down to the availability of a single machine? Is this 
really correct? Are there HA options available for the engine server itself?

-Original Message-
From: Yedidyah Bar David (d...@redhat.com)  
Sent: Monday, January 6, 2020 12:57 AM
To: Bob Franzke 
Cc: users 
Subject: [ovirt-users] Re: OVirt Engine Server Died - Steps for Rebuilding the 
Ovirt Engine System

On Mon, Jan 6, 2020 at 12:00 AM Bob Franzke  wrote:
>
> Thanks for the reply here. Still waiting on a server to rebuild this with. 
> Should be here tomorrow. The engine was running on bare metal server, and was 
> not a VM.
>
> In the mean time we had a few of the VMs go dark for some reason. I 
> discovered the vdsm-client commands and tried figuring out what happened. Is 
> there any way I can start a VM via command line on one of the VM hosts? Is 
> the vdsm-client command the way to do this without a working engine?

It is, in principle, but that's not supported and is risky - because the engine 
will not know what you do.

See also e.g.:

https://www.ovirt.org/develop/release-management/features/integration/cockpit.html

>
> -Original Message-
> From: Yedidyah Bar David (d...@redhat.com) 
> Sent: Tuesday, December 24, 2019 1:50 AM
> To: Bob Franzke 
> Cc: users 
> Subject: [ovirt-users] Re: OVirt Engine Server Died - Steps for 
> Rebuilding the Ovirt Engine System
>
> On Mon, Dec 23, 2019 at 7:08 PM Bob Franzke  wrote:
> >
> > > Which nightly backups? Do they run engine-backup?
> >
> > Yes sorry. The backups are the backups created when running the 
> > engine-backup script. So I have the files and the DB backed up and off onto 
> > different storage. I just grabbed a copy of the entire /etc directory as 
> > well just in case there was something needed in there that is not included 
> > in the engine-backup solution.
> >
> > > In either case, assuming this is a production env, I suggest to first 
> > > test on a separate env to see how it all looks like.
> >
> > This is a production environment. My plan is to get a new server ordered 
> > and built, removing the old server from the equation (old server is old and 
> > needs to be replaced anyway). Then rebuild the Ovirt bits and restore the 
> > data from my backups.
>
> I assume, from your first post, that you refer to the host running the 
> engine, and that this is a standalone engine, not hosted-engine.
> Right? Meaning, it's running on bare-metal, not inside a VM managed by itself.
>
> For testing you can try stuff on an isolated VM somewhere, no need to wait 
> for your new server to arrive.
>
> >
> > I just more needed a quick set up steps to take here. From what I gather I 
> > need to basically:
> >
> > 1. reinstall CentOS
> > 2. Reconfigure storage (this server has several ISCSI LUNs its attached to 
> > currently. I don’t know if they are required for this or what).
>
> I obviously have no idea what is your storage design and requirements, but 
> this is largely a local matter, unrelated to the hosts that run VMs. The 
> engine machine's storage is (normally) not used for that, only for the engine 
> itself (and its db, etc.).
>
> > 3. Install PostGreSQL (maybe? Or does the ovirt engine script do 
> > this for you?) 3. Install Ovirt/run ovirt-engine script maybe?
>
> Add relevant repo, by installing relevant ovirt-releast* package (see the web 
> site), and then 'yum install ovirt-engine' - this should grab for you 
> postgresql etc.
>
> > 4. Restore DB and data
>
> Yes. Run basically 'engine-backup --mode=restore' and then 'engine-setup'. 
> Please check the backup/restore documentation on the web site.
> If your current engine used only defaults (meaning, engine+dwh+their DBs all 
> on the engine machine, provisioned by engine-setup), then the restore command 
> should be something like:
>
> engine-backup --mode=restore --file=your-backup-file 
> --provision-all-databases
>
> Again, please test on a test VM somewhere, and make sure it's isolated
> - that it can't reach your hosts and start to manage them (unless that's what 
> you want, of course).
>
> >
> > I am not sure the details of the list outlined above (what to run where, 
> > etc.). I am looking for consultants to help me out here as its clear I am a 
> > bit behind the curve on this one. So far not much has worked out on that 
> > front. Does the above list seem reasonable in terms of needed steps to get 
> > this 

[ovirt-users] Re: OVirt Engine Server Died - Steps for Rebuilding the Ovirt Engine System

[Bob Franzke]

Thanks for the reply here. Still waiting on a server to rebuild this with. 
Should be here tomorrow. The engine was running on bare metal server, and was 
not a VM.

In the mean time we had a few of the VMs go dark for some reason. I discovered 
the vdsm-client commands and tried figuring out what happened. Is there any way 
I can start a VM via command line on one of the VM hosts? Is the vdsm-client 
command the way to do this without a working engine?

-Original Message-
From: Yedidyah Bar David (d...@redhat.com)  
Sent: Tuesday, December 24, 2019 1:50 AM
To: Bob Franzke 
Cc: users 
Subject: [ovirt-users] Re: OVirt Engine Server Died - Steps for Rebuilding the 
Ovirt Engine System

On Mon, Dec 23, 2019 at 7:08 PM Bob Franzke  wrote:
>
> > Which nightly backups? Do they run engine-backup?
>
> Yes sorry. The backups are the backups created when running the engine-backup 
> script. So I have the files and the DB backed up and off onto different 
> storage. I just grabbed a copy of the entire /etc directory as well just in 
> case there was something needed in there that is not included in the 
> engine-backup solution.
>
> > In either case, assuming this is a production env, I suggest to first test 
> > on a separate env to see how it all looks like.
>
> This is a production environment. My plan is to get a new server ordered and 
> built, removing the old server from the equation (old server is old and needs 
> to be replaced anyway). Then rebuild the Ovirt bits and restore the data from 
> my backups.

I assume, from your first post, that you refer to the host running the engine, 
and that this is a standalone engine, not hosted-engine.
Right? Meaning, it's running on bare-metal, not inside a VM managed by itself.

For testing you can try stuff on an isolated VM somewhere, no need to wait for 
your new server to arrive.

>
> I just more needed a quick set up steps to take here. From what I gather I 
> need to basically:
>
> 1. reinstall CentOS
> 2. Reconfigure storage (this server has several ISCSI LUNs its attached to 
> currently. I don’t know if they are required for this or what).

I obviously have no idea what is your storage design and requirements, but this 
is largely a local matter, unrelated to the hosts that run VMs. The engine 
machine's storage is (normally) not used for that, only for the engine itself 
(and its db, etc.).

> 3. Install PostGreSQL (maybe? Or does the ovirt engine script do this 
> for you?) 3. Install Ovirt/run ovirt-engine script maybe?

Add relevant repo, by installing relevant ovirt-releast* package (see the web 
site), and then 'yum install ovirt-engine' - this should grab for you 
postgresql etc.

> 4. Restore DB and data

Yes. Run basically 'engine-backup --mode=restore' and then 'engine-setup'. 
Please check the backup/restore documentation on the web site.
If your current engine used only defaults (meaning, engine+dwh+their DBs all on 
the engine machine, provisioned by engine-setup), then the restore command 
should be something like:

engine-backup --mode=restore --file=your-backup-file --provision-all-databases

Again, please test on a test VM somewhere, and make sure it's isolated
- that it can't reach your hosts and start to manage them (unless that's what 
you want, of course).

>
> I am not sure the details of the list outlined above (what to run where, 
> etc.). I am looking for consultants to help me out here as its clear I am a 
> bit behind the curve on this one. So far not much has worked out on that 
> front. Does the above list seem reasonable in terms of needed steps to get 
> this going again?

See above.

For consultants, you might want to check:

https://www.ovirt.org/community/user-stories/users-and-providers.html

And/or post again to the list with a subject line that's more likely to attract 
them ("Looking for an oVirt consultant...").

Good luck and best regards,

>
>
> -Original Message-
> From: Yedidyah Bar David (d...@redhat.com) 
> Sent: Sunday, December 22, 2019 1:58 AM
> To: bob.fran...@mdaemon.com
> Cc: users 
> Subject: [ovirt-users] Re: OVirt Engine Server Died - Steps for 
> Rebuilding the Ovirt Engine System
>
> On Fri, Dec 20, 2019 at 8:55 PM  wrote:
> >
> > Full disclosure here.I am not an Ovirt Expert. I am a network Engineer 
> > that has been forced to take over sysadmin duties for a departed co-worker. 
> > I have little experience with Ovirt so apologies up front for anything I 
> > say that comes across as stupid or "RTM" questions. Normally I would do 
> > just that but I am in a bind and am trying to figure this out quickly. We 
> > have an OVirt installation setup that consists of 4 nodes and a server that 
> > hosts the ovirt-engine all

[ovirt-users] Looking for Ovirt Consultants

[Bob Franzke]

Having an issue with Ovirt. Ovirt Engine server died. I have no idea about
Ovirt and I am way over my head here. Trying to put the engine back together
to get my environment working again. Can anyone help me here? Thanks in
advance.

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/UO2LGQCEW6F5NSRWXL6GU66UPDCJOAFW/

[ovirt-users] Re: OVirt Engine Server Died - Steps for Rebuilding the Ovirt Engine System

[Bob Franzke]

> Which nightly backups? Do they run engine-backup?

Yes sorry. The backups are the backups created when running the engine-backup 
script. So I have the files and the DB backed up and off onto different 
storage. I just grabbed a copy of the entire /etc directory as well just in 
case there was something needed in there that is not included in the 
engine-backup solution.

> In either case, assuming this is a production env, I suggest to first test on 
> a separate env to see how it all looks like.

This is a production environment. My plan is to get a new server ordered and 
built, removing the old server from the equation (old server is old and needs 
to be replaced anyway). Then rebuild the Ovirt bits and restore the data from 
my backups.

I just more needed a quick set up steps to take here. From what I gather I need 
to basically:

1. reinstall CentOS
2. Reconfigure storage (this server has several ISCSI LUNs its attached to 
currently. I don’t know if they are required for this or what).
3. Install PostGreSQL (maybe? Or does the ovirt engine script do this for you?)
3. Install Ovirt/run ovirt-engine script maybe?
4. Restore DB and data

I am not sure the details of the list outlined above (what to run where, etc.). 
I am looking for consultants to help me out here as its clear I am a bit behind 
the curve on this one. So far not much has worked out on that front. Does the 
above list seem reasonable in terms of needed steps to get this going again?


-Original Message-
From: Yedidyah Bar David (d...@redhat.com)  
Sent: Sunday, December 22, 2019 1:58 AM
To: bob.fran...@mdaemon.com
Cc: users 
Subject: [ovirt-users] Re: OVirt Engine Server Died - Steps for Rebuilding the 
Ovirt Engine System

On Fri, Dec 20, 2019 at 8:55 PM  wrote:
>
> Full disclosure here.I am not an Ovirt Expert. I am a network Engineer 
> that has been forced to take over sysadmin duties for a departed co-worker. I 
> have little experience with Ovirt so apologies up front for anything I say 
> that comes across as stupid or "RTM" questions. Normally I would do just that 
> but I am in a bind and am trying to figure this out quickly. We have an OVirt 
> installation setup that consists of 4 nodes and a server that hosts the 
> ovirt-engine all running CentOS 7. The server that hosts the engine has a 
> pair of failing hard drives and I need to replace the hardware ASAP. Need to 
> outline the steps needed to build a new server to serve as and replace the 
> ovirt engine server. I have backed up the entire /etc directory and the 
> backups being done nightly by the engine itself.

Which nightly backups? Do they run engine-backup?

> I also backed up the iscsi info and took a printout of all the disk 
> arrangement . The disk has gotten so bad at this point that the DB won't back 
> up any longer. Get fatal:backup failed error when
>   trying to run the ovirt backup tool. Also the Ovirt management site is not 
> rendering and I am not sure why.
>
> Is there anything else I need to make sure I backup in order to migrate the 
> engine from one server to another?

Generally speaking, if you used engine-backup for backups, it should be enough 
- it backs up all it needs from /etc.

If you didn't use that, /etc won't be enough. You also need a database backup.

If you do not have a backup of the database, you'll need to create a new engine 
from scratch. You can then import the existing storage domains and add the 
hosts. This will require downtime, and you'll loose some stuff, so if you do 
have an engine-backup backup, better use that.

In either case, assuming this is a production env, I suggest to first test on a 
separate env to see how it all looks like.

> Also, until I can get the engine running again, is there any tool available 
> to manage the VMs on the hosts themselves. The VMs on the hosts are running 
> but need a way to manage them if needed in case something happens while the 
> engine is being repaired.

Some management is possible via cockpit. It's much less than what the engine 
allows.

If you search the list archives, you can find suggestions by people to directly 
use libvirt/virsh after poking a bit inside your storage domain. I'd not 
recommend doing that, unless you know very well what you are doing and have no 
other solution (e.g. if storage is corrupted enough so that import to a new 
engine fails).

> Any info on this as well as what to backup and the steps to move the engine 
> from one server to another would be much much appreciated.

You can search the site for backup, restore, and import storage domain, and 
should find the relevant pages. Please note that the pages under /develop are 
written during development and are usually not updated after a feature is 
complete. The official documentation is under /documentation. That, in turn, is 
often outdated as well :-(.
You can use RHV docs in addition. These are more up-to-date and should be 99% 
applicable to oVirt.

> Sorry I know this a real 

[ovirt-users] OVirt Engine Server Died - Steps for Rebuilding the Ovirt Engine System

[bob . franzke]

Full disclosure here.I am not an Ovirt Expert. I am a network Engineer that 
has been forced to take over sysadmin duties for a departed co-worker. I have 
little experience with Ovirt so apologies up front for anything I say that 
comes across as stupid or "RTM" questions. Normally I would do just that but I 
am in a bind and am trying to figure this out quickly. We have an OVirt 
installation setup that consists of 4 nodes and a server that hosts the 
ovirt-engine all running CentOS 7. The server that hosts the engine has a pair 
of failing hard drives and I need to replace the hardware ASAP. Need to outline 
the steps needed to build a new server to serve as and replace the ovirt engine 
server. I have backed up the entire /etc directory and the backups being done 
nightly by the engine itself. I also backed up the iscsi info and took a 
printout of all the disk arrangement . The disk has gotten so bad at this point 
that the DB won't back up any longer. Get fatal:backup failed error when
  trying to run the ovirt backup tool. Also the Ovirt management site is not 
rendering and I am not sure why. 

Is there anything else I need to make sure I backup in order to migrate the 
engine from one server to another? Also, until I can get the engine running 
again, is there any tool available to manage the VMs on the hosts themselves. 
The VMs on the hosts are running but need a way to manage them if needed in 
case something happens while the engine is being repaired. Any info on this as 
well as what to backup and the steps to move the engine from one server to 
another would be much much appreciated. Sorry I know this a real RTM type post 
but I am in a bind and need a solution rather quickly. Thanks in advance.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/CLLD7EAAMHCVXV45HNQTN2PW3DTBWUTQ/