RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.