Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 479777[details]
full vdsm-log
Description of problem: When iSCSI SD contains inaccessible PV, the PV marked as unknown device, the VG marked as parital and getStorageDomainInfo fails with the Error below :
Thread-9478::ERROR::2011-02-20 16:46:28,354::task::854::TaskManager.Task::(_setError) Unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 862, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/storage/hsm.py", line 1303, in public_getStorageDomainInfo
self.validateSdUUID(sdUUID)
File "/usr/share/vdsm/storage/hsm.py", line 113, in validateSdUUID
SDF.produce(sdUUID=sdUUID).validate()
File "/usr/share/vdsm/storage/blockSD.py", line 600, in validate
svdsm.testReadDevices(devices)
File "<string>", line 2, in testReadDevices
File "/usr/lib64/python2.6/multiprocessing/managers.py", line 740, in _callmethod
raise convert_to_error(kind, result)
OSError: [Errno 2] No such file or directory: 'unknown device'
Version-Release number of selected component (if applicable):
-vdsm-4.9-49.el6.x86_64
How reproducible:
-always
Steps to Reproduce:
1.add iscsi storage domain with 2 or more targets
2.Block connection to one target
Additional info:
-pvs output:
PV VG Fmt Attr PSize PFree
/dev/mapper/1IET_00150001 8ebeceaa-e7ac-4606-8506-704c3fc805f8 lvm2 a- 11.81g 8.38g
/dev/mapper/1Net-3-50G 3afc595e-3d0a-4fa7-8c22-c72688a1ff01 lvm2 a- 49.81g 37.38g
/dev/mapper/1Net-4-50G 3afc595e-3d0a-4fa7-8c22-c72688a1ff01 lvm2 a- 49.94g 43.94g
/dev/sda2 vg0 lvm2 a- 136.24g 0
unknown device 8ebeceaa-e7ac-4606-8506-704c3fc805f8 lvm2 a- 11.94g 11.94g
We need to check it for several scenarios:
1. for attached domain
2. for active domain
3. for last domain (active)
I suspect that for active domains the getRepoStats will return same wrong error.
Verified on vdsm-4.9-52.el6
vdsClient -s 0 getStorageDomainInfo b9750b78-f531-4161-ac3e-fe1805297861
Domain is either partially accessible or entirely inaccessible: ('b9750b78-f531-4161-ac3e-fe1805297861: [\' /dev/mapper/1LIBVIRT3: read failed after 0 of 4096 at 107374116864: Input/output error\', \' /dev/mapper/1LIBVIRT3: read failed after 0 of 4096 at 107374174208: Input/output error\', \' /dev/mapper/1LIBVIRT3: read failed after 0 of 4096 at 0: Input/output error\', \' /dev/mapper/1LIBVIRT3: read failed after 0 of 4096 at 4096: Input/output error\', " Couldn\'t find device with uuid kFcRY0-PUkK-0BWo-HGfc-En60-G4Mf-d12jAR.", \' The volume group is missing 1 physical volumes.\']',)
Created attachment 479777 [details] full vdsm-log Description of problem: When iSCSI SD contains inaccessible PV, the PV marked as unknown device, the VG marked as parital and getStorageDomainInfo fails with the Error below : Thread-9478::ERROR::2011-02-20 16:46:28,354::task::854::TaskManager.Task::(_setError) Unexpected error Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 862, in _run return fn(*args, **kargs) File "/usr/share/vdsm/storage/hsm.py", line 1303, in public_getStorageDomainInfo self.validateSdUUID(sdUUID) File "/usr/share/vdsm/storage/hsm.py", line 113, in validateSdUUID SDF.produce(sdUUID=sdUUID).validate() File "/usr/share/vdsm/storage/blockSD.py", line 600, in validate svdsm.testReadDevices(devices) File "<string>", line 2, in testReadDevices File "/usr/lib64/python2.6/multiprocessing/managers.py", line 740, in _callmethod raise convert_to_error(kind, result) OSError: [Errno 2] No such file or directory: 'unknown device' Version-Release number of selected component (if applicable): -vdsm-4.9-49.el6.x86_64 How reproducible: -always Steps to Reproduce: 1.add iscsi storage domain with 2 or more targets 2.Block connection to one target Additional info: -pvs output: PV VG Fmt Attr PSize PFree /dev/mapper/1IET_00150001 8ebeceaa-e7ac-4606-8506-704c3fc805f8 lvm2 a- 11.81g 8.38g /dev/mapper/1Net-3-50G 3afc595e-3d0a-4fa7-8c22-c72688a1ff01 lvm2 a- 49.81g 37.38g /dev/mapper/1Net-4-50G 3afc595e-3d0a-4fa7-8c22-c72688a1ff01 lvm2 a- 49.94g 43.94g /dev/sda2 vg0 lvm2 a- 136.24g 0 unknown device 8ebeceaa-e7ac-4606-8506-704c3fc805f8 lvm2 a- 11.94g 11.94g