Back to bug 1314080
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2016-03-02 20:52:07 UTC | Target Release | --- | 8.0 |
| Joe Talerico | 2016-03-02 20:53:56 UTC | Priority | unspecified | high |
| Severity | unspecified | high | ||
| Zane Bitter | 2016-03-09 21:24:57 UTC | Assignee | zbitter | sbaker |
| Zane Bitter | 2016-03-23 21:24:01 UTC | Target Release | 8.0 | 10.0 |
| CC | zbitter | |||
| Steve Baker | 2016-03-23 21:26:51 UTC | Link ID | Launchpad 1561214 | |
| John Skeoch | 2016-04-18 08:07:31 UTC | CC | yeylon | srevivo |
| Perry Myers | 2016-04-19 01:11:13 UTC | CC | pmyers | |
| Jaromir Coufal | 2016-09-27 02:10:35 UTC | CC | jcoufal | |
| Flags | needinfo?(sbaker) | |||
| Jaromir Coufal | 2016-09-27 02:10:56 UTC | Keywords | Triaged | |
| Priority | high | medium | ||
| Zane Bitter | 2016-09-27 14:01:12 UTC | Link ID | Launchpad 1570576 | |
| Zane Bitter | 2016-09-27 14:02:47 UTC | CC | akaris | |
| Steve Baker | 2016-09-28 11:59:26 UTC | Status | NEW | MODIFIED |
| Link ID | OpenStack gerrit 305306 | |||
| Flags | needinfo?(sbaker) | |||
| Lon Hohberger | 2016-09-28 21:00:34 UTC | Status | MODIFIED | ASSIGNED |
| Fixed In Version | openstack-heat-7.0.0-0.20160923054727.e4c4c56.el7ost | |||
| Lon Hohberger | 2016-09-28 21:00:48 UTC | Status | ASSIGNED | MODIFIED |
| Jon Schlueter | 2016-09-29 13:50:03 UTC | CC | jschluet | |
| Target Milestone | --- | rc | ||
| errata-xmlrpc | 2016-09-29 20:55:28 UTC | Status | MODIFIED | ON_QA |
| Jaromir Coufal | 2016-10-05 21:43:14 UTC | Target Milestone | rc | ga |
| Scott Lewis | 2016-10-11 16:25:29 UTC | Target Milestone | ga | rc |
| Amit Ugol | 2016-11-02 07:15:49 UTC | Status | ON_QA | VERIFIED |
| Zane Bitter | 2016-11-22 17:40:01 UTC | Doc Text | Feature: heat-manage now supports a "heat-manage reset_stack_status" subcommand. Reason: if heat-engine is unable to contact the database, any stacks that were in progress will remain stuck there due to outdated information in the database. In the event a failure like this occurs, administrators need a way to reset the status to allow these stacks to be updated again. Result: Administrators can now reset stuck stacks using the "heat-manage reset_stack_status" command. | |
| Doc Type | Bug Fix | Enhancement | ||
| Martin Lopes | 2016-11-30 05:51:59 UTC | CC | mlopes | |
| Doc Text | Feature: heat-manage now supports a "heat-manage reset_stack_status" subcommand. Reason: if heat-engine is unable to contact the database, any stacks that were in progress will remain stuck there due to outdated information in the database. In the event a failure like this occurs, administrators need a way to reset the status to allow these stacks to be updated again. Result: Administrators can now reset stuck stacks using the "heat-manage reset_stack_status" command. | With this enhancement, `heat-manage` now supports a `heat-manage reset_stack_status` subcommand. This was added because of the scenario where `heat-engine` was unable to contact the database, causing any stacks that were in-progress to remain stuck due to outdated database information. When this occurred, administrators needed a way to reset the status to allow these stacks to be updated again. As a result, administrators can now use the `heat-manage reset_stack_status` command to reset a stuck stack. |
||
| Martin Lopes | 2016-12-01 01:01:59 UTC | Doc Text | With this enhancement, `heat-manage` now supports a `heat-manage reset_stack_status` subcommand. This was added because of the scenario where `heat-engine` was unable to contact the database, causing any stacks that were in-progress to remain stuck due to outdated database information. When this occurred, administrators needed a way to reset the status to allow these stacks to be updated again. As a result, administrators can now use the `heat-manage reset_stack_status` command to reset a stuck stack. | With this enhancement, `heat-manage` now supports a `heat-manage reset_stack_status` subcommand. This was added to manage situations where `heat-engine` was unable to contact the database, causing any stacks that were in-progress to remain stuck due to outdated database information. When this occurred, administrators needed a way to reset the status to allow these stacks to be updated again. As a result, administrators can now use the `heat-manage reset_stack_status` command to reset a stuck stack. |
| errata-xmlrpc | 2016-12-14 14:00:42 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-12-14 15:25:17 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-12-14 10:25:17 UTC |
Back to bug 1314080