Bug 1852806 - [Tracker for BZ #1859181][BM/vsphere] Sometimes ceph status->scrub status is showing 4 idle mds though OCS cluster has only 2 MDS pods
Summary: [Tracker for BZ #1859181][BM/vsphere] Sometimes ceph status->scrub status is ...
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: ceph
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: OCS 4.8.0
Assignee: Venky Shankar
QA Contact: Pratik Surve
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-01 10:55 UTC by Pratik Surve
Modified: 2023-08-03 08:28 UTC (History)
5 users (show)

Fixed In Version: 4.8.0-416.ci
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 45349 0 None None None 2020-07-16 16:59:05 UTC
Ceph Project Bug Tracker 46495 0 None None None 2020-07-16 16:59:05 UTC
Github ceph ceph pull 36139 0 None closed mon: only dump non-empty "task status" 2021-01-21 19:10:57 UTC

Comment 4 Michael Adam 2020-07-02 20:56:23 UTC 
new bz. moving out of 4.5
Comment 5 Yaniv Kaul 2020-07-12 07:02:46 UTC 
It's unclear why is the severity high. What's the user impact?
Comment 6 Raz Tamir 2020-07-12 10:20:05 UTC 
Mainly to get attention due to comment #2.
Possible data corruption?

health: HEALTH_ERR
            1 scrub errors
            Possible data damage: 1 pg inconsistent
Comment 9 Mudit Agarwal 2020-09-21 02:28:56 UTC 
Venky, looks like this is already fixed. Please help me in determining which ceph release has this fix?
OCS 4.6 will use Ceph 4.1.z2, is the fix there?
Comment 10 Venky Shankar 2020-09-22 08:15:20 UTC 
(In reply to Mudit Agarwal from comment #9)
> Venky, looks like this is already fixed. Please help me in determining which
> ceph release has this fix?
> OCS 4.6 will use Ceph 4.1.z2, is the fix there?

I'll check and update. thx!
Comment 11 Venky Shankar 2020-09-22 08:52:33 UTC 
The fix is tracked by https://bugzilla.redhat.com/show_bug.cgi?id=1859181

Patrick  moved the fix to 4.1.z1 as per https://bugzilla.redhat.com/show_bug.cgi?id=1859181#c3
Comment 12 Mudit Agarwal 2020-09-22 10:16:49 UTC 
(In reply to Venky Shankar from comment #11)
> The fix is tracked by https://bugzilla.redhat.com/show_bug.cgi?id=1859181
> 
> Patrick  moved the fix to 4.1.z1 as per
> https://bugzilla.redhat.com/show_bug.cgi?id=1859181#c3

https://bugzilla.redhat.com/show_bug.cgi?id=1859181 is targeted to 4.2 not 4.1, so I gues you meant 4.2.z1

If that is the case we can't expect this BZ to be fixed in OCS4.6 timeframe.
Comment 13 Venky Shankar 2020-09-22 13:21:17 UTC 
(In reply to Mudit Agarwal from comment #12)
> (In reply to Venky Shankar from comment #11)
> > The fix is tracked by https://bugzilla.redhat.com/show_bug.cgi?id=1859181
> > 
> > Patrick  moved the fix to 4.1.z1 as per
> > https://bugzilla.redhat.com/show_bug.cgi?id=1859181#c3
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1859181 is targeted to 4.2 not
> 4.1, so I gues you meant 4.2.z1

oh yeh -- 4.2.z1

> 
> If that is the case we can't expect this BZ to be fixed in OCS4.6 timeframe.
Comment 14 Mudit Agarwal 2021-01-11 09:34:01 UTC 
https://bugzilla.redhat.com/show_bug.cgi?id=1859181 is targeted for RHCS 4.2z2 does it mean RHCS 4.2?
Comment 15 Venky Shankar 2021-01-19 02:05:22 UTC 
(In reply to Mudit Agarwal from comment #14)
> https://bugzilla.redhat.com/show_bug.cgi?id=1859181 is targeted for RHCS
> 4.2z2 does it mean RHCS 4.2?

The fix will be a part of RHCS 4.2z2 and will not make it to RHCS 4.1.* thereby not making to OCS 4.6.
Comment 18 Mudit Agarwal 2021-06-09 17:26:58 UTC 
BZ #1859181 is fixed in 4.2z2
Note You need to log in before you can comment on or make changes to this bug.