[ovirt-users] Re: Sanlock volume corrupted on deployment

2019-01-31 Thread Simone Tiraboschi
On Thu, Jan 31, 2019 at 2:48 PM Nir Soffer wrote: > On Thu, Jan 31, 2019 at 2:52 PM Strahil Nikolov > wrote: > >> Dear Nir, >> >> the issue with the 'The method does not exist or is not available: >> {'method': u'GlusterHost.list'}, code = -32601' is not related to the >> sanlock. I don't know

[ovirt-users] Re: Sanlock volume corrupted on deployment

2019-01-31 Thread Nir Soffer
On Tue, Jan 29, 2019 at 2:00 PM Strahil wrote: > Dear Nir, > > According to redhat solution 1179163 'add_lockspace fail result -233' > indicates corrupted ids lockspace. > Good work finding the solution! Note that the page mention error -223, not -233: 2014-08-27 14:26:42+ 2244 [14497]:

[ovirt-users] Re: Sanlock volume corrupted on deployment

2019-01-31 Thread Nir Soffer
On Thu, Jan 31, 2019 at 2:52 PM Strahil Nikolov wrote: > Dear Nir, > > the issue with the 'The method does not exist or is not available: > {'method': u'GlusterHost.list'}, code = -32601' is not related to the > sanlock. I don't know why the 'vdsm-gluster' package was not installed as a >

[ovirt-users] Re: Sanlock volume corrupted on deployment

2019-01-30 Thread Strahil Nikolov
Dear All, I have rebuilt the gluster cluster , but it seems that with the latest updates (I started over from scratch) I am not able to complete the "Prepare VM" phase and thus I cannot reach to the last phase where the sanlock issue happens. I have checked the contents of "

[ovirt-users] Re: Sanlock volume corrupted on deployment

2019-01-29 Thread Strahil
Dear Nir,According to redhat solution 1179163 'add_lockspace fail result -233' indicates corrupted ids lockspace.During the install, the VM fails to get up.In order to fix it, I stop:ovirt-ha-agent, ovirt-ha-broker, vdsmd, supervdsmd, sanlockThen reinitialize the lockspace via 'sanlock direct init

[ovirt-users] Re: Sanlock volume corrupted on deployment

2019-01-28 Thread Nir Soffer
On Sat, Jan 26, 2019 at 6:13 PM Strahil wrote: > Hey guys, > > I have noticed that with 4.2.8 the sanlock issue (during deployment) is > still not fixed. > Am I the only one with bad luck or there is something broken there ? > > The sanlock service reports code 's7 add_lockspace fail result

[ovirt-users] Re: Sanlock volume corrupted on deployment

2019-01-28 Thread Strahil Nikolov
Hi Simone, I will reinstall the nodes and will provide an update. Best Regards,Strahil Nikolov On Sat, Jan 26, 2019 at 5:13 PM Strahil wrote: Hey guys, I have noticed that with 4.2.8 the sanlock issue (during deployment) is still not fixed.Am I the only one with bad luck or there is something

[ovirt-users] Re: Sanlock volume corrupted on deployment

2019-01-28 Thread Simone Tiraboschi
On Sat, Jan 26, 2019 at 5:13 PM Strahil wrote: > Hey guys, > > I have noticed that with 4.2.8 the sanlock issue (during deployment) is > still not fixed. > Am I the only one with bad luck or there is something broken there ? > Hi, I'm not aware on anything breaking hosted-engine deployment on