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 478463[details]
full vdsm log
For example when trying to login to a target when iscsid is down, iscsiadm reports exit message <rc> = 20 which means : ISCSI_ERR_ISCSID_NOTCONN - could not connect to iscsid. and vdsm reports "status: 200" which means: "General Storage Exception"
Versions:
-vdsm-4.9-48.el6.x86_64
-iscsi-initiator-utils-6.2.0.872-16.el6.x86_64
How reproducible:
stop iscsid and try to login to a target.
relevant part of vdsm log:
Thread-186136::DEBUG::2011-02-13 12:06:13,341::iscsi::469::Storage.Misc.excCmd::(addiSCSINode) '/usr/bin/sudo -n /sbin/iscsiadm -m node -T iscsi-error1 -l -p 10.35.64.25:3260' (
cwd None)
Dummy-73::DEBUG::2011-02-13 12:06:14,973::storage_mailbox::632::Storage.Misc.excCmd::(_checkForMail) 'dd if=/rhev/data-center/fad50a22-9f5b-4444-881e-b06d43ad6861/mastersd/dom_m
d/inbox iflag=direct,fullblock count=1 bs=1024000' (cwd None)
Dummy-73::DEBUG::2011-02-13 12:06:15,009::storage_mailbox::632::Storage.Misc.excCmd::(_checkForMail) SUCCESS: <err> = '1+0 records in\n1+0 records out\n1024000 bytes (1.0 MB) co
pied, 0.0232658 s, 44.0 MB/s\n'; <rc> = 0
Thread-186136::DEBUG::2011-02-13 12:06:16,387::iscsi::469::Storage.Misc.excCmd::(addiSCSINode) FAILED: <err> = 'iscsiadm: iscsid is not running. Could not start it up automatica
lly using the startup command in the /etc/iscsi/iscsid.conf iscsid.startup setting. Please check that the file exists or that your init scripts have started iscsid.\niscsiadm: can not connect to iSCSI daemon (111)!\niscsiadm: Could not login to [iface: admin, target: iscsi-error1, portal: 10.35.64.25,3260].\niscsiadm: initiator reported error (20 - could not connect to iscsid)\niscsiadm: iscsid is not running. Could not start it up automatically using the startup command in the /etc/iscsi/iscsid.conf iscsid.startup setting. Please check that the file exists or that your init scripts have started iscsid.\niscsiadm: can not connect to iSCSI daemon (111)!\niscsiadm: Could not login to [iface: david, target: iscsi-error1, portal: 10.35.64.25,3260].\niscsiadm: initiator reported error (20 - could not connect to iscsid)\niscsiadm: iscsid is not running. Could not start it up automatically using the startup command in the /etc/iscsi/iscsid.conf iscsid.startup setting. Please check that the file exists or that your init scripts have started iscsid.\niscsiadm: can not connect to iSCSI daemon (111)!\niscsiadm: Could not login to [iface: sfdf, target: iscsi-error1, portal: 10.35.64.25,3260].\niscsiadm: initiator reported error (20 - could not connect to iscsid)\niscsiadm: Could not log into all portals\n'; <rc> = 20
...
Thread-186136::INFO::2011-02-13 12:06:16,414::dispatcher::100::Storage.Dispatcher.Protect::(run) Run and protect: connectStorageServer, Return response: {'status': {'message': '
OK', 'code': 0}, 'statuslist': [{'status': 200, 'id': '00000000-0000-0000-0000-000000000000'}]}
full log attached.
Verified - connection to a target with wrong CHAP user name and password:
Thread-11445::DEBUG::2011-02-23 22:58:12,785::iscsi::468::Storage.Misc.excCmd::(addiSCSINode) FAILED: <err> = 'iscsiadm: Could not login to [iface: default, target: iscsi-error1
, portal: 10.35.64.25,3260].\niscsiadm: initiator reported error (24 - iSCSI login failed due to authorization failure)\niscsiadm: Could not log into all portals\n'; <rc> = 24
Thread-11445::INFO::2011-02-23 22:58:12,856::dispatcher::100::Storage.Dispatcher.Protect::(run) Run and protect: connectStorageServer, Return response: {'status': {'message': 'OK', 'code': 0}, 'statuslist': [{'status': 464, 'id': '00000000-0000-0000-0000-000000000000'}]}
which means:
class iSCSILoginError(StorageServeriSCSIError):
code = 464
message = "Failed to login to iSCSI node"
Created attachment 478463 [details] full vdsm log For example when trying to login to a target when iscsid is down, iscsiadm reports exit message <rc> = 20 which means : ISCSI_ERR_ISCSID_NOTCONN - could not connect to iscsid. and vdsm reports "status: 200" which means: "General Storage Exception" Versions: -vdsm-4.9-48.el6.x86_64 -iscsi-initiator-utils-6.2.0.872-16.el6.x86_64 How reproducible: stop iscsid and try to login to a target. relevant part of vdsm log: Thread-186136::DEBUG::2011-02-13 12:06:13,341::iscsi::469::Storage.Misc.excCmd::(addiSCSINode) '/usr/bin/sudo -n /sbin/iscsiadm -m node -T iscsi-error1 -l -p 10.35.64.25:3260' ( cwd None) Dummy-73::DEBUG::2011-02-13 12:06:14,973::storage_mailbox::632::Storage.Misc.excCmd::(_checkForMail) 'dd if=/rhev/data-center/fad50a22-9f5b-4444-881e-b06d43ad6861/mastersd/dom_m d/inbox iflag=direct,fullblock count=1 bs=1024000' (cwd None) Dummy-73::DEBUG::2011-02-13 12:06:15,009::storage_mailbox::632::Storage.Misc.excCmd::(_checkForMail) SUCCESS: <err> = '1+0 records in\n1+0 records out\n1024000 bytes (1.0 MB) co pied, 0.0232658 s, 44.0 MB/s\n'; <rc> = 0 Thread-186136::DEBUG::2011-02-13 12:06:16,387::iscsi::469::Storage.Misc.excCmd::(addiSCSINode) FAILED: <err> = 'iscsiadm: iscsid is not running. Could not start it up automatica lly using the startup command in the /etc/iscsi/iscsid.conf iscsid.startup setting. Please check that the file exists or that your init scripts have started iscsid.\niscsiadm: can not connect to iSCSI daemon (111)!\niscsiadm: Could not login to [iface: admin, target: iscsi-error1, portal: 10.35.64.25,3260].\niscsiadm: initiator reported error (20 - could not connect to iscsid)\niscsiadm: iscsid is not running. Could not start it up automatically using the startup command in the /etc/iscsi/iscsid.conf iscsid.startup setting. Please check that the file exists or that your init scripts have started iscsid.\niscsiadm: can not connect to iSCSI daemon (111)!\niscsiadm: Could not login to [iface: david, target: iscsi-error1, portal: 10.35.64.25,3260].\niscsiadm: initiator reported error (20 - could not connect to iscsid)\niscsiadm: iscsid is not running. Could not start it up automatically using the startup command in the /etc/iscsi/iscsid.conf iscsid.startup setting. Please check that the file exists or that your init scripts have started iscsid.\niscsiadm: can not connect to iSCSI daemon (111)!\niscsiadm: Could not login to [iface: sfdf, target: iscsi-error1, portal: 10.35.64.25,3260].\niscsiadm: initiator reported error (20 - could not connect to iscsid)\niscsiadm: Could not log into all portals\n'; <rc> = 20 ... Thread-186136::INFO::2011-02-13 12:06:16,414::dispatcher::100::Storage.Dispatcher.Protect::(run) Run and protect: connectStorageServer, Return response: {'status': {'message': ' OK', 'code': 0}, 'statuslist': [{'status': 200, 'id': '00000000-0000-0000-0000-000000000000'}]} full log attached.