Re: [ovirt-users] master storage domain stuck in locked state

On Jan 22, 2017 10:13 PM, "Bill Bill" <jax2568(a)outlook.com&gt; wrote: Hello, It was 4.0.5 however, we’ve decided to pull the plug on oVirt for now as it’s too risky in taking down possibly a large number or servers due to this issue. I think oVirt should be a little less “picky” if you will, on storage connections. For example, this specific issue prevented anything storage related from being done. Because the “master” was locked you cannot: Add other storage Activate hosts Start VM’s Reinitialize the datacenter Remove storage These points above a huge – while oVirt is indeed open source, upstream of RHEV and doesn’t cost anything, I feel that in scenarios like this it could be the downfall of oVirt itself being too risky. The logging with oVirt seems to be crazy though – we’ve been testing it now for about 2.5 years, maybe 3 years? Once oVirt gets in a state where it cannot connect to something, it just goes haywire – many likely don’t see this however, every time these things happened it when we’re testing failover scenarios to see how oVirt responds. A few recommendations I would make are: Thank you for your recommendations. I agree with some, wholly disagree with others. I'd still appreciate if you could send us the requested logs. TIA, Y. Drop the whole “master” storage thing – it complicates setting storage up. Either connect, or don’t connect. If there’s connectivity issues, oVirt gets hung up on switching to this “master” storage. If you have a single storage domain, you’ll likely have problems as we’ve experienced because once oVirt cannot find the “master” it begins to go berserk, then spirals out of control there. It might not on small setups with a few hypervisors, but on an install with a few hundred VM’s, large number of hypervisors etc, it seems to get ugly real quick. Stop trying to reconnect things, I think that’s what I’m looking for. When something fails, oVirt just goes in a loop over and over which eventually causes dashboard issues, crazy amounts of logs etc. It would be better if oVirt would just stop, make a log entry and then quit, maybe after a few times. In my case, I could mount the storage manually to ALL hosts, I could even force start the VM’s with virsh. The oVirt dashboard just kept saying it was locked, and wouldn’t let you do anything at all with the entire datacenter. At this time, we’ve pushed these servers back into production using our current hypervisor software which is stable but does not have the benefits of oVirt. It’ll be revisited later on and is still in use for non-production things. *From: *Maor Lipchuk <mlipchuk(a)redhat.com&gt; *Sent: *Sunday, January 22, 2017 7:33 AM *To: *Bill Bill <jax2568(a)outlook.com&gt; *Cc: *users <users(a)ovirt.org&gt; *Subject: *Re: [ovirt-users] master storage domain stuck in locked state On Sun, Jan 22, 2017 at 2:31 PM, Maor Lipchuk <mlipchuk(a)redhat.com&gt; wrote: Also which oVirt version are you using? _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users