Hi Bill, Can you please attach the engine and VDSM logs. Does the storage domain still stuck?
Regards, Maor On Sat, Jan 21, 2017 at 3:11 AM, Bill Bill <[email protected]> wrote: > > > Also cannot reinitialize the datacenter because the storage domain is > locked. > > > > *From: *Bill Bill <[email protected]> > *Sent: *Friday, January 20, 2017 8:08 PM > *To: *users <[email protected]> > *Subject: *RE: master storage domain stuck in locked state > > > > Spoke too soon. Some hosts came back up but the storage domain is still > locked so no vm’s can be started. What is the proper way to force this to > be unlocked? Each time we look to move into production after successful > testing, something like this always seems to pop up at the last minute > rending oVirt questionable in terms of reliability for some unknown issue. > > > > > > > > *From: *Bill Bill <[email protected]> > *Sent: *Friday, January 20, 2017 7:54 PM > *To: *users <[email protected]> > *Subject: *RE: master storage domain stuck in locked state > > > > > > So apparently something didn’t change the metadata to master before > connection was lost. I changed the metadata role to master and it came > backup. Seems emailing in helped because every time I can’t figure > something out, email in a find it shortly after. > > > > > > *From: *Bill Bill <[email protected]> > *Sent: *Friday, January 20, 2017 7:43 PM > *To: *users <[email protected]> > *Subject: *master storage domain stuck in locked state > > > > No clue how to get this out. I can mount all storage manually on the > hypervisors. It seems like after a reboot oVirt is now having some issue > and the storage domain is stuck in locked state. Because of this, can’t > activate any other storage either, so the other domains are in maintenance > and the master sits in locked state, has been for hours. > > > > This sticks out on a hypervisor: > > > > StoragePoolWrongMaster: Wrong Master domain or its version: > u'SD=d8a0172e-837f-4552-92c7-566dc4e548e4, pool=3fd2ad92-e1eb-49c2-906d- > 00ec233f610a' > > > > Not sure, nothing changed other than a reboot of the storage. > > > > Engine log shows: > > > > [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] > (DefaultQuartzScheduler8) [5696732b] START, SetVdsStatusVDSCommand(HostName > = U31U32NodeA, SetVdsStatusVDSCommandParameters:{runAsync='true', > hostId='70e2b8e4-0752-47a8-884c-837a00013e79', status='NonOperational', > nonOperationalReason='STORAGE_DOMAIN_UNREACHABLE', > stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 6db9820a > > > > No idea why it says unreachable, it certainly is because I can manually > mount ALL storage to the hypervisor. > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows 10 > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > >
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
