Hello, I think I0ve found another issue:
I have the three node that are under heavy test and, after having problem with 
gluster I configured them to use with iSCSI (without multipath now) so I 
configured via the gui a new iscsi data domain using a single target under a 
single VLAN.
I suspect there is an issue reporting the correct volume in my case:
I try to explain.
This are the scsi devices in the three nodes:
[root@ovirt-node2 ~]# lsscsi 
[4:0:0:0]    disk    ATA      ST4000NM000A-2HZ TN02  /dev/sda 
[5:0:0:0]    disk    ATA      Samsung SSD 870  2B6Q  /dev/sdb 
[6:0:0:0]    disk    IBM      2145             0000  /dev/sdc 
[N:0:1:1]    disk    Force MP600__1                             /dev/nvme0n1

[root@ovirt-node3 ~]# lsscsi 
[0:0:0:0]    disk    ATA      Samsung SSD 870  2B6Q  /dev/sda 
[6:0:0:0]    disk    IBM      2145             0000  /dev/sdb 
[N:0:0:1]    disk    WD Blue SN570 500GB__1                     /dev/nvme0n1

[root@ovirt-node4 ~]# lsscsi 
[3:0:0:0]    disk    ATA      ST4000NM000A-2HZ TN02  /dev/sda 
[4:0:0:0]    disk    ATA      KINGSTON SA400S3 1103  /dev/sdb 
[5:0:0:0]    disk    IBM      2145             0000  /dev/sdc 

So you see, the SCSI target (IBM 2145) are mapped as /dev/sdc in node2 and 
node4, but in node3 is mapped as /dev/sdb.
In vdsm log of node3 I can find:
2022-09-21 15:53:57,831+0000 INFO  (monitor/aac7917) 
[storage.storagedomaincache] Looking up domain 
aac79175-ab2b-4b5b-a6e4-9feef9ce17ab (sdc:171)
2022-09-21 15:53:57,899+0000 INFO  (monitor/aac7917) 
[storage.storagedomaincache] Looking up domain 
aac79175-ab2b-4b5b-a6e4-9feef9ce17ab: 0.07 seconds (utils:390)
2022-09-21 15:53:57,899+0000 ERROR (monitor/aac7917) [storage.monitor] Setting 
up monitor for aac79175-ab2b-4b5b-a6e4-9feef9ce17ab failed (monitor:363)
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/storage/monitor.py", line 360, in 
_setupLoop
    self._setupMonitor()
  File "/usr/lib/python3.6/site-packages/vdsm/storage/monitor.py", line 382, in 
_setupMonitor
    self._setupDomain()
  File "/usr/lib/python3.6/site-packages/vdsm/utils.py", line 153, in wrapper
    value = meth(self, *a, **kw)
  File "/usr/lib/python3.6/site-packages/vdsm/storage/monitor.py", line 598, in 
_setupDomain
    domain = sdCache.produce(self.sdUUID)
  File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 115, in 
produce
    domain.getRealDomain()
  File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 51, in 
getRealDomain
    return self._cache._realProduce(self._sdUUID)
  File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 139, in 
_realProduce
    domain = self._findDomain(sdUUID)
  File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 156, in 
_findDomain
    return findMethod(sdUUID)
  File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 186, in 
_findUnfetchedDomain
    raise se.StorageDomainDoesNotExist(sdUUID)
vdsm.storage.exception.StorageDomainDoesNotExist: Storage domain does not 
exist: ('aac79175-ab2b-4b5b-a6e4-9feef9ce17ab',)

So the node is kicked out of the ovirt cluster telling that it's not possible 
to connect to iSCSI domain.....

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/J5HYQOJNZBNXH2KAHEEXUM3ACJ7DUTWM/

Reply via email to