Convergence doesn't catch some runtime errors

Bug #1681416 reported by Thomas Herve
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
New
High
Unassigned

Bug Description

This seems to be another example of bug #1492433, but this time for convergence. This template http://paste.openstack.org/show/606037/ seems to reproduce it. It looks like we don't go through reset_state_on_error on convergence. In this case, I'm not sure if there is an actual bug, though I couldn't reproduce it without yaql.

Thomas Herve (therve)
tags: added: convergence-bugs
Changed in heat:
assignee: nobody → Jason Dunsmore (jasondunsmore)
Rico Lin (rico-lin)
Changed in heat:
milestone: pike-1 → pike-2
Revision history for this message
Rabi Mishra (rabi) wrote :

This also happens for errors in translation(RESOLVE translation where we make service calls). You can reproduce it by reducing the token expiration time(default 1hr) in keystone and creating a stack with a TestResource(with action_wait_secs more than the expiration time) and other resources depending on it.

Changed in heat:
assignee: Jason Dunsmore (jasondunsmore) → nobody
Rico Lin (rico-lin)
Changed in heat:
milestone: pike-2 → pike-3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.