oVirt nodes with local storage
On the weekend I upgraded my self-hosted oVirt engine to 4.56. All went well with that! I also spotted that there was an update for all my 4.54 nodes, but something has changed with the repo overnight because none of my nodes see updates anymore, though the update remains available here … https://resources.ovirt.org/pub/ovirt-4.5/iso/ovirt-node-ng-installer/. Yesterday, I attempted to update just one of my nodes and ran into this snag… “Local storage domains were found on the same filesystem as / ! Please migrate the data to a new LV before upgrading, or you will lose the VMs”. I’ve always stored my VMs in a separate /DATA directory off the root filesystem, and shared the local storage using NFS. I know it’s not ideal, but with good frequent regular backups, it has served me well for many years. A Google search revealed, that others have also had similar local storage issues, and suggestions on ways to mitigate the issue, including the oVirt documentation found here… https://www.ovirt.org/documentation/upgrade_guide/index.html#Upgrading_hyper..., is not my preferred fix. In the past node updates with my local storage were not a problem and were easy peasy! From some of the discussions I saw at Red Hat, I have deduced (maybe wrongly) that there was an issue that necessitated a fix, which introduced a required check for local storage during the upgrade process. I probably should move all the local storage off the oVirt nodes, but at this time, that is easier said than done. I’m posting here only to see if there are perhaps other ideas or perspectives I may not have thought of and should consider with my local storage. Thank you all in advance, much appreciated, and of course, thank you all for supporting oVirt!
Your problem seems similar to this one: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/C2VS5Q56URFSVO2... From what I understand, the entire /data directory should live in a different filesystem than the root one, otherwise the update fails. --gianluca On Tue, Jan 16, 2024 at 6:59 AM Wild Star <wildstar2004@hotmail.com> wrote:
On the weekend I upgraded my self-hosted oVirt engine to 4.56. All went well with that!
I also spotted that there was an update for all my 4.54 nodes, but something has changed with the repo overnight because none of my nodes see updates anymore, though the update remains available here … https://resources.ovirt.org/pub/ovirt-4.5/iso/ovirt-node-ng-installer/.
Yesterday, I attempted to update just one of my nodes and ran into this snag… “Local storage domains were found on the same filesystem as / ! Please migrate the data to a new LV before upgrading, or you will lose the VMs”.
I’ve always stored my VMs in a separate /DATA directory off the root filesystem, and shared the local storage using NFS. I know it’s not ideal, but with good frequent regular backups, it has served me well for many years.
A Google search revealed, that others have also had similar local storage issues, and suggestions on ways to mitigate the issue, including the oVirt documentation found here… https://www.ovirt.org/documentation/upgrade_guide/index.html#Upgrading_hyper..., is not my preferred fix.
In the past node updates with my local storage were not a problem and were easy peasy! From some of the discussions I saw at Red Hat, I have deduced (maybe wrongly) that there was an issue that necessitated a fix, which introduced a required check for local storage during the upgrade process.
I probably should move all the local storage off the oVirt nodes, but at this time, that is easier said than done.
I’m posting here only to see if there are perhaps other ideas or perspectives I may not have thought of and should consider with my local storage.
Thank you all in advance, much appreciated, and of course, thank you all for supporting oVirt! _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/YR23KNJSUXH4DS...
Hi Gianluca, One would think that moving the storage off the / (root) filesystem and moving it to its own LV would be all that I needed to do to complete the upgrade. However, come to find out that with oVirt 4.55, local storage can no longer be shared with the other nodes in the same data centre! Although local storage is not ideal, I am not sure why that change had to be implemented, but I do know that I must have missed the memo explaining it. That one node I upgraded has been rolled back to oVirt 4.54 and our entire oVirt environment will need to remain at that version for now. Thanks!
Just a quick note... I can share the local storage with the other nodes. Since I use NFS, mounting it and opening port 2049 surely helped. :)
Yes, but... they will be different volumes... For example: /mnt/local_storage/9eee2948-2772-4d9c-9650-9df5e361353 (your local storage created by oVirt) /mnt/local_storage/nfs_share (your nfs share created by you) chown vdsm: /mnt/local_storage/nfs_share Export the path on /etc/export file. Try it and let us know if it worked. Em dom., 21 de jan. de 2024 às 00:10, Wild Star <wildstar2004@hotmail.com> escreveu:
Just a quick note... I can share the local storage with the other nodes. Since I use NFS, mounting it and opening port 2049 surely helped. :) _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/6FY5VC7ZQ37YVW...
-- Att, Jorge Visentini +55 55 98432-9868
Here's an example with one shared Storage Domain that works. (local.ca is an internal domain) /etc/exports (n1.local) ----------------------- /data/images/ovirt/n1_data_storage *.local.ca(rw,async,wdelay,root_squash) /data/images/ovirt/n1_data_storage 192.168.1.0/24(rw,async,wdelay,root_squash) /etc/exports (n2.local) ----------------------- /data/images/ovirt/n2_data_storage *.local.ca(rw,async,wdelay,root_squash) /data/images/ovirt/n2_data_storage 192.168.1.0/24(rw,async,wdelay,root_squash) NFS mounts (n1.local) --------------------- Server n1.local.ca:/data/images/ovirt/n1_data_storage Mount point /rhev/data-center/mnt/n1.local.ca:_data_images_ovirt_n1__data__storage Server n2.local.ca:/data/images/ovirt/n2_data_storage Mount point /rhev/data-center/mnt/n2.local.ca:_data_images_ovirt_n2__data__storage NFS mounts (n2.local) --------------------- Server n1.local.ca:/data/images/ovirt/n1_data_storage Mount point /rhev/data-center/mnt/n1.local.ca:_data_images_ovirt_n1__data__storage Server n2.local.ca:/data/images/ovirt/n2_data_storage Mount point /rhev/data-center/mnt/n2.local.ca:_data_images_ovirt_n2__data__storage Like I said, local storage is not ideal, because you do lose some functionality. Also, If you lose a node, you also lose it's storage and its VMs, but at least this way (using NFS), you can keep it all within the same Data Center which gives you more flexibility by not isolating each node's local storage to its own Data Center. Once I move that /data directory (where the VMs sit) off the root filesystem "/" to it's own LV, I'll try the upgrade again. I did find examples on how to shrink an NSF, but I'm not sure how to handle oVirt's onn-pool00-tpool. I did try reinstalling a node from scratch, but the custom disk partitioning during setup doesn't seem to work. It would be nice if oVirt automatically partitioned the /data directory to its own LV while sizing it with the remaining disk space.
participants (3)
-
Gianluca Amato -
Jorge Visentini -
Wild Star