[Heat] heat stack-list does not work after stack update

Bug #1693845 reported by Javier Diaz Jr on 2017-05-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
High
Alexey Stupnikov

Bug Description

Backport to MOS 7 - Kilo

https://bugs.launchpad.net/heat/+bug/1477812

Detailed bug description:

Tried creating template https://github.com/openstack/heat-templates/blob/master/hot/hello_world.yaml and since nova could not succeed, ResourceFailure was raised and stack went to CREATE FAILED state.

Now If we modify one of the parameters consumed by template, lets say 'key_name' to 'keyname', and perform an update, and ResourceFailure again occurs stack will be moved to UPDATE FAILED state.

After the above operations heat stack-list breaks with error:
The Parameter (keyname) was not provided

Steps to reproduce:

Modify parameters in template and perform a stack update. Then performn a stack-list command.

Expected results:

Stack-list should output.

Actual result:

You get a message such as:

The Parameter (parameter changed) was not provided

Reproducibility:

100%

Workaround:

Update parameter back to original parameter

Impact:

Unable to use heat stack-list via CLI or Horizon after update is made.

Changed in mos:
importance: Undecided → High
status: New → Won't Fix
status: Won't Fix → Confirmed
Changed in mos:
assignee: MOS Maintenance (mos-maintenance) → Alexey Stupnikov (astupnikov)

Fix proposed to branch: openstack-ci/fuel-7.0/2015.1.0
Change author: Rakesh H S <email address hidden>
Review: https://review.fuel-infra.org/37305

Changed in mos:
status: Confirmed → In Progress
Changed in mos:
milestone: 7.0-updates → 7.0-mu-9

Reviewed: https://review.fuel-infra.org/37305
Submitter: Denis V. Meltsaykin <email address hidden>
Branch: openstack-ci/fuel-7.0/2015.1.0

Commit: 0bd9fee74d72f93c9a04151a6531a54d4f0f3d73
Author: Rakesh H S <email address hidden>
Date: Thu Nov 30 07:42:40 2017

Fix stack-list after failed update

When a update is being performed, the existing template is updated
incrementally as resources change. Now if update fails, template will
have mix of resources from existing and new template. Hence we need to
ensure we have the user params of both.

Change-Id: I9e6831c58b167809e3faed519d2fb4f7c61244fc
Closes-Bug: #1693845

Changed in mos:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers