Bug 1463101 - custom templates can have old heat versions
custom templates can have old heat versions
Status: CLOSED NOTABUG
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation (Show other bugs)
12.0 (Pike)
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Dan Macpherson
RHOS Documentation Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-20 02:54 EDT by Amit Ugol
Modified: 2017-06-20 03:13 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-06-20 03:13:57 EDT
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)

  None (edit)
Description Amit Ugol 2017-06-20 02:54:15 EDT
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 03:13:57 EDT
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.