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 " /var/log/ovirt-hosted-engine-setup/engine-logs-2019-01-31T06:54:22Z/ovirt-engine/engine.log" and the only errors I see are:


[root@ovirt1 ovirt-engine]# grep ERROR engine.log
2019-01-31 08:56:33,326+02 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [3806b629] Failed in 'GlusterServersListVDS' method
2019-01-31 08:56:33,343+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [3806b629] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt1.localdomain command GlusterServersListVDS failed: The method does not exist or is not available: {'method': u'GlusterHost.list'}
2019-01-31 08:56:33,344+02 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [3806b629] Command 'GlusterServersListVDSCommand(HostName = ovirt1.localdomain, VdsIdVDSCommandParametersBase:{hostId='07c6b36a-6939-4059-8dd3-4e47ea094538'})' execution failed: VDSGenericException: VDSErrorException: Failed to GlusterServersListVDS, error = The method does not exist or is not available: {'method': u'GlusterHost.list'}, code = -32601
2019-01-31 08:56:33,591+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-55) [51bf8a11] EVENT_ID: GLUSTER_COMMAND_FAILED(4,035), Gluster command [<UNKNOWN>] failed on server <UNKNOWN>.
2019-01-31 08:56:34,856+02 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-60) [3ee4bd51] Failed in 'GlusterServersListVDS' method
2019-01-31 08:56:34,857+02 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-60) [3ee4bd51] Command 'GlusterServersListVDSCommand(HostName = ovirt1.localdomain, VdsIdVDSCommandParametersBase:{hostId='07c6b36a-6939-4059-8dd3-4e47ea094538'})' execution failed: VDSGenericException: VDSErrorException: Failed to GlusterServersListVDS, error = The method does not exist or is not available: {'method': u'GlusterHost.list'}, code = -32601
2019-01-31 08:56:35,191+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-60) [3fd826e] EVENT_ID: GLUSTER_COMMAND_FAILED(4,035), Gluster command [<UNKNOWN>] failed on server <UNKNOWN>.



Any hint how to proceed further ?

Best Regards,
Strahil Nikolov



В вторник, 29 януари 2019 г., 14:01:17 ч. Гринуич+2, Strahil <hunter86_bg@yahoo.com> написа:


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, sanlock
Then reinitialize the lockspace via 'sanlock direct init -s' (used bugreport 1116469 as guidance).
Once the init is successful and all the services are up - the VM is started but the deployment was long over and the setup needs additional cleaning up.

I will rebuild the gluster cluster and then will repeat the deployment.

Can you guide me what information will be needed , as I'm quite new in ovirt/RHV ?

Best Regards,
Strahil Nikolov

On Jan 28, 2019 20:34, Nir Soffer <nsoffer@redhat.com> wrote:
On Sat, Jan 26, 2019 at 6:13 PM Strahil <hunter86_bg@yahoo.com> 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 -233' 
'leader1 delta_acquire_begin error -233 lockspace hosted-engine host_id 1'.

Sanlock does not have such error code - are you sure this is -233?

Here sanlock return values:

Can you share your sanlock log?

 

Best Regards,
Strahil Nikolov
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SZMF5KKHSXOUTLGX3LR2NBN7E6QGS6G3/

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, sanlock
Then reinitialize the lockspace via 'sanlock direct init -s' (used bugreport 1116469 as guidance).
Once the init is successful and all the services are up - the VM is started but the deployment was long over and the setup needs additional cleaning up.

I will rebuild the gluster cluster and then will repeat the deployment.

Can you guide me what information will be needed , as I'm quite new in ovirt/RHV ?

Best Regards,
Strahil Nikolov


On Jan 28, 2019 20:34, Nir Soffer <nsoffer@redhat.com> wrote:
>
> On Sat, Jan 26, 2019 at 6:13 PM Strahil <hunter86_bg@yahoo.com> 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 -233' 
>> 'leader1 delta_acquire_begin error -233 lockspace hosted-engine host_id 1'.
>
>
> Sanlock does not have such error code - are you sure this is -233?
>
> Here sanlock return values:
> https://pagure.io/sanlock/blob/master/f/src/sanlock_rv.h
>
> Can you share your sanlock log?
>
>  
>>
>>
>> Best Regards,
>> Strahil Nikolov
>> _______________________________________________
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-leave@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SZMF5KKHSXOUTLGX3LR2NBN7E6QGS6G3/