Bug 1547949 - Undercloud / Overcloud Heat stack fails on: YAQL list index out of range (includes upgrades cases)
Summary: Undercloud / Overcloud Heat stack fails on: YAQL list index out of range (inc...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 13.0 (Queens)
Hardware: All
OS: Unspecified
Target Milestone: beta
: 13.0 (Queens)
Assignee: Emilien Macchi
QA Contact: Gurenko Alex
Depends On:
Blocks: 1547955 1547956 1547957
TreeView+ depends on / blocked
Reported: 2018-02-22 11:08 UTC by Sergii Golovatiuk
Modified: 2018-06-27 13:46 UTC (History)
9 users (show)

Fixed In Version: openstack-tripleo-heat-templates-8.0.0-0.20180215092255.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1547955 (view as bug list)
Last Closed: 2018-06-27 13:45:38 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1750032 0 None None None 2018-02-22 17:46:58 UTC
OpenStack gerrit 545856 0 None None None 2018-02-22 17:47:19 UTC
Red Hat Product Errata RHEA-2018:2086 0 None None None 2018-06-27 13:46:11 UTC

Description Sergii Golovatiuk 2018-02-22 11:08:20 UTC
The latest YAQL (1.1.3-2.el7) introduces backward incompatible change which was not present in YAQL (1.1.0-3.el7) and below. In order to be able to upgrade to latest YAQL and not to break any new deployments or upgrades YAQL expression should be rewritten to version which is compatible in all YAQL versions. 

Upstream bug: https://bugs.launchpad.net/tripleo/+bug/1750032
Upstream fix: https://review.openstack.org/#/c/545856/1

Comment 5 Omri Hochman 2018-03-18 13:59:55 UTC
Verified with openstack-tripleo-heat-templates-8.0.0-0.20180304031146.6cd4184.el7ost.noarch

Comment 7 errata-xmlrpc 2018-06-27 13:45:38 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.


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