Red Hat Bugzilla – Bug 1502021
rbd-target-gw does not support cluster name different than 'ceph'
Last modified: 2018-09-26 14:18:18 EDT
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:
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.
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").
*** Bug 1503556 has been marked as a duplicate of this bug. ***
I thought Sage was obsoleting cluster names with Luminous anyway?
AFAIR the plan is to keep cluster name around for containers and clusters on demand purposes.
Created attachment 1456259 [details] ansible-vvv.log Attaching the ansible log
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