[ovirt-users] Re: Broke my GlusterFS somehow

I think Patrick already gave quite sound advice. I'd only want to add, that you should strictly separate dealing with Gluster and oVirt: the integration isn't strong and oVirt just uses Gluster and won't try to fix it intelligently. Changing hostnames on an existing Gluster is "not supported" I guess, even if I understand how that can be a need in real life. I've had occasion to move HCI clusters from one IP range to another and it's a bit like open heart surgery. I had no control over the DNS in that environment so I made do with /etc/hosts on all Gluster members. It's stone age, but it works and you have full control. So you are basically free to use the old hostnames in /etc/hosts to ensure that the gluster pool members are able to talk to each other, while all outside access is with the new names. If you can get the management engine to run somehow, you can use the trick of using the old aliases in the host file, too, to regain operations. In some cases I've even worked with pure IP addresses for the Gluster setup and even that can be all changed in the /var/lib configuration files if and only if all Gluster daemons are shut down (they tend to keep their state in memory and write it down as the daemon finishes). Once Gluster itself is happy and "gluster volume status all" is showing "y" on all ports and bricks, oVirt generally had no issues at all using the storage. It may just take a long time to show things as ok. The only other piece of advice I can give for a situation like that is to decide where your value is and how quickly you need to be back in business. If it's the VMs running on the infra or the oVirt setup itself? If it's the VMs and if you're still running on one Gluster leg, I'd concentrate on saving the VMs. Backup and Export domains on NFS are safe in the sense, that they can typically be attached to an oVirt that you rebuilt from scratch, so that's one option. OVA exports sometimes work and I've also used Clonezilla to copy VMs across to other hypervisors, booting the Clonezilla ISO at both ends and doing a network transfer: they lose some attributs and the network may need to be redone afterwards, but the data stays safe. If it's the oVirt setup, I'd rather recommend starting from scratch with the latest release and hopefully some backup of the VMs. Fiddling with the database is nothing I'd recommend.