Bug 1566514

Summary: [RFE] Support no authentication for all clients from gwcli
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Jason Dillaman <jdillama>
Component: iSCSIAssignee: Mike Christie <mchristi>
Status: CLOSED ERRATA QA Contact: Manohar Murthy <mmurthy>
Severity: medium Docs Contact: Aron Gunn <agunn>
Priority: medium    
Version: 3.0CC: agunn, ceph-eng-bugs, ceph-qe-bugs, hnallurv, jbrier, kdreyer, mchristi, tchandra
Target Milestone: rcKeywords: FutureFeature
Target Release: 3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-iscsi-cli-2.7-5.el7cp Doc Type: Enhancement
Doc Text:
.Disabling CHAP for iSCSI gateway authentication Previously, CHAP authentication was required when using the Ceph iSCSI gateway. With this release, disabling CHAP authentication can be configured with the `gwcli` utility or with Ceph Ansible. However, mixing clients with CHAP enabled and disabled is not supported. All clients must either have CHAP enabled or disabled. If enabled, clients might have different CHAP credentials.
 Story Points: ---
Clone Of:
: 1615088 (view as bug list) Environment:
Last Closed: 2018-09-26 18:19:46 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: 1584264, 1615088    
Attachments:
Description Flags
playbook.log, messages log,event logs none

Description Jason Dillaman 2018-04-12 12:48:45 UTC 
Description of problem:
You should be able to selectively disable CHAP authentication on a per-initiator basis. Right now, CHAP is required for all initiators.
Comment 6 Madhavi Kasturi 2018-08-09 08:40:45 UTC 
Created attachment 1474605 [details]
playbook.log, messages log,event logs
Comment 21 errata-xmlrpc 2018-09-26 18:19:46 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/RHBA-2018:2819