Bug 1463101 - custom templates can have old heat versions
Summary: custom templates can have old heat versions
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Dan Macpherson
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-20 06:54 UTC by Amit Ugol
Modified: 2017-06-20 07:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-20 07:13:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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