Bug 2225589
| Summary: | [rgw][rfe]: rgw-restore-bucket-index should be able to recover metadata for buckets in non-default realms 5.3z5 | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | J. Eric Ivancich <ivancich> |
| Component: | RGW | Assignee: | J. Eric Ivancich <ivancich> |
| Status: | CLOSED ERRATA | QA Contact: | Madhavi Kasturi <mkasturi> |
| Severity: | high | Docs Contact: | Akash Raj <akraj> |
| Priority: | unspecified | ||
| Version: | 5.3 | CC: | ceph-eng-bugs, cephqe-warriors, mkasturi, rmandyam, tserlin, vereddy |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | 5.3z5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-16.2.10-201.el8cp | Doc Type: | Enhancement |
| Doc Text: |
Feature: rgw-restore-bucket-index now allows realm, zone, and zonegroup of bucket to be specified.
Reason: Previously rgw-restore-bucket-index would only be able to restore the indices for buckets that were in the default realm, default zonegroup, and default zone.
Result: Now rgw-restore-bucket-index is able to restore the indices for buckets that are in the non-default realm, non-default zonegroup, or non-default zone when the user specifies that info on the command-line.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-08-28 09:40:56 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
J. Eric Ivancich
2023-07-25 14:15:23 UTC
Please specify the severity of this bug. Severity is defined here: https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity. 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.3 Bug Fix update), 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-2023:4760 |