Bug 1463101

Summary:	custom templates can have old heat versions
Product:	Red Hat OpenStack	Reporter:	Amit Ugol <augol>
Component:	documentation	Assignee:	Dan Macpherson <dmacpher>
Status:	CLOSED NOTABUG	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	12.0 (Pike)	CC:	dmacpher, srevivo
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-20 07:13:57 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 Amit Ugol 2017-06-20 06:54:15 UTC

Description of problem:

When customers are upgrading from previous versions with Director and are using custom templates, it should be up to them to make sure that the custom templates are up-to-date both in heat version and in content as functions can be added or removed between versions.

Information about the various versions is here:
https://docs.openstack.org/developer/heat/template_guide/hot_spec.html#heat-template-version

Setting this to High, as it might actually fail upgrades. The fix here would be to go over the custom templates and very carefully update them to a newer, supported version.

Comment 1 Amit Ugol 2017-06-20 07:13:57 UTC

So this is actually a Heat bug and it will address this issue there. No need to document it as fixing the bug will stop the version mismatch.