Bug 1506214 - [UPDATES] Change the ceph-ansible playbook on overcloud updates
Summary: [UPDATES] Change the ceph-ansible playbook on overcloud updates
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 12.0 (Pike)
Assignee: mathieu bultel
QA Contact: Yogev Rabl
Depends On:
TreeView+ depends on / blocked
Reported: 2017-10-25 12:19 UTC by Yurii Prokulevych
Modified: 2018-02-05 19:15 UTC (History)
12 users (show)

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:
Clone Of:
Last Closed: 2017-12-13 22:18:18 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1723428 0 None None None 2017-10-25 12:19:34 UTC
OpenStack gerrit 515436 0 None None None 2017-10-26 15:12:51 UTC
OpenStack gerrit 515442 0 None None None 2017-10-26 15:12:02 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

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):

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

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.


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