No SPM and the master data domain won't come up
------=_Part_52954813_1884487966.1473191351932 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit During network testing last night I put one compute node into maintenance mode and changed it's network from legacy to OVS, this caused issues and I changed it back. When I changed it back SPM contention started and neither became SPM, the logs are filled with this error message: 2016-09-06 14:43:38,720 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand] (DefaultQuartzScheduler5) [] Command 'SpmStatusVDSCommand(HostName = ovirttest1, SpmStatusVDSCommandParameters:{runAsync='true', hostId='d84ebe29-5acd-4e4b-9bee-041b27a2f9f9', storagePoolId='00000001-0001-0001-0001-0000000000d8'})' execution failed: VDSGenericException: VDSErrorException: Failed to SpmStatusVDS, error = (13, 'Sanlock resource read failure', 'Permission denied'), code = 100 I've put all but the master data domain into maitenance mode and the permissions on it are vdsm/kvm. The permissions on the nfs share have not been modified, but I re-exported the share anyway, the share can be seen on the compute node and I can even mount it on that compute node, as can vdsm: nfs-server:/rbd/it/ovirt-nfs 293G 111G 183G 38% /rhev/data-center/mnt/nfs-server:_rbd_it_ovirt-nfs I'm not really sure where to go beyond this point.. Regards, Logan ------=_Part_52954813_1884487966.1473191351932 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"font-family: Arial; font-size: 12pt; color: #0000= 00"><div>During network testing last night I put one compute node into main= tenance mode and changed it's network from legacy to OVS, this caused issue= s and I changed it back. When I changed it back SPM contention starte= d and neither became SPM, the logs are filled with this error message:</div=
<div><br>2016-09-06 14:43:38,720 ERROR [org.ovirt.engine.core.vdsbroker.vd= sbroker.SpmStatusVDSCommand] (DefaultQuartzScheduler5) [] Command 'SpmStatu= sVDSCommand(HostName =3D ovirttest1, SpmStatusVDSCommandParameters:{runAsyn= c=3D'true', hostId=3D'd84ebe29-5acd-4e4b-9bee-041b27a2f9f9', storagePoolId= =3D'00000001-0001-0001-0001-0000000000d8'})' execution failed: VDSGenericEx= ception: VDSErrorException: Failed to SpmStatusVDS, error =3D (13, 'Sanlock= resource read failure', 'Permission denied'), code =3D 100<br></div><div><= br></div><div>I've put all but the master data domain into maitenance mode = and the permissions on it are vdsm/kvm. The permissions on the nfs sh= are have not been modified, but I re-exported the share anyway, the share c= an be seen on the compute node and I can even mount it on that compute node= , as can vdsm: </div><div><br data-mce-bogus=3D"1"></div><div>nfs-serv= er:/rbd/it/ovirt-nfs 293G 111G 183G 38% /rhev/data-center/mnt/nfs-server:_r= bd_it_ovirt-nfs</div><div><br data-mce-bogus=3D"1"></div><div>I'm not reall= y sure where to go beyond this point..</div><div><br data-mce-bogus=3D"1"><= /div><div data-marker=3D"__SIG_PRE__">Regards,<br>Logan</div></div></body><= /html> ------=_Part_52954813_1884487966.1473191351932--
IIRC, a previous (recent) post stated that going from OVS to legacy was not supported. CC On Wed, Sep 7, 2016 at 3:49 AM, Logan Kuhn <logank@wolfram.com> wrote:
During network testing last night I put one compute node into maintenance mode and changed it's network from legacy to OVS, this caused issues and I changed it back. When I changed it back SPM contention started and neither became SPM, the logs are filled with this error message:
2016-09-06 14:43:38,720 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand] (DefaultQuartzScheduler5) [] Command 'SpmStatusVDSCommand(HostName = ovirttest1, SpmStatusVDSCommandParameters:{runAsync='true', hostId='d84ebe29-5acd-4e4b-9bee-041b27a2f9f9', storagePoolId='00000001-0001-0001-0001-0000000000d8'})' execution failed: VDSGenericException: VDSErrorException: Failed to SpmStatusVDS, error = (13, 'Sanlock resource read failure', 'Permission denied'), code = 100
I've put all but the master data domain into maitenance mode and the permissions on it are vdsm/kvm. The permissions on the nfs share have not been modified, but I re-exported the share anyway, the share can be seen on the compute node and I can even mount it on that compute node, as can vdsm:
nfs-server:/rbd/it/ovirt-nfs 293G 111G 183G 38% /rhev/data-center/mnt/nfs- server:_rbd_it_ovirt-nfs
I'm not really sure where to go beyond this point..
Regards, Logan
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (2)
-
Colin Coe -
Logan Kuhn