Bug 2094955 - (RHCS 6.0) [GSS] "deep-scrub starts" message missing in RHCS 5.1
Summary: (RHCS 6.0) [GSS] "deep-scrub starts" message missing in RHCS 5.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 5.1
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: 6.0
Assignee: Prashant Dhange
QA Contact: skanta
Eliska
URL:
Whiteboard:
Depends On: 2091773
Blocks: 2126050
TreeView+ depends on / blocked
 
Reported: 2022-06-08 17:22 UTC by Vikhyat Umrao
Modified: 2023-03-20 18:57 UTC (History)
19 users (show)

Fixed In Version: ceph-17.2.3-22.el9cp
Doc Type: Bug Fix
Doc Text:
.The `starts` message is added to notify that scrub or deep-scrub process has begun Previously, users were not able to determine when the scrubbing process started for a placement group (PG) because the `starts` message was missing from the cluster log. This made it difficult to calculate the time taken to scrub or deep-scrub a PG. With this fix, the `scrub starts` or the `deep-scrub starts` message appears to notify the user that scrub or deep-scrub process has begun for the PG.
Clone Of: 2091773
Environment:
Last Closed: 2023-03-20 18:56:39 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph pull 47621 0 None Merged quincy: osd/scrub: Reintroduce scrub starts message 2022-09-08 05:21:08 UTC
Red Hat Issue Tracker RHCEPH-4492 0 None None None 2022-06-08 17:31:56 UTC
Red Hat Product Errata RHBA-2023:1360 0 None None None 2023-03-20 18:57:05 UTC

Comment 31 errata-xmlrpc 2023-03-20 18:56:39 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 (Red Hat Ceph Storage 6.0 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:1360
Note You need to log in before you can comment on or make changes to this bug.