Hi all, today we stumbled across an rgw issue. This issue [0] (and PR [1]) seems to address it but to me it looks like not all cases are covered. - cephadm deployment - Ceph v20.2.4 - Ubuntu hosts (22.04) - no multi-site For a specific reason we gave a customer the instructions to pre-create a realm, zonegroup and zone before applying the rgw service. It worked well in previous versions (Squid < 19.2.6, haven't tested other versions yet). Now on 20.2.4 we try the same procedure (create realm, zonegroup and zone beforehand) with this rgw spec: service_type: rgw service_id: s3 service_name: s3 placement: label: rgw spec: ssl: true rgw_frontend_port: 7480 generate_cert: true wildcard_enabled: true zonegroup_hostnames: - s3.example.com What we didn't have in previous tests was the requirement to use a generated certificate (generate_cert). And we currently don't have our own certificates in this case (I know, we could just generate some and probably will). Anyway, applying this spec results in working RGW daemons (they successfully show ListAllMyBuckets) but this Ceph warning can't be cleared: [WRN] CEPHADM_APPLY_SPEC_FAIL: Failed to apply 1 service(s): rgw.s3 rgw.s3: rgw zonegroup modify failed: Module 'rgw' is not enabled (required by command 'rgw zonegroup modify'): use `ceph mgr module enable rgw` to enable it retval: -95 Is the mentioned fix incomplete? Or how could we utilize generate_cert without issuing a health warning? I guess the simple workaround would be to create our own certs and use the same procedure as before. Thanks, Eugen [0] https://tracker.ceph.com/issues/75264 [1] https://github.com/ceph/ceph/pull/67598