Bug 1637038
| Summary: | [RHCS2]ceph-ansible must allow upgrades while cluster is scrubbing | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Tomas Petr <tpetr> |
| Component: | Ceph-Ansible | Assignee: | Ram Raja <rraja> |
| Status: | CLOSED ERRATA | QA Contact: | Persona non grata <nobody+410372> |
| Severity: | high | Docs Contact: | Bara Ancincova <bancinco> |
| Priority: | medium | ||
| Version: | 2.5 | CC: | aschoen, ceph-eng-bugs, ceph-qe-bugs, gabrioux, gfarnum, gmeno, hnallurv, kdreyer, nthomas, rperiyas, sankarshan, shan, tchandra, tpetr, tserlin |
| Target Milestone: | z3 | ||
| Target Release: | 2.5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-ansible-3.0.47-1.el7cp Ubuntu: ceph-ansible_3.0.47-2redhat1 | Doc Type: | Bug Fix |
| Doc Text: |
The ceph-ansible utility previously required all placement groups (PGs) in a cluster to be in the active+clean state. Consequently, the noscrub flag had to be set before upgrading the cluster to prevent PGs to be in the active+clean+scrubbing state. With this update, ceph-ansible allows upgrading a cluster even when the cluster is scrubbing.
|
Story Points: | --- |
| Clone Of: | 1616066 | Environment: | |
| Last Closed: | 2018-11-27 21:15:40 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: | 1616066 | ||
| Bug Blocks: | |||
|
Comment 4
Sébastien Han
2018-10-10 16:31:15 UTC
(In reply to leseb from comment #4) > Ramana, please push and adapt if necessary this change > https://github.com/ceph/ceph-ansible/pull/3164 in the stable-3.0 branch > upstream. Thanks Done. See here, https://github.com/ceph/ceph-ansible/pull/3225 Once the PR is merged in stable-3.0 branch, is there something else that needs to be done? 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:3689 |