Bug 1506214

Summary: [UPDATES] Change the ceph-ansible playbook on overcloud updates
Product: Red Hat OpenStack Reporter: Yurii Prokulevych <yprokule>
Component: python-tripleoclientAssignee: mathieu bultel <mbultel>
Status: CLOSED ERRATA QA Contact: Yogev Rabl <yrabl>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 12.0 (Pike)CC: augol, gfidente, hbrock, jpichon, jschluet, jslagle, lbezdick, mburns, ohochman, rhel-osp-director-maint, scohen, yrabl
Target Milestone: rcKeywords: Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-tripleoclient-7.3.3-5.el7ost openstack-tripleo-common-7.6.3-4.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-13 22:18:18 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 Yurii Prokulevych 2017-10-25 12:19:34 UTC 
Description of problem. CLONE of upstream bug
---------------------------------------------

When performing an update (minor) of the overcloud with the openstack overcloud update command, we shoud switch the ceph-ansible playbookfrom the default [1] to [2].

The default playbook should be used instead for regular stack updates.

1. https://github.com/openstack/tripleo-heat-templates/blob/master/docker/services/ceph-ansible/ceph-base.yaml#L48
2. /usr/share/ceph-ansible/infrastructure-playbooks/rolling_update.yml

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
python-tripleoclient-7.3.2-0.20171011135141.456a1f3.el7ost.noarch
Comment 1 Julie Pichon 2017-11-22 16:38:01 UTC 
(POST - waiting on builds)
Comment 2 Jon Schlueter 2017-11-22 17:07:49 UTC 
openstack-tripleo-common-7.6.3-4.el7ost
Comment 5 Yogev Rabl 2017-12-05 14:57:20 UTC 
verified on python-tripleoclient-7.3.3-7.el7ost.noarch
Comment 8 errata-xmlrpc 2017-12-13 22:18:18 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/RHEA-2017:3462