Back to bug 1320771
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2016-03-24 00:43:01 UTC | Target Release | --- | 8.0 |
| Alexander Chuzhoy | 2016-03-24 00:43:59 UTC | Priority | unspecified | high |
| Severity | unspecified | high | ||
| Alexander Chuzhoy | 2016-03-24 00:44:14 UTC | Keywords | Regression | |
| Zane Bitter | 2016-03-24 01:03:56 UTC | CC | rybrown | |
| Assignee | zbitter | therve | ||
| Summary | openstack-heat: No way to stop the running heat deployment. | Heat resources left IN_PROGRESS after engine restart during update | ||
| Zane Bitter | 2016-03-24 01:04:19 UTC | CC | zbitter | |
| Thomas Hervé | 2016-03-24 09:50:10 UTC | Link ID | Launchpad 1561429 | |
| Thomas Hervé | 2016-03-24 09:50:35 UTC | Link ID | OpenStack gerrit 296976 | |
| Jaromir Coufal | 2016-03-24 17:55:49 UTC | CC | jcoufal | |
| Jaromir Coufal | 2016-03-24 17:56:01 UTC | Target Milestone | --- | ga |
| Zane Bitter | 2016-03-31 01:11:16 UTC | Keywords | Regression | |
| CC | sasha | |||
| Flags | needinfo?(sasha) | |||
| Scott Lewis | 2016-04-08 14:59:00 UTC | Target Milestone | ga | --- |
| RHEL Program Management | 2016-04-08 16:08:08 UTC | Keywords | ZStream | |
| Marius Cornea | 2016-04-12 08:30:28 UTC | CC | mcornea | |
| Zane Bitter | 2016-04-12 15:35:45 UTC | CC | ohochman | |
| Zane Bitter | 2016-04-14 20:33:35 UTC | Link ID | Launchpad 1570576 | |
| Flags | needinfo?(sasha) | |||
| Zane Bitter | 2016-04-14 20:34:45 UTC | Link ID | Launchpad 1570569 | |
| John Skeoch | 2016-04-18 08:07:50 UTC | CC | yeylon | srevivo |
| Perry Myers | 2016-04-19 00:48:30 UTC | CC | pmyers | |
| Charlie Llewellyn | 2016-08-11 18:42:22 UTC | CC | cllewellyn | |
| Zane Bitter | 2016-08-24 21:17:42 UTC | Target Release | 8.0 (Liberty) | 10.0 (Newton) |
| Jaromir Coufal | 2016-10-05 19:19:10 UTC | Keywords | Triaged | |
| Target Release | 10.0 (Newton) | 11.0 (Ocata) | ||
| Red Hat Bugzilla Rules Engine | 2016-10-05 19:19:16 UTC | Target Release | 11.0 (Ocata) | 10.0 (Newton) |
| Jaromir Coufal | 2016-10-05 20:18:41 UTC | Priority | high | medium |
| Target Release | 10.0 (Newton) | 11.0 (Ocata) | ||
| Summary | Heat resources left IN_PROGRESS after engine restart during update | [Heat] Heat resources left IN_PROGRESS after engine restart during update | ||
| Zane Bitter | 2016-10-05 21:22:54 UTC | Link ID | OpenStack gerrit 378987 | |
| Jon Schlueter | 2017-01-04 13:46:25 UTC | Keywords | ZStream | |
| Zane Bitter | 2017-01-12 15:10:29 UTC | Link ID | OpenStack gerrit 378987 | OpenStack gerrit 386741 |
| Zane Bitter | 2017-01-26 15:10:05 UTC | Status | NEW | POST |
| Jon Schlueter | 2017-03-29 17:11:16 UTC | Status | POST | MODIFIED |
| CC | jschluet | |||
| Fixed In Version | openstack-heat-8.0.0-4.el7ost | |||
| errata-xmlrpc | 2017-03-30 07:56:27 UTC | Status | MODIFIED | ON_QA |
| Scott Lewis | 2017-04-10 12:53:30 UTC | Target Milestone | --- | rc |
| Thomas Hervé | 2017-05-12 13:32:46 UTC | Doc Text | Cause: While Heat was able to reset the status of resources when the state of the stack was incorrect, it failed to do so when an update has been retriggered. Consequence: The resources were stuck in progress, requiring database fixes to unblock the deployment. Fix: When Heat sets the status of the stack, it also sets the status of all the resources. Result: The resources aren't stuck in progress anymore, and the operation can be retried. |
|
| Amit Ugol | 2017-05-15 04:35:21 UTC | Status | ON_QA | VERIFIED |
| Don Domingo | 2017-05-17 00:31:43 UTC | CC | ddomingo | |
| Doc Text | Cause: While Heat was able to reset the status of resources when the state of the stack was incorrect, it failed to do so when an update has been retriggered. Consequence: The resources were stuck in progress, requiring database fixes to unblock the deployment. Fix: When Heat sets the status of the stack, it also sets the status of all the resources. Result: The resources aren't stuck in progress anymore, and the operation can be retried. | Previously, while the Orchestration service could reset the status of resource when the state of the stack was incorrect, the service failed to do so when an update was retriggered. This resulted in resources being stuck in progress, which required database fixes to unblock the deployment. With this release, the Orchestration service now sets the status of all resources when it sets the status of the stack. This prevents the resources from getting stuck in progress, allowing operations to be retried successfully. |
||
| errata-xmlrpc | 2017-05-17 19:27:58 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-05-17 15:27:58 UTC | |||
| Red Hat One Jira (issues.redhat.com) | 2021-12-10 14:49:59 UTC | Link ID | Red Hat Issue Tracker OSP-11266 |
Back to bug 1320771