Login
Log in using an SSO provider:
Fedora Account System
Red Hat Associate
Red Hat Customer
Login using a Red Hat Bugzilla account
Forgot Password
Create an Account
Red Hat Bugzilla – Bug 2052516
Home
New
Search
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh109 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
Migrated Products
[?]
This site requires JavaScript to be enabled to function correctly, please enable it.
Bug 2052516
-
[rgw-multisite] Incorrect reporting of recovering shards in sync status
Summary:
[rgw-multisite] Incorrect reporting of recovering shards in sync status
Keywords
:
UserExperience
Status
:
CLOSED DUPLICATE of
bug 2105309
Alias:
None
Product:
Red Hat Ceph Storage
Classification:
Red Hat Storage
Component:
RGW-Multisite
Sub Component:
---
Version:
4.3
Hardware:
x86_64
OS:
Linux
Priority:
unspecified
Severity:
medium
Target Milestone:
---
Target Release
:
5.3
Assignee:
Matt Benjamin (redhat)
QA Contact:
Vidushi Mishra
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+
depends on
/
blocked
Reported:
2022-02-09 13:37 UTC by
Gaurav Sitlani
Modified:
2022-12-14 08:10 UTC (
History
)
CC List:
8 users
(
show
)
akraj
cbodley
ceph-eng-bugs
kdreyer
smanjara
tserlin
vereddy
vimishra
Fixed In Version:
ceph-16.2.10-48.el8cp
Doc Type:
No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
2022-09-30 04:40:24 UTC
Embargoed:
Dependent Products:
Red Hat OpenShift Container Storage
Red Hat OpenShift Data Foundation
Red Hat OpenStack
Attachments
(Terms of Use)
Links
System
ID
Private
Priority
Status
Summary
Last Updated
Red Hat Issue Tracker
RHCEPH-3128
0
None
None
None
2022-02-09 13:45:36 UTC
Comment 23
Vidushi Mishra
2022-09-30 04:40:24 UTC
*** This bug has been marked as a duplicate of
bug 2105309
***
Note
You need to
log in
before you can comment on or make changes to this bug.