In a similar situation, I’ve had some luck creating a second storage domain & allowing the master role to be moved to it. You don’t even need to have any VMs on it, just have it exist and add it to the engine. That way ovirt doesn’t freak out and reboot your nodes as much while you clean up your main storage domain.
-Darrell On Sep 8, 2014, at 6:27 AM, Jorick Astrego <j.astr...@netbulae.eu> wrote: > Hi, > > Our ovirt test instance has 4 nodes with glusterfs master storage domain. I > had the volume set to distributed replicated gluster and things worked. > > Due to quorum issues, I'm trying to switch it to replicated with replica > count 4. > > Currenlty the nodes keep rebooting while the master storage is down and I > can't get things up again. > > Invalid status on Data Center Default. Setting status to Non Responsive. > Host node3 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data > Center Default. Setting Host state to Non-Operational. > Is there a known way to change the glusterfs volume for the master domain > that doesn't end in a total system faillure? > > Kind regards, > > Jorick Astrego > Netbulae > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
