Bug 1852806
| Summary: | [Tracker for BZ #1859181][BM/vsphere] Sometimes ceph status->scrub status is showing 4 idle mds though OCS cluster has only 2 MDS pods | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | Pratik Surve <prsurve> |
| Component: | ceph | Assignee: | Venky Shankar <vshankar> |
| Status: | VERIFIED --- | QA Contact: | Pratik Surve <prsurve> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.4 | CC: | ebenahar, muagarwa, nberry, sostapov, vshankar |
| Target Milestone: | --- | Keywords: | AutomationBackLog, Tracking |
| Target Release: | OCS 4.8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 4.8.0-416.ci | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 4
Michael Adam
2020-07-02 20:56:23 UTC
It's unclear why is the severity high. What's the user impact? Mainly to get attention due to comment #2. Possible data corruption? health: HEALTH_ERR 1 scrub errors Possible data damage: 1 pg inconsistent 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? (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! 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 (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. (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. https://bugzilla.redhat.com/show_bug.cgi?id=1859181 is targeted for RHCS 4.2z2 does it mean RHCS 4.2? (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. BZ #1859181 is fixed in 4.2z2 |