2015-04-21 11:06:48 |
Kairat Kushaev |
bug |
|
|
added bug |
2015-04-21 11:06:48 |
Kairat Kushaev |
attachment added |
|
murano_first https://bugs.launchpad.net/bugs/1446575/+attachment/4380503/+files/murano_first |
|
2015-04-21 11:06:57 |
Kairat Kushaev |
heat: assignee |
|
Kairat Kushaev (kkushaev) |
|
2015-04-21 11:07:15 |
Kairat Kushaev |
attachment added |
|
murano_second https://bugs.launchpad.net/heat/+bug/1446575/+attachment/4380504/+files/murano_second |
|
2015-04-21 11:07:33 |
Kairat Kushaev |
attachment added |
|
murano_third https://bugs.launchpad.net/heat/+bug/1446575/+attachment/4380505/+files/murano_third |
|
2015-04-21 11:11:54 |
Kairat Kushaev |
description |
During testing of Murano we faced with the following issue:
Heat stack is handing on in UPDATE_IN_PROGRESS state or DELETE_IN_PROGRESS case when we are trying to create and update the stack in series.
The case is the following:
1. Create the stack with murano_first template (using neutron router in devstack).
2. Update the stack with murano_second template using m1.express flavor( flavor RAM value should be enough to raise No valid host found in Nova)
The stack is failing because of no valid host found error.
3. Update the failed stack with murano_third (using neutron public net as floating network).
The stack is failing again because of no valid host found error.
4. Delete the stack.
Expected result: the stack has been deleted successfully.
Actual result: the stack is hanging on in DELETE_IN_PROGRESS
This is specialty of Murano that it sends update requests in a bunch and doesn't check that the previous update was successful.
But we definitely need to treat properly such kind of cases. |
During testing of Murano we faced with the following issue:
Heat stack is handing on in UPDATE_IN_PROGRESS state or DELETE_IN_PROGRESS case when we are trying to create and update the stack in series.
The case is the following:
1. Create the stack with murano_first template (using neutron router in devstack).
2. Update the stack with murano_second template using m1.express flavor( flavor RAM value should be enough to raise No valid host found in Nova)
The stack is failing because of no valid host found error.
3. Update the failed stack with murano_third (using neutron public net as floating network).
The stack is failing again because of no valid host found error.
4. Delete the stack.
Expected result: the stack has been deleted successfully.
Actual result: the stack is hanging on in DELETE_IN_PROGRESS
This is specialty of Murano that it sends update requests in a bunch and doesn't check that the previous update was successful.
But we definitely need to treat properly such kind of cases.
When I looked into the heat log I found that because of some reason heat generated Invalid Template Reference error. |
|
2015-04-21 13:55:11 |
OpenStack Infra |
heat: status |
New |
In Progress |
|
2015-04-21 15:25:42 |
Kairat Kushaev |
tags |
|
kilo-rc-potential |
|
2015-04-27 12:36:27 |
Kairat Kushaev |
tags |
kilo-rc-potential |
juno-backport-potential kilo-rc-potential |
|
2015-04-28 07:54:35 |
Angus Salkeld |
heat: milestone |
|
liberty-1 |
|
2015-04-28 07:54:38 |
Angus Salkeld |
heat: importance |
Undecided |
Medium |
|
2015-04-28 07:54:59 |
Angus Salkeld |
heat: importance |
Medium |
High |
|
2015-04-30 13:22:55 |
Thierry Carrez |
tags |
juno-backport-potential kilo-rc-potential |
juno-backport-potential |
|
2015-04-30 19:43:19 |
Zane Bitter |
bug |
|
|
added subscriber Zane Bitter |
2015-05-07 08:07:49 |
Kairat Kushaev |
attachment added |
|
Backup.pdf https://bugs.launchpad.net/heat/+bug/1446575/+attachment/4392793/+files/Backup.pdf |
|
2015-05-11 04:16:28 |
OpenStack Infra |
heat: status |
In Progress |
Fix Committed |
|
2015-06-04 22:50:47 |
Zane Bitter |
tags |
juno-backport-potential |
juno-backport-potential kilo-backport-potential |
|
2015-06-24 12:45:08 |
Thierry Carrez |
heat: status |
Fix Committed |
Fix Released |
|
2015-06-25 08:40:59 |
Steven Hardy |
nominated for series |
|
heat/kilo |
|
2015-06-25 08:40:59 |
Steven Hardy |
bug task added |
|
heat/kilo |
|
2015-06-25 10:00:04 |
OpenStack Infra |
heat/kilo: status |
New |
Fix Committed |
|
2015-07-23 21:54:40 |
Alan Pevec |
heat/kilo: milestone |
|
2015.1.1 |
|
2015-07-29 21:43:37 |
Alan Pevec |
heat/kilo: status |
Fix Committed |
Fix Released |
|
2015-08-25 20:51:20 |
Steve Baker |
tags |
juno-backport-potential kilo-backport-potential |
in-stable-kilo juno-backport-potential |
|
2015-09-17 22:35:25 |
Zane Bitter |
nominated for series |
|
heat/juno |
|
2015-09-17 22:35:25 |
Zane Bitter |
bug task added |
|
heat/juno |
|
2015-10-01 20:39:44 |
OpenStack Infra |
heat/juno: status |
New |
In Progress |
|
2015-10-01 20:39:44 |
OpenStack Infra |
heat/juno: assignee |
|
Zane Bitter (zaneb) |
|
2015-10-11 20:43:15 |
OpenStack Infra |
heat/juno: status |
In Progress |
Fix Committed |
|
2015-10-13 14:34:51 |
Zane Bitter |
tags |
in-stable-kilo juno-backport-potential |
in-stable-juno in-stable-kilo |
|
2015-10-15 10:17:42 |
Thierry Carrez |
heat: milestone |
liberty-1 |
5.0.0 |
|
2015-11-14 15:04:58 |
Alan Pevec |
heat/juno: milestone |
|
2014.2.4 |
|
2015-11-19 21:41:41 |
Alan Pevec |
heat/juno: status |
Fix Committed |
Fix Released |
|