Hide Forgot
Description of problem: If the ceph cluster was not using the default ceph name, then rbd checker initialization will fail with Oct 25 04:52:19 | rbd2: Could not read rados conf like is seen in https://bugzilla.redhat.com/show_bug.cgi?id=1388063#c4 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Mike, Customers will have ceph clusters with different names. We cannot ask them to recreate ceph cluster for the iscsi gateways. So this is a critical fix from the view of backward compatibility. Any idea when we can get this fix? We need this fix. Thanks, Tejas
(In reply to Tejas from comment #3) > Mike, > > Customers will have ceph clusters with different names. We cannot ask > them to recreate ceph cluster for the iscsi gateways. So this is a critical > fix from the view of backward compatibility. > Any idea when we can get this fix? We need this fix. > I should hopefully have something upstream approves of Monday or Tuesday. I can make you a rpm then.
I flagged the ceph-iscsi-ansible side of this issue (BZ 1388063) to be included in the release notes. You don't need to re-create your cluster. The cluster name is just a way to automatically pick a configuration file. Instead, if you gave your cluster a unique name, you just need to copy your "/etc/ceph/<unique cluster name>.conf" (and associated keyring) to "/etc/ceph/ceph.conf" on the bootstrap monitor host.
We are changing the implementation in RHCS 2.2 so we will not need this change anymore.