On Tue, Jun 16, 2020 at 10:18 PM Philip Brown <pbr...@medata.com> wrote: > > > Okay, since you asked: > > (note: this is in node 4.3.10. but hosted-engine is 4.2 > I'd LIKE to upgrade it. but the upgrade process is broken. > thats a whole nuther story, aobut how postgresql10 doesnt show up even > though its required for > yum update 'ovirt*setup' > :-/) > > > 1. go to individual node UI. > 2. Click on Storage > 3. Look at the right-sdie aera for "Volume Groups". click on the one that is > for your master data volume > 4. Click on the Rename button on the top right. Pick something sensible
OK, so you are renaming logical volumes *outside* of oVirt. The node UI is *not* part of oVirt. This is just like running: # lvrename ... In the shell. I think this is one of the issues caused by not having lvm filter in the host. With a proper lvm filter, the node UI will not be able to access the logical volumes used by oVirt, that should be managed only by oVirt. Please try this: 1. Open a rootshell in the node (using ssh or node UI) 2. Create lvm filter: vdsm-tool config-lvm-filter Answer "yes" when the tool asks to confirm. 3. Go to the node UI - you should not be able to see or modify logical volumes managed by oVit. > 5. wait a while, and eventually your cluster logs will freak out. > > Happily for me, since our VMs are very lightly loaded, this did not > immediately cause a crash. > But the cluster freaked out.. engine log spewed those errors after a while.. > and in the cluster(engine) UI, it eventually showed > Storage->Domains > as offline. > (well it shows the master as offline, and it didnt even know about the other > ones any more, until I renamed it back) > > > > > > > ----- Original Message ----- > From: "Nir Soffer" <nsof...@redhat.com> > To: "Philip Brown" <pbr...@medata.com> > Cc: "users" <users@ovirt.org> > Sent: Tuesday, June 16, 2020 10:56:45 AM > Subject: Re: [ovirt-users] Re: help: renamed master volume > > On Tue, Jun 16, 2020 at 8:31 PM Philip Brown <pbr...@medata.com> wrote: > > > > nevermind.. found the answer myself thank goodness. > > > > had to rename the volume back to the value of the msdUUID. not the spUUID, > > which I already tried. > > > > If its fatal to rename that volume... > > would be nice to have it lockedout or something? > > Did you rename the volume from within oVirt UI? > > Can you give clear reproduction instructions, how to break your storage domain > by renaming a volume? > > Nir > > > ----- Original Message ----- > > From: "Philip Brown" <pbr...@medata.com> > > To: "users" <users@ovirt.org> > > Sent: Tuesday, June 16, 2020 10:21:12 AM > > Subject: help: renamed master volume > > > > Im pretty new to ovirt. Trying to upgrade an old install from 4.1 to 4.3 > > > > on the way, I browsed into the Storage area, in one of the nodes. > > > > Noticed under the "Volume groups", area that the volumes were named after > > some loong ID string. > > > > Saw there was a "rename" button. > > figured it would be just like renaming a VM. thigns would just get auto > > adjusted. > > > > but after I renamed to something in english, the cluster is freaking out, > > > > "cant find master domain: u'spUUID=xxxxxxx, msdUUID=xxxxxxx' " > > > > and under Storage: Storage DOmains, the Data(Master) is down. > > How can I recover from this ASAP? :-( > > _______________________________________________ > > 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/ZTDLZ7W4TQAON7U27IWJSOLYJBMKAB3V/ > _______________________________________________ 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/C3RGGEWEV2XLWGBPDLDAZOSSQC76GDYU/