Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1928143

Summary:	[cephadm][RGW]: RGW realm name linked to the service_id parameter in the spec file
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Tejas <tchandra>
Component:	Cephadm	Assignee:	Daniel Pivonka <dpivonka>
Status:	CLOSED ERRATA	QA Contact:	Tejas <tchandra>
Severity:	urgent	Docs Contact:	Karen Norteman <knortema>
Priority:	unspecified
Version:	5.0	CC:	kdreyer, sewagner, vereddy
Target Milestone:	---
Target Release:	5.0
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	ceph-16.1.0-997.el8cp	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-08-30 08:28:20 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 Tejas 2021-02-12 13:28:57 UTC

Description of problem:
  The scenario is to create 2 rgw instances on the same node (different ports) under the same realm and same zone.
Currently the approach to do it fails as changing the port with the same service_id fails to launch a new RGW insatnce, and changing the service_id create a new RGW realm altogether.

The new approach discussed is , to decouple the service_id from the realm name , and use the rgw_realm parameter to determine the realm name.

Version-Release number of selected component (if applicable):
ceph version 16.0.0-7953.el8cp (aac7c5c7d5f82d2973c366730f65255afd66e515) pacific (dev)

How reproducible:
always

Steps to Reproduce:
1. Create a spec file with service_id and rgw_realm and rgw_zone, and create orch apply this spec.
2. Create a new spec file with the same service_id , and different port for RGW. This fails to launch the rgw instance , and the service_id is the same.
3. Change the service_id in the spec file , and a new realm is created, which defeats our original purpose altogether.

Comment 2 Daniel Pivonka 2021-03-11 20:28:17 UTC

upstream fix PR: https://github.com/ceph/ceph/pull/39877/files

* The ``ceph orch apply rgw`` syntax and behavior have changed.  RGW
  services can now be arbitrarily named (it is no longer forced to be
  `realm.zone`).  The ``--rgw-realm=...`` and ``--rgw-zone=...``
  arguments are now optional, which means that if they are omitted, a
  vanilla single-cluster RGW will be deployed.  When the realm and
  zone are provided, the user is now responsible for setting up the
  multisite configuration beforehand--cephadm no longer attempts to
  create missing realms or zones.

Comment 3 Ken Dreyer (Red Hat) 2021-03-19 18:28:30 UTC

Sage backported PR 39877 to pacific in https://github.com/ceph/ceph/pull/40135. This will be in the next weekly rebase I build downstream (March 22nd).

Comment 8 errata-xmlrpc 2021-08-30 08:28:20 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 (Red Hat Ceph Storage 5.0 bug fix and enhancement), 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-2021:3294