Bug 1517179 - [UPDATES] Switch default playbook for ceph update to site-docker.yml
Summary: [UPDATES] Switch default playbook for ceph update to site-docker.yml
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: Giulio Fidente
QA Contact: Yogev Rabl
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-24 10:19 UTC by Yurii Prokulevych
Modified: 2023-02-22 23:02 UTC (History)
14 users (show)

Fixed In Version: python-tripleoclient-7.3.3-6.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 22:23:28 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1734307 0 None None None 2017-11-24 10:23:07 UTC
OpenStack gerrit 522891 0 None stable/pike: MERGED python-tripleoclient: Move back to docker-site.yaml for ceph ansible update (I41f638b0a7df903bd95ab8d42241249d6ec1043a) 2017-11-28 04:27:46 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-11-24 10:19:25 UTC
Description of problem:
As discussed on a call we need to switch from rolling_update.yml to site-docker.yml playbook for ceph minor update in RHOS-12.

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

Comment 1 Giulio Fidente 2017-11-24 20:04:53 UTC
Updating external reference to stable/pike port

Comment 6 Giulio Fidente 2017-11-29 12:41:12 UTC
As a workaround, to make the update succeed, pass the following additional argument to the update command:

  --ceph-ansible-playbook /usr/share/ceph-ansible/site-docker.yml.sample

Comment 8 mathieu bultel 2017-11-29 12:55:50 UTC
Ack, ok sounds good as a workaround, thanks

Comment 9 Yogev Rabl 2017-12-05 14:56:16 UTC
verified on python-tripleoclient-7.3.3-7.el7ost.noarch

Comment 12 errata-xmlrpc 2017-12-13 22:23:28 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.