Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1569689

Summary: MDS rolling-upgrade process needs to be changed to follow new recommendations
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Patrick Donnelly <pdonnell>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED ERRATA QA Contact: Ameena Suhani S H <amsyedha>
Severity: high Docs Contact:
Priority: high    
Version: 3.0CC: adeza, amsyedha, aschoen, ceph-eng-bugs, gabrioux, gmeno, hgurav, hnallurv, kdreyer, nthomas, pasik, pdonnell, rperiyas, tserlin, vashastr
Target Milestone: z2   
Target Release: 3.3   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: RHEL: ceph-ansible-3.2.32-1.el7cp Ubuntu: ceph-ansible_3.2.32-2redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-19 17:58:55 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:

Description Patrick Donnelly 2018-04-19 19:49:26 UTC 
Description of problem:

The MDS rolling-upgrade procedure should follow the guide documented in this PR:

https://github.com/ceph/ceph/pull/21263/files

Note, the current upgrade procedure in the master branch is for Mimic only.
Comment 6 Ken Dreyer (Red Hat) 2018-05-30 14:08:24 UTC 
https://github.com/ceph/ceph-ansible/pull/2549 still in progress upstream. Re-targeting this BZ to a later product release.
Comment 7 Harish NV Rao 2018-09-18 14:13:10 UTC 
(In reply to Ken Dreyer (Red Hat) from comment #6)
> https://github.com/ceph/ceph-ansible/pull/2549 still in progress upstream.
> Re-targeting this BZ to a later product release.

@Ken, looks like above is still in progress. Can you please check and move this BZ out of z1 if it's not going to be fixed in 3.1z1?
Comment 13 Giridhar Ramaraju 2019-08-05 13:08:13 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 14 Giridhar Ramaraju 2019-08-05 13:09:44 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 21 Ameena Suhani S H 2019-11-27 05:44:43 UTC 
Verified using ceph-ansible-3.2.36-1.
Moving it to "VERIFIED" state
Comment 23 errata-xmlrpc 2019-12-19 17:58:55 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/RHSA-2019:4353