Bug 1503607 - tcmu-runner should support arbitrary Ceph cluster names
Summary: tcmu-runner should support arbitrary Ceph cluster names
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: iSCSI
Version: 3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 3.1
Assignee: Mike Christie
QA Contact: Tejas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-18 13:20 UTC by Jason Dillaman
Modified: 2022-02-21 18:20 UTC (History)
4 users (show)

Fixed In Version: tcmu-runner-1.4.0-0.1.el7cp
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-26 18:16:44 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github open-iscsi tcmu-runner pull 317 0 None None None 2017-10-18 13:35:59 UTC
Red Hat Product Errata RHBA-2018:2819 0 None None None 2018-09-26 18:18:17 UTC

Description Jason Dillaman 2017-10-18 13:20:03 UTC
Description of problem:
The tcmu-runner daemon expects a "/etc/ceph/ceph.conf" file for connecting to the cluster. If the Ceph cluster has a non-default name, ceph-ansible will create a config file using the provided name instead of "ceph". This will prevent tcmu-runner from connecting to the cluster.

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

How reproducible:
100%

Steps to Reproduce:
1. use a custom Ceph cluster name
2. attempt to use tcmu-runner against RBD devices

Actual results:
tcmu-runner will not be able to connect to the cluster

Expected results:
tcmu-runner should support an optional to specify the path to the Ceph configuration file.

Comment 8 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


Note You need to log in before you can comment on or make changes to this bug.