Bug 1484052 - [UPDATES] tasks with step == "0" are never executed
Summary: [UPDATES] tasks with step == "0" are never executed
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 12.0 (Pike)
Assignee: mathieu bultel
QA Contact: Yurii Prokulevych
Depends On:
TreeView+ depends on / blocked
Reported: 2017-08-22 14:29 UTC by Yurii Prokulevych
Modified: 2018-02-05 19:12 UTC (History)
7 users (show)

Fixed In Version: openstack-tripleo-heat-templates-7.0.3-0.20171023134947.8da5e1f.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 21:53:35 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1712498 0 None None None 2017-08-23 08:22:22 UTC
OpenStack gerrit 496397 0 None None None 2017-08-22 20:17:20 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Yurii Prokulevych 2017-08-22 14:29:13 UTC
Description of problem:
In the generated playbook for minor updates update_steps_tasks.yaml is included in a loop like this: '''with_sequence: count=5'''

The problem is that with this invocation iteration starts with '1', and we still have tasks referencing 0.

E.g: https://review.openstack.org/#/c/486567/34/puppet/services/tripleo-packages.yaml@63

Version-Release number of selected component (if applicable):

Comment 1 mathieu bultel 2017-08-22 20:04:54 UTC
Nice catch,
We can specify the start with:
        - start: 0
I guess it should fix the issue.

Comment 4 Yurii Prokulevych 2017-11-21 13:12:56 UTC
Patch present in openstack-tripleo-heat-templates-7.0.3-10.el7ost.noarch

Comment 7 errata-xmlrpc 2017-12-13 21:53:35 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.