Bug 1616066
Summary: | ceph-ansible must allow upgrades while cluster is scrubbing | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Greg Farnum <gfarnum> | |
Component: | Ceph-Ansible | Assignee: | Guillaume Abrioux <gabrioux> | |
Status: | CLOSED ERRATA | QA Contact: | Persona non grata <nobody+410372> | |
Severity: | high | Docs Contact: | Bara Ancincova <bancinco> | |
Priority: | medium | |||
Version: | 3.1 | CC: | aschoen, ceph-eng-bugs, gabrioux, gmeno, nthomas, rperiyas, sankarshan, shan, tchandra, tpetr | |
Target Milestone: | z1 | |||
Target Release: | 3.1 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | RHEL: ceph-ansible-3.1.7-1.el7cp Ubuntu: ceph-ansible_3.1.7-2redhat1 | Doc Type: | Bug Fix | |
Doc Text: |
.`ceph-ansible` now allows upgrading a cluster that is scrubbing
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: | ||||
: | 1637038 (view as bug list) | Environment: | ||
Last Closed: | 2018-11-09 00:59:21 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: | 1584264, 1637038 |
Description
Greg Farnum
2018-08-14 20:43:53 UTC
*** Bug 1627802 has been marked as a duplicate of this bug. *** 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:3530 |