Bug 1500832

Summary:	deployed-server-roles-data.yaml doesn't include the disable_upgrade_deployment flag and other flags introduced for P/12
Product:	Red Hat OpenStack	Reporter:	Marius Cornea <mcornea>
Component:	openstack-tripleo-heat-templates	Assignee:	Emilien Macchi <emacchi>
Status:	CLOSED ERRATA	QA Contact:	Gurenko Alex <agurenko>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	12.0 (Pike)	CC:	agurenko, aschultz, dbecker, emacchi, jjoyce, jschluet, jslagle, mandreou, mburns, mcornea, morazi, ohochman, rhel-osp-director-maint, tvignaud
Target Milestone:	beta	Keywords:	Triaged
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-7.0.3-0.20171019091938.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-13 22:13:59 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 Marius Cornea 2017-10-11 14:53:21 UTC

Description of problem:
deployed-server-roles-data.yaml shipped in THT doesn't include the disable_upgrade_deployment flag for compute and objectstorage roles. These are needed for being able to disable upgrade on non controller nodes so the operator can upgrade them individually.

Also the roles_data.yaml provided in the tht root looks quite different than deployed-server/deployed-server-roles-data.yaml, including the new networks attributes and several other options so I suspect we need to add these new options in deployed-server-roles-data.yaml as well?

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-7.0.1-0.20170928105409.el7ost.noarch

Comment 1 Marios Andreou 2017-10-12 14:32:40 UTC

As in comment 0 the disable_upgrade_deployment flag specifically causes problems during the upgrade as it isn't set for the (deployed server) compute and object storeage roles but should be. 

However we should probably also include the other new flags (unless it doesn't make sense to/they aren't use for deployed-server?) that are introduced in Pike for the roles_data.yaml

Assigning to DFG:DF and moving Upgrades secondary. We can post something for the disable_upgrade_deployment flag if necessary but it would be best if DFG:DF did that and also checked the other flags?

I'll post something tomorrow if someone else doesn't get round to it first.

thanks

Comment 6 Marius Cornea 2017-10-21 09:26:00 UTC

Change is in the latest build. Adding the fixed in version and moving to modified.

Comment 16 Gurenko Alex 2017-11-22 14:59:32 UTC

Verified on build 2017-11-20.1

Comment 20 errata-xmlrpc 2017-12-13 22:13:59 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