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 1581403

Summary: OSDs are restarted twice during rolling update
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Guillaume Abrioux <gabrioux>
Component: Ceph-AnsibleAssignee: Sébastien Han <shan>
Status: CLOSED ERRATA QA Contact: Vasishta <vashastr>
Severity: medium Docs Contact:
Priority: high    
Version: 3.1CC: adeza, aschoen, ceph-eng-bugs, gmeno, hnallurv, nthomas, sankarshan, tserlin
Target Milestone: z4   
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-ansible-3.0.35-1.el7cp Ubuntu: ceph-ansible_3.0.35-2redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-11 18:11:11 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 Guillaume Abrioux 2018-05-22 16:37:01 UTC 
Description of problem:

During a rolling update, OSDs are restarted twice currently. Once, by the
handler in roles/ceph-defaults/handlers/main.yml and a second time by tasks
in the rolling_update playbook.


Version-Release number of selected component (if applicable):


How reproducible:

Try to apply a config change on an existing cluster.

Steps to Reproduce:
1. Deploy a cluster
2. Upgrade this cluster with rolling_update playbook

Actual results:

OSDs are restarted twice

Expected results:

OSDs are restarted only once
Comment 3 Guillaume Abrioux 2018-05-22 17:17:39 UTC 
fix will be in v3.1.0rc4 and v3.0.35
Comment 8 errata-xmlrpc 2018-07-11 18:11:11 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-2018:2177