Bug 1548481
| Summary: | [CEE/SD] inconsistent PG - omap_digest_mismatch_oi discovered after 2.4a -> 2.5 update, plus several "bad complete for" | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Tomas Petr <tpetr> | |
| Component: | RADOS | Assignee: | David Zafman <dzafman> | |
| Status: | CLOSED ERRATA | QA Contact: | ceph-qe-bugs <ceph-qe-bugs> | |
| Severity: | urgent | Docs Contact: | Aron Gunn <agunn> | |
| Priority: | urgent | |||
| Version: | 2.5 | CC: | agunn, bniver, ceph-eng-bugs, dzafman, flucifre, gmeno, hklein, hnallurv, jdurgin, karan, kchai, kdreyer, mhackett, nlevine, pablo.iranzo, rwheeler, shmohan, tserlin, vumrao | |
| Target Milestone: | z1 | |||
| Target Release: | 2.5 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | RHEL: ceph-10.2.10-17.el7cp Ubuntu: ceph_10.2.10-14redhat1xenial | Doc Type: | Bug Fix | |
| Doc Text: |
.Slow OSD startup after upgrading to Red Hat Ceph Storage 2.5
Ceph Storage Clusters that have large `omap` databases experience slow OSD startup due to scanning and repairing during the upgrade from Red Hat Ceph Storage 2.4 to 2.5. The rolling update may take longer than the specified time out of 5 minutes. Before running the Ansible `rolling_update.yml` playbook, set the `handler_health_osd_check_delay` option to 180 in the `group_vars/all.yml` file.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1549293 (view as bug list) | Environment: | ||
| Last Closed: | 2018-02-28 01:34:24 UTC | 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1536401, 1558185 | |||
|
Comment 5
Josh Durgin
2018-02-23 16:27:07 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/RHBA-2018:0371 |