Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1581403 - OSDs are restarted twice during rolling update
OSDs are restarted twice during rolling update
Status: CLOSED ERRATA
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: Ceph-Ansible (Show other bugs)
3.1
Unspecified Unspecified
high Severity medium
: z4
: 3.0
Assigned To: leseb
Vasishta
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-05-22 12:37 EDT by Guillaume Abrioux
Modified: 2018-07-11 14:11 EDT (History)
8 users (show)

See Also:
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 14:11:11 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github ceph/ceph-ansible/pull/2451 None None None 2018-05-22 12:37 EDT
Red Hat Product Errata RHSA-2018:2177 None None None 2018-07-11 14:11 EDT

  None (edit)
Description Guillaume Abrioux 2018-05-22 12:37:01 EDT
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 13:17:39 EDT
fix will be in v3.1.0rc4 and v3.0.35
Comment 8 errata-xmlrpc 2018-07-11 14:11:11 EDT
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

Note You need to log in before you can comment on or make changes to this bug.