Bug 1592424

Summary:	UpgradeInitCommonCommand not executed on split stack environments
Product:	Red Hat OpenStack	Reporter:	Jiri Stransky <jstransk>
Component:	openstack-tripleo-heat-templates	Assignee:	Jiri Stransky <jstransk>
Status:	CLOSED ERRATA	QA Contact:	Raviv Bar-Tal <rbartal>
Severity:	high	Docs Contact:
Priority:	high
Version:	13.0 (Queens)	CC:	ccamacho, jstransk, lmarsh, mburns, morazi, rbartal
Target Milestone:	z1	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-8.0.2-43.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, the UpgradeInitCommonCommand parameter was not present in heat templates used to deploy the overcloud on pre-provisioned servers. The ‘openstack overcloud upgrade prepare’ command would not perform all of the necessary operations, which caused issues during upgrades in some environments. This update adds UpgradeInitCommonCommand to the templates used for pre-provisioned servers, allowing the ‘openstack overcloud upgrade prepare’ command to perform the necessary actions.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-19 14:27:12 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 Jiri Stransky 2018-06-18 13:54:40 UTC

When deploying with split stack (deployed server), the UpgradeInitCommonCommand [1] would not be executed because it's missing from the UpgradeInitConfig variant used in split stack overclouds [2].

[1] https://github.com/openstack/tripleo-heat-templates/blob/1065da35a04579aeb384048b163187179b855d35/environments/lifecycle/upgrade-prepare.yaml#L15-L21

[2] https://github.com/openstack/tripleo-heat-templates/blob/1065da35a04579aeb384048b163187179b855d35/deployed-server/deployed-server.yaml#L73

Comment 1 Jiri Stransky 2018-06-29 14:22:21 UTC

Merged to stable/queens.

Comment 12 errata-xmlrpc 2018-07-19 14:27:12 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/RHSA-2018:2214