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_bg(a)yahoo.com (Strahil Nikolov) <hunter86_bg(a)yahoo.com>
Sent: Friday, August 14, 2020 4:25 AM
To: bob.franzke(a)mdaemon.com; users(a)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"
<users(a)ovirt.org> написа:
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 0 1G
0 part /boot
└─sdc2 8:34 0 277.9G
0 part
├─centos_mydesktop-root 253:0 0 50G
0 lvm /
├─centos_mydesktop-swap 253:1 0 23.6G
0 lvm [SWAP]
├─centos_mydesktop-home 253:2 0 25G
0 lvm /home
└─centos_mydesktop-gluster 253:3 0 179.3G
0 lvm /gluster
The current layout is now:
└─sda3
8:3 0 277.7G 0 part
├─centos-root
253:0 0 50G 0 lvm /
├─centos-swap
253:1 0 4G 0 lvm [SWAP]
└─centos-home
253:2 0 223.7G 0 lvm /home
Can I just create a new filesystem here, destroy the old ISO domain,
and add a new one using the new path? I am a total Ovirt Noob so would
appreciate any help here. Thanks.
Bob
_______________________________________________
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/N65ZFGT5C3C...