Bug 1508695

Summary: [ceph-iscsi-config]: LUNs are not mapped to hostgroup hosts after reboot
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Jason Dillaman <jdillama>
Component: iSCSIAssignee: Jason Dillaman <jdillama>
Status: CLOSED ERRATA QA Contact: Madhavi Kasturi <mkasturi>
Severity: medium Docs Contact: Aron Gunn <agunn>
Priority: unspecified    
Version: 3.0CC: agunn, ceph-eng-bugs, ceph-qe-bugs, edonnell, hnallurv, jdillama, kdreyer, tchandra
Target Milestone: z3   
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-iscsi-config-2.3-13.el7cp Doc Type: Bug Fix
Doc Text:
.Assigning LUNs and hosts to a hostgroup using the Ceph iSCSI `gwcli` utility no longer prevents access to the LUNs upon reboot of the iSCSI gateway host Previously, after assigning Logical Unit Numbers (LUNs) and hosts to a hostgroup by using the Ceph iSCSI `gwcli` utiliy, and then rebooting the Ceph iSCSI gateway node, this would cause the LUN mappings to not restore properly for the hosts. In this release, hosts are no longer prevented access to the LUNs.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-15 18:20:29 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: 1494421    

Description Jason Dillaman 2017-11-02 00:53:28 UTC 
Description of problem:
After assigning LUNs and hosts to a hostgroup via gwcli, if the IGW host is rebooted, the LUN mappings are not properly restored for the hosts. This prevents access to the LUNs.

Version-Release number of selected component (if applicable):
2.3

How reproducible:
100%

Steps to Reproduce:
1. Assign LUNs and hosts to a hostgroup via gwcli
2. reboot the IGW host

Actual results:
The initiator hosts cannot access their assigned LUNs

Expected results:
The LUNs are available to the assigned hosts
Comment 16 errata-xmlrpc 2018-05-15 18:20:29 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:1563