Bug 1482452 – Switch to the appropriate ceph-ansible playbook on OSP11 > OSP12 upgrade

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1482452 - Switch to the appropriate ceph-ansible playbook on OSP11 > OSP12 upgrade

Summary:	Switch to the appropriate ceph-ansible playbook on OSP11 > OSP12 upgrade

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-tripleo-heat-templates (Show other bugs)
Sub Component:
Version:	12.0 (Pike)
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	beta
Target Release:	12.0 (Pike)
Assigned To:	Giulio Fidente
QA Contact:	Marius Cornea
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:	1482897
Blocks:
	Show dependency tree / graph

Reported:	2017-08-17 06:09 EDT by Giulio Fidente
Modified:	2018-02-05 14:12 EST (History)
CC List:	7 users (show)

See Also:
Fixed In Version:	openstack-tripleo-heat-templates-7.0.0-0.20170821194253.el7ost
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-12-13 16:52:15 EST
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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
OpenStack gerrit	494336	None	None	None	2017-08-17 06:10 EDT
OpenStack gerrit	496243	None	None	None	2017-08-28 10:45 EDT
Red Hat Product Errata	RHEA-2017:3462	normal	SHIPPED_LIVE	Red Hat OpenStack Platform 12.0 Enhancement Advisory	2018-02-15 20:43:25 EST

Groups: None (edit)

Description Giulio Fidente 2017-08-17 06:09:51 EDT

Ideally users won't have to provide via parameter the playbook to run on upgrade; we should rather figure that out automatically when upgrading.

Comment 6 errata-xmlrpc 2017-12-13 16:52:15 EST

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

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