Bug 1484052

Summary: [UPDATES] tasks with step == "0" are never executed
Product: Red Hat OpenStack Reporter: Yurii Prokulevych <yprokule>
Component: openstack-tripleo-heat-templatesAssignee: mathieu bultel <mbultel>
Status: CLOSED ERRATA QA Contact: Yurii Prokulevych <yprokule>
Severity: high Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: aschultz, lbezdick, mandreou, mbultel, mburns, rhel-osp-director-maint, tvignaud
Target Milestone: rcKeywords: Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-7.0.3-0.20171023134947.8da5e1f.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-13 21:53:35 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:

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):
-------------------------------------------------------------
openstack-tripleo-heat-templates-7.0.0-0.20170805163048.el7ost.noarch
Comment 1 mathieu bultel 2017-08-22 20:04:54 UTC 
Nice catch,
We can specify the start with:
      with_sequence:
        - 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.

https://access.redhat.com/errata/RHEA-2017:3462