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.
Description of problem:
testing FCP, with multipath configuration (each LUN is seen by 2 paths - 2 HBA cards), after vdsm discovered all LUNs, number of paths I see in rhevm is 0.
problem is that getDeivceList returns empty path list, but, put status with all information.
please note that since we're talking about FCP, means that there is no actual connections here (differs from iSCSI), and since there is no connect Storage Server sent from backend, and vdsm collect its information from multipath, it will work, but its a version blocker.
{'GUID': '360060160661029000a7f99ef8812e011',
'capacity': '10737418240',
'devtype': 'FCP',
'fwrev': '0000',
'pathlist': [],
'pathstatus': [{'lun': '58',
'physdev': 'sdbl',
'state': 'active',
'type': 'FCP'},
{'lun': '58',
'physdev': 'sdfl',
'state': 'active',
'type': 'FCP'}],
'productID': 'RAID 5',
'pvUUID': '',
'serial': 'SDGC_RAID_5_APM00102500132',
'vendorID': 'DGC',
'vgUUID': ''}]
attachments:
1) multipath -ll
2) getDeviceList
3) vdsm log
Description of problem: testing FCP, with multipath configuration (each LUN is seen by 2 paths - 2 HBA cards), after vdsm discovered all LUNs, number of paths I see in rhevm is 0. problem is that getDeivceList returns empty path list, but, put status with all information. please note that since we're talking about FCP, means that there is no actual connections here (differs from iSCSI), and since there is no connect Storage Server sent from backend, and vdsm collect its information from multipath, it will work, but its a version blocker. {'GUID': '360060160661029000a7f99ef8812e011', 'capacity': '10737418240', 'devtype': 'FCP', 'fwrev': '0000', 'pathlist': [], 'pathstatus': [{'lun': '58', 'physdev': 'sdbl', 'state': 'active', 'type': 'FCP'}, {'lun': '58', 'physdev': 'sdfl', 'state': 'active', 'type': 'FCP'}], 'productID': 'RAID 5', 'pvUUID': '', 'serial': 'SDGC_RAID_5_APM00102500132', 'vendorID': 'DGC', 'vgUUID': ''}] attachments: 1) multipath -ll 2) getDeviceList 3) vdsm log