Bug 1830330
| Summary: | rgw_bucket_parse_bucket_key function is holding old tenant value, when this function is executed in a loop | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Vikhyat Umrao <vumrao> |
| Component: | RGW | Assignee: | Matt Benjamin (redhat) <mbenjamin> |
| Status: | CLOSED ERRATA | QA Contact: | Tejas <tchandra> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | CC: | cbodley, ceph-eng-bugs, jbrier, kbader, mbenjamin, sweil, tchandra, tserlin, vereddy |
| Target Milestone: | z1 | Keywords: | CodeChange |
| Target Release: | 4.1 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-14.2.8-72.el8cp, ceph-14.2.8-72.el7cp | Doc Type: | Bug Fix |
| Doc Text: |
.Bucket tenanting status is interpreted correctly when `rgw_parse_bucket_key` is called
Previously, some callers of `rgw_parse_bucket_key` like `radosgw-admin bucket stats`, which processed keys in a loop, could incorrectly interpret untenanted buckets as tenanted, if some tenanted buckets were listed. If `rgw_parse_bucket_key` was called with a non-empty rgw bucket argument, it would not correctly assign an empty value for bucket::tenant when no tenant was present in the key. In {storage-product} 4.1z1 the bucket tenant member is now cleared if no tenant applies and bucket tenanting status is interpreted correctly.
|
Story Points: | --- |
| Clone Of: | 1830329 | Environment: | |
| Last Closed: | 2020-07-20 14:21:03 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1816167 | ||
|
Description
Vikhyat Umrao
2020-05-01 16:13:29 UTC
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, 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/RHSA-2020:3003 |