Bug 1502021

Summary: rbd-target-gw does not support cluster name different than 'ceph'
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Sébastien Han <shan>
Component: iSCSIAssignee: Jason Dillaman <jdillama>
Status: CLOSED ERRATA QA Contact: Madhavi Kasturi <mkasturi>
Severity: medium Docs Contact: Aron Gunn <agunn>
Priority: medium    
Version: 3.0CC: agunn, anharris, ceph-eng-bugs, ceph-qe-bugs, edonnell, flucifre, hnallurv, jdillama, mchristi, mkasturi, shan, tchandra
Target Milestone: rc   
Target Release: 3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-iscsi-config-2.6-3.el7cp Doc Type: Bug Fix
Doc Text:
.The iSCSI gateway supports custom cluster names Previously, the Ceph iSCSI gateway only worked with the default storage cluster name (`ceph`). In this release, the `rbd-target-gw` now supports arbitrary Ceph configuration file locations, which allows the use of storage clusters not named `ceph`. The Ceph iSCSI gateway can be deployed using Ceph Ansible or using the command-line interface with a custom cluster name.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-26 18:16:44 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: 1459861, 1635924    
Bug Blocks: 1494421, 1584264    
Attachments:
Description Flags
ansible-vvv.log none

Description Sébastien Han 2017-10-13 18:22:37 UTC
Description of problem:

rbd-target-gw has hardcoded ceph command.

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


How reproducible:

Deploy a cluster with a name different than 'ceph', try to start rbd-target-gw.

Steps to Reproduce:
1.
2.
3.

Actual results:

Daemon fails with:

Oct 13 16:20:29 ceph-iscsi-gw0 systemd[1]: Started Setup system to export rbd images through LIO.
Oct 13 16:20:29 ceph-iscsi-gw0 systemd[1]: Starting Setup system to export rbd images through LIO...
Oct 13 16:20:29 ceph-iscsi-gw0 rbd-target-gw[5975]: Processing osd blacklist entries for this node
Oct 13 16:20:30 ceph-iscsi-gw0 rbd-target-gw[5975]: Failed to run 'ceph osd blacklist ls'. Please resolve manually...
Expected results:

Runs normally:

-- Logs begin at Fri 2017-10-13 15:36:46 UTC. --
Oct 13 17:19:06 ceph-iscsi-gw0 rbd-target-gw[20764]: No OSD blacklist entries found
Oct 13 17:19:06 ceph-iscsi-gw0 rbd-target-gw[20764]: Reading the configuration object to update local LIO configuration
Oct 13 17:19:06 ceph-iscsi-gw0 rbd-target-gw[20764]: Processing Gateway configuration
Oct 13 17:19:06 ceph-iscsi-gw0 rbd-target-gw[20764]: (Gateway.create_tpg) created TPG '1' for target iqn 'iqn.2003-01.com.redhat.iscsi-gw:ceph-igw'
Oct 13 17:19:06 ceph-iscsi-gw0 rbd-target-gw[20764]: (Gateway.create_target) created an iscsi target with iqn of 'iqn.2003-01.com.redhat.iscsi-gw:ceph-igw'
Oct 13 17:19:06 ceph-iscsi-gw0 rbd-target-gw[20764]: Processing LUN configuration
Oct 13 17:19:06 ceph-iscsi-gw0 rbd-target-gw[20764]: No LUNs to export
Oct 13 17:19:06 ceph-iscsi-gw0 rbd-target-gw[20764]: Processing client configuration
Oct 13 17:19:06 ceph-iscsi-gw0 rbd-target-gw[20764]: Adding the IP to the enabled tpg, allowing iSCSI logins
Oct 13 17:19:06 ceph-iscsi-gw0 rbd-target-gw[20764]: iSCSI configuration load complete


Additional info:

Comment 4 Sébastien Han 2017-10-18 08:38:32 UTC
We fall into the category "Services don't start (e.g. can't launch monitor or RGW, etc.) when following prescribed methodology in published product documentation", but the workaround can be "don't use a ceph cluster name different than the default 'ceph'.

So I don't know.
Federico, can you help us with this?
Thanks.

Comment 5 Jason Dillaman 2017-10-18 13:05:04 UTC
tcmu-runner doesn't support a cluster name other than "ceph", so I think this just becomes a release note / doc update saying that is iSCSI is being utilized, you must name your cluster "ceph" (or manually copy the generated "/etc/ceph/<cluster name>.conf" to "/etc/ceph/ceph.conf").

Comment 6 Sébastien Han 2017-10-18 13:20:19 UTC
*** Bug 1503556 has been marked as a duplicate of this bug. ***

Comment 7 Federico Lucifredi 2017-11-02 23:58:17 UTC
I thought Sage was obsoleting cluster names with Luminous anyway?

Comment 8 Sébastien Han 2017-11-03 08:15:42 UTC
AFAIR the plan is to keep cluster name around for containers and clusters on demand purposes.

Comment 15 Madhavi Kasturi 2018-07-03 14:53:34 UTC
Created attachment 1456259 [details]
ansible-vvv.log

Attaching the ansible log

Comment 30 errata-xmlrpc 2018-09-26 18:16:44 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