[ceph-users] Re: Upgraded to Quincy 17.2.7: some S3 buckets inaccessible

2024-04-04 Thread Lorenz Bausch
buckets except one are usable again. The rados objects seem to still exist, so we might have luck with something like rgw-restore-bucket-index. On 03/04/2024 21:43, Casey Bodley wrote: On Wed, Apr 3, 2024 at 3:09 PM Lorenz Bausch wrote: Hi Casey, thank you so much for analysis! We tested

[ceph-users] Re: Upgraded to Quincy 17.2.7: some S3 buckets inaccessible

2024-04-03 Thread Lorenz Bausch
Hi Casey, thank you so much for analysis! We tested the upgraded intensively, but the buckets in our test environment were probably too small to get dynamically resharded. after upgrading to the Quincy release, rgw would look at the wrong object names when trying to list those buckets. As

[ceph-users] Upgraded to Quincy 17.2.7: some S3 buckets inaccessible

2024-04-03 Thread Lorenz Bausch
Hi everybody, we upgraded our containerized Red Hat Pacific cluster to the latest Quincy release (Community Edition). The upgrade itself went fine, the cluster is HEALTH_OK, all daemons run the upgraded version: %< $ ceph -s cluster: id: