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 2365888

Summary: [GSS][RGW][DOCS][ANSIBLE UPGRADE PRECHECKS] Update Red Hat Documentation to reflect a change in the RGW startup process which could lead to an outage after upgrade and avoid upgrade if prechecks find the misconfiguration
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: José Enrique <josgutie>
Component: RGWAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED CURRENTRELEASE QA Contact: Madhavi Kasturi <mkasturi>
Severity: medium Docs Contact: Rivka Pollack <rpollack>
Priority: high    
Version: 8.0CC: bkunal, ceph-eng-bugs, cephqe-warriors, ckulal, kjosy, mbenjamin, mcaldeir, rkachach, roemerso, rpollack
Target Milestone: ---   
Target Release: 9.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
.Ceph Object Gateway services down after upgrade After upgrading, Ceph Object Gateway services may fail to start. The service fails to start as the `rgw` service now enforces the `rgw_realm` configuration but no realm exists in the Ceph Object Gateway configuration. As a result, the following outputs occur: * The Ceph Object Gateway logs show the following error: `rgw main: failed to load zone: (2) No such file or directory` * The `ceph orch ps | grep rgw` output displays Ceph Object Gateway in an error state. * Ceph Object Gateways are missing from `ceph versions`. As a workaround, removing the `rgw_realm` entry and restart all Ceph Object Gateway services. 1. Verify if the Ceph Object Gateways are configured with no realm indicated while the Ceph configuration database specifies a realm. a. Check the Ceph Object Gateway realm list. `radosgw-admin realm list` The following is an example with an empty realm list: ``` [ceph: root@host01 /]# radosgw-admin realm list { "default_info": "", "realms": [] } ``` b. Check the Ceph configuration database. `ceph config dump | egrep "^WHO|rgw_realm”` For example, ``` [ceph: root@host01 /]# `ceph config dump | egrep "^WHO|rgw_realm WHO MASK LEVEL OPTION VALUE xxxxx.yyyyy advanced rgw_realm default ``` If step 1a matches step 1b, continue to step 2 to remove the `rgw_realm` from the Ceph configuration database. If the two steps do not match, contact Support. 2. Remove the `rgw_realm` from the Ceph configuration database. `ceph config rm xxxxx.yyyyy rgw_realm` 3. Restart all Ceph Object Gateway services. `ceph orch restart rgw`.
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-12-15 12:45:57 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:
Bug Depends On:    
Bug Blocks: 2388233    

Description José Enrique 2025-05-13 11:38:49 UTC
Description of problem:
There is a change in the RGW startup code from Ceph 8.0 where validates the content of rgw_realm, and if it's wrong the startup should fail. 
We should update the release notes to state that change, and the Ansible script should advertise about that bad configuration.

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


How reproducible:
Upgrade a Ceph 7.0 deployment where rgw_realm points to a non-existent realm.

Actual results:

RGW does not start.

Expected results:

Ansible should advertise about the misconfiguration or reflect the RGW startup change in the documentation.

Comment 15 Red Hat Bugzilla 2026-02-06 04:26:13 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days or the product is inactive and locked