Back to bug 2104780
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Rachana Patel | 2022-07-07 06:36:15 UTC | Target Release | 6.1 | 5.2 |
| Rachana Patel | 2022-07-07 06:36:59 UTC | CC | vereddy, vumrao | |
| Red Hat One Jira (issues.redhat.com) | 2022-07-07 06:45:54 UTC | Link ID | Red Hat Issue Tracker RHCEPH-4677 | |
| Adam King | 2022-07-11 13:53:24 UTC | Status | NEW | ASSIGNED |
| Adam King | 2022-07-13 14:45:05 UTC | Status | ASSIGNED | POST |
| Ken Dreyer (Red Hat) | 2022-07-13 15:18:24 UTC | Fixed In Version | ceph-16.2.8-74.el8cp | |
| Status | POST | MODIFIED | ||
| CC | kdreyer | |||
| errata-xmlrpc | 2022-07-13 20:44:22 UTC | CC | tserlin | |
| Status | MODIFIED | ON_QA | ||
| Manasa | 2022-07-15 05:56:32 UTC | Flags | needinfo?(adking) | |
| CC | adking | |||
| Bipin Kunal | 2022-07-15 08:21:22 UTC | CC | bkunal | |
| Flags | needinfo?(adking) | |||
| Manasa | 2022-07-18 17:50:16 UTC | Flags | needinfo?(adking) | |
| Adam King | 2022-07-18 18:16:32 UTC | Doc Type | If docs needed, set a value | Known Issue |
| Doc Text | Cause: Buckets resharded in 5.1 may not be understandable by an RHCS 5.2 RGW daemon. Consequence: An upgrade warning/blocker was added to make sure all users upgrading to RHCS 5.2 are aware of the issue and can downgrade if they wer epreviously using RHCS 5.2 Workaround (if any): run "ceph config set mgr mgr/cephadm/no_five_one_rgw" to remove the warning/blocker and return operation to normal Result: Users will have to acknowledge they are aware of the RGW issue before they can complete an upgrade to RHCS 5.2. | |||
| Flags | needinfo?(adking) needinfo?(adking) needinfo?(adking) | |||
| Manasa | 2022-07-19 04:40:32 UTC | Status | ON_QA | VERIFIED |
| Bipin Kunal | 2022-07-19 10:07:15 UTC | Doc Text | Cause: Buckets resharded in 5.1 may not be understandable by an RHCS 5.2 RGW daemon. Consequence: An upgrade warning/blocker was added to make sure all users upgrading to RHCS 5.2 are aware of the issue and can downgrade if they wer epreviously using RHCS 5.2 Workaround (if any): run "ceph config set mgr mgr/cephadm/no_five_one_rgw" to remove the warning/blocker and return operation to normal Result: Users will have to acknowledge they are aware of the RGW issue before they can complete an upgrade to RHCS 5.2. | Cause: Buckets resharded in 5.1 may not be understandable by an RHCS 5.2 RGW daemon. Consequence: An upgrade warning/blocker was added to make sure all users upgrading to RHCS 5.2 are aware of the issue and can downgrade if they were previously using RHCS 5.2 Workaround (if any): run "ceph config set mgr mgr/cephadm/no_five_one_rgw" to remove the warning/blocker and return operation to normal Result: Users will have to acknowledge they are aware of the RGW issue before they can complete an upgrade to RHCS 5.2. |
| Akash Raj | 2022-07-29 09:29:52 UTC | Blocks | 2102272 | |
| Akash Raj | 2022-07-29 09:30:34 UTC | Flags | needinfo?(adking) | |
| CC | akraj | |||
| Adam King | 2022-07-29 16:43:57 UTC | Flags | needinfo?(adking) | |
| Akash Raj | 2022-08-03 15:41:24 UTC | Doc Text | Cause: Buckets resharded in 5.1 may not be understandable by an RHCS 5.2 RGW daemon. Consequence: An upgrade warning/blocker was added to make sure all users upgrading to RHCS 5.2 are aware of the issue and can downgrade if they were previously using RHCS 5.2 Workaround (if any): run "ceph config set mgr mgr/cephadm/no_five_one_rgw" to remove the warning/blocker and return operation to normal Result: Users will have to acknowledge they are aware of the RGW issue before they can complete an upgrade to RHCS 5.2. | .Users are warned while upgrading from {storage-product} 5.1 to {storage-product} 5.2 Previously, buckets resharded in {storage-product} 5.1, might not have been understandable by a {storage-product} 5.2 Ceph Object Gateway daemon, due to which an upgrade warning orblocker was added to make sure all users upgrading to {storage-product} 5.2 are aware of the issue and can downgrade if they were previously using {storage-product} 5.2. As a workaround, run `ceph config set mgr mgr/cephadm/no_five_one_rgw` to remove the warning or blocker and return all operations to normal. Users have to acknowledge that they are aware of the Ceph Object Gateway issue before they upgrade to {storage-product} 5.2. |
| Flags | needinfo?(adking) | |||
| Adam King | 2022-08-03 17:20:14 UTC | Flags | needinfo?(adking) | |
| Doc Text | .Users are warned while upgrading from {storage-product} 5.1 to {storage-product} 5.2 Previously, buckets resharded in {storage-product} 5.1, might not have been understandable by a {storage-product} 5.2 Ceph Object Gateway daemon, due to which an upgrade warning orblocker was added to make sure all users upgrading to {storage-product} 5.2 are aware of the issue and can downgrade if they were previously using {storage-product} 5.2. As a workaround, run `ceph config set mgr mgr/cephadm/no_five_one_rgw` to remove the warning or blocker and return all operations to normal. Users have to acknowledge that they are aware of the Ceph Object Gateway issue before they upgrade to {storage-product} 5.2. | .Users are warned while upgrading from {storage-product} 5.0 or 5.1 to {storage-product} 5.2 Previously, buckets resharded in {storage-product} 5.1, might not have been understandable by a {storage-product} 5.2 Ceph Object Gateway daemon, due to which an upgrade warning/blocker was added to make sure all users upgrading to {storage-product} 5.2 are aware of the issue and can downgrade if they were previously using {storage-product} 5.1 with object storage. As a workaround, users not using object storage or upgrading from a version other than 5.1 can run `ceph config set mgr mgr/cephadm/no_five_one_rgw --force` to remove the warning/blocker and return all operations to normal. By setting this config option users have acknowledged that they are aware of the Ceph Object Gateway issue before they upgrade to {storage-product} 5.2. |
||
| Akash Raj | 2022-08-05 06:33:15 UTC | Doc Text | .Users are warned while upgrading from {storage-product} 5.0 or 5.1 to {storage-product} 5.2 Previously, buckets resharded in {storage-product} 5.1, might not have been understandable by a {storage-product} 5.2 Ceph Object Gateway daemon, due to which an upgrade warning/blocker was added to make sure all users upgrading to {storage-product} 5.2 are aware of the issue and can downgrade if they were previously using {storage-product} 5.1 with object storage. As a workaround, users not using object storage or upgrading from a version other than 5.1 can run `ceph config set mgr mgr/cephadm/no_five_one_rgw --force` to remove the warning/blocker and return all operations to normal. By setting this config option users have acknowledged that they are aware of the Ceph Object Gateway issue before they upgrade to {storage-product} 5.2. | .Users are warned while upgrading from {storage-product} 5.0 or 5.1 to {storage-product} 5.2 Previously, buckets resharded in {storage-product} 5.1, might not have been understandable by a {storage-product} 5.2 Ceph Object Gateway daemon, due to which an upgrade warning/blocker was added to make sure all users upgrading to {storage-product} 5.2 are aware of the issue and can downgrade if they were previously using {storage-product} 5.1 with object storage. As a workaround, users not using object storage or upgrading from a version other than 5.1 can run `ceph config set mgr mgr/cephadm/no_five_one_rgw --force` to remove the warning/blocker and return all operations to normal. By setting this config option users have acknowledged that they are aware of the Ceph Object Gateway issue before they upgrade to {storage-product} 5.2. |
| Akash Raj | 2022-08-05 08:47:50 UTC | Doc Text | .Users are warned while upgrading from {storage-product} 5.0 or 5.1 to {storage-product} 5.2 Previously, buckets resharded in {storage-product} 5.1, might not have been understandable by a {storage-product} 5.2 Ceph Object Gateway daemon, due to which an upgrade warning/blocker was added to make sure all users upgrading to {storage-product} 5.2 are aware of the issue and can downgrade if they were previously using {storage-product} 5.1 with object storage. As a workaround, users not using object storage or upgrading from a version other than 5.1 can run `ceph config set mgr mgr/cephadm/no_five_one_rgw --force` to remove the warning/blocker and return all operations to normal. By setting this config option users have acknowledged that they are aware of the Ceph Object Gateway issue before they upgrade to {storage-product} 5.2. | .Users are warned while upgrading to {storage-product} 5.2 Previously, buckets resharded in {storage-product} 5, might not have been understandable by a {storage-product} 5.2 Ceph Object Gateway daemon, due to which an upgrade warning/blocker was added to make sure all users upgrading to {storage-product} 5.2 are aware of the issue and can downgrade if they were previously using {storage-product} 5.1 with object storage. As a workaround, users not using object storage or upgrading from a version other than 5.1 can run `ceph config set mgr mgr/cephadm/no_five_one_rgw --force` to remove the warning/blocker and return all operations to normal. By setting this config option users have acknowledged that they are aware of the Ceph Object Gateway issue before they upgrade to {storage-product} 5.2. |
| Adam King | 2022-08-08 12:33:00 UTC | Doc Text | .Users are warned while upgrading to {storage-product} 5.2 Previously, buckets resharded in {storage-product} 5, might not have been understandable by a {storage-product} 5.2 Ceph Object Gateway daemon, due to which an upgrade warning/blocker was added to make sure all users upgrading to {storage-product} 5.2 are aware of the issue and can downgrade if they were previously using {storage-product} 5.1 with object storage. As a workaround, users not using object storage or upgrading from a version other than 5.1 can run `ceph config set mgr mgr/cephadm/no_five_one_rgw --force` to remove the warning/blocker and return all operations to normal. By setting this config option users have acknowledged that they are aware of the Ceph Object Gateway issue before they upgrade to {storage-product} 5.2. | .Users are warned while upgrading to {storage-product} 5.2 Previously, buckets resharded in {storage-product} 5.1, might not be understandable by a {storage-product} 5.2 Ceph Object Gateway daemon, due to which an upgrade warning/blocker was added to make sure all users upgrading to {storage-product} 5.2 are aware of the issue and can downgrade if they were previously using {storage-product} 5.1 with object storage. As a workaround, users not using object storage or upgrading from a version other than 5.1 can run `ceph config set mgr mgr/cephadm/no_five_one_rgw --force` to remove the warning/blocker and return all operations to normal. By setting this config option users have acknowledged that they are aware of the Ceph Object Gateway issue before they upgrade to {storage-product} 5.2. |
| errata-xmlrpc | 2022-08-09 10:01:28 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-08-09 17:39:24 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2022-08-09 17:39:24 UTC | |||
| errata-xmlrpc | 2022-08-09 17:39:55 UTC | Link ID | Red Hat Product Errata RHSA-2022:5997 |
Back to bug 2104780