Bug 1503607

Summary:	tcmu-runner should support arbitrary Ceph cluster names
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Jason Dillaman <jdillama>
Component:	iSCSI	Assignee:	Mike Christie <mchristi>
Status:	CLOSED ERRATA	QA Contact:	Tejas <tchandra>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	ceph-eng-bugs, ceph-qe-bugs, mkasturi, tchandra
Target Milestone:	rc
Target Release:	3.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tcmu-runner-1.4.0-0.1.el7cp	Doc Type:	If docs needed, set a value
Doc Text:		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:

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