Bug 1444770

Summary: [gluster-block]: Authentication failure while discovering targets from an initiator
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: surabhi <sbhaloth>
Component: gluster-blockAssignee: Prasanna Kumar Kalever <prasanna.kalever>
Status: CLOSED ERRATA QA Contact: surabhi <sbhaloth>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.2CC: amukherj, prasanna.kalever, rcyriac, rhs-bugs
Target Milestone: ---Keywords: Reopened
Target Release: RHGS 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: gluster-block
Fixed In Version: gluster-block-0.2-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-21 04:17:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1417151    

Description surabhi 2017-04-24 09:10:09 UTC
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.

Comment 2 Prasanna Kumar Kalever 2017-04-25 07:49:28 UTC
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.

Comment 5 Prasanna Kumar Kalever 2017-04-28 12:14:12 UTC

*** This bug has been marked as a duplicate of bug 1446567 ***

Comment 6 Prasanna Kumar Kalever 2017-04-28 12:19:09 UTC
Apologies for closing, I actually intended mark #1446567 as duplicate of this bug.

Comment 7 Prasanna Kumar Kalever 2017-04-28 12:20:08 UTC
*** Bug 1446567 has been marked as a duplicate of this bug. ***

Comment 8 Prasanna Kumar Kalever 2017-05-08 06:30:49 UTC
Complete support for Authentication:
https://review.gluster.org/#/c/17037/
https://review.gluster.org/#/c/17040/

Comment 10 surabhi 2017-05-30 13:21:03 UTC
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

Comment 12 errata-xmlrpc 2017-09-21 04:17:54 UTC
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