Description of problem: ********************************* After following the steps to create a setup for block storage, the discovery of targets fails with authentication error. When we use target-cli to do the setup the authentication steps are mentioned to add username and password on all the servers. But when using gluster-block it would be expected to take care of it, else these additional steps needs to be documented. iscsiadm -m discovery -t st -p 10.70.46.60 -l 10.70.46.60:3260,1 iqn.2016-12.org.gluster-block:9226c987-17c2-4c05-90d1-47f4a1ae6f55 10.70.46.60:3260,1 iqn.2016-12.org.gluster-block:30db51e5-9772-4ad7-9833-f73b74ca51b8 Logging in to [iface: default, target: iqn.2016-12.org.gluster-block:9226c987-17c2-4c05-90d1-47f4a1ae6f55, portal: 10.70.46.60,3260] (multiple) Logging in to [iface: default, target: iqn.2016-12.org.gluster-block:30db51e5-9772-4ad7-9833-f73b74ca51b8, portal: 10.70.46.60,3260] (multiple) iscsiadm: Could not login to [iface: default, target: iqn.2016-12.org.gluster-block:9226c987-17c2-4c05-90d1-47f4a1ae6f55, portal: 10.70.46.60,3260]. iscsiadm: initiator reported error (24 - iSCSI login failed due to authorization failure) iscsiadm: Could not login to [iface: default, target: iqn.2016-12.org.gluster-block:30db51e5-9772-4ad7-9833-f73b74ca51b8, portal: 10.70.46.60,3260]. iscsiadm: initiator reported error (24 - iSCSI login failed due to authorization failure) To continue I am going to follow the target cli steps and have authentication in place until this gets fixed. Version-Release number of selected component (if applicable): ********************************************** rpm -qa | grep gluster-block gluster-block-0.1.1-1.x86_64 How reproducible: *********************************** Always Steps to Reproduce: 1. Create the setup for block storage 2. Execute the command to discover iscsi targets from the initiator 3. Actual results: ******************************** It fails with authentication error. Could not login to [iface: default, target: iqn.2016-12.org.gluster-block:30db51e5-9772-4ad7-9833-f73b74ca51b8, portal: 10.70.46.60,3260]. iscsiadm: initiator reported error (24 - iSCSI login failed due to authorization failure) Expected results: ********************************* The authentication should succeed and targets should be discovered successfully. Additional info: ********************* Will be trying manually to have authentication steps in place and will update the results.
Authentication support is coming as part of [1] patches [2] [1] https://github.com/gluster/gluster-block/issues/5 [2] https://review.gluster.org/#/c/17037/ https://review.gluster.org/#/c/17038/ https://review.gluster.org/#/c/17039/ https://review.gluster.org/#/c/17040/ Note: please do not expect gluster-block to support any manual edits.
*** This bug has been marked as a duplicate of bug 1446567 ***
Apologies for closing, I actually intended mark #1446567 as duplicate of this bug.
*** Bug 1446567 has been marked as a duplicate of this bug. ***
Complete support for Authentication: https://review.gluster.org/#/c/17037/ https://review.gluster.org/#/c/17040/
After using auth enable while creating the block and executing discovery from initiators, successfully able to discover the targets and login. Tried creating multiple blocks and successfully able to discover and login. Marking the BZ verified. gluster-block-0.2-3.el7rhgs.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:2773