Back to bug 1307125
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2016-02-12 18:45:03 UTC | Target Release | --- | 8.0 |
| Mike Burns | 2016-02-12 18:55:06 UTC | Target Release | 8.0 | 7.0 |
| Alexander Chuzhoy | 2016-02-12 18:59:10 UTC | CC | sasha | |
| Summary | Heat engine crashes during osp-d update from 7.1 to 7.3 | Heat engine crashes during osp-d update from 7.1 and from 7.0 to 7.3 | ||
| Alexander Chuzhoy | 2016-02-12 18:59:27 UTC | Priority | unspecified | high |
| Target Milestone | --- | y3 | ||
| RHEL Program Management | 2016-02-12 19:05:16 UTC | Keywords | ZStream | |
| Omri Hochman | 2016-02-12 20:34:27 UTC | CC | ohochman | |
| Zane Bitter | 2016-02-15 14:15:57 UTC | Doc Text | Cause: If heat-engine's connection to the database is lost during startup, it may fail to start. Consequence: When updating a machine on which both the database and heat-engine are running using yum alone (as is the case when updating a TripleO undercloud), heat-engine may not be running after the update. Workaround (if any): If heat-engine is not running after the yum update (as shown by "systemctl status openstack-heat-engine.service), start heat-engine explicitly using the command "systemctl start openstack-heat-engine.service". Result: heat-engine will be running again. | |
| Doc Type | Bug Fix | Known Issue | ||
| Angus Thomas | 2016-02-15 14:29:46 UTC | Blocks | 1308576 | |
| Angus Thomas | 2016-02-15 14:34:43 UTC | Status | NEW | CLOSED |
| CC | athomas | |||
| Resolution | --- | WONTFIX | ||
| Last Closed | 2016-02-15 09:34:43 UTC | |||
| Jaromir Coufal | 2016-02-15 15:42:54 UTC | Status | CLOSED | NEW |
| CC | jcoufal | |||
| Resolution | WONTFIX | --- | ||
| Keywords | Reopened | |||
| Steve Baker | 2016-02-15 22:28:18 UTC | Assignee | zbitter | sbaker |
| Steve Baker | 2016-02-15 22:29:59 UTC | Status | NEW | ASSIGNED |
| Steve Baker | 2016-02-16 00:12:09 UTC | Link ID | OpenStack gerrit 280451 | |
| Steve Baker | 2016-02-16 02:28:26 UTC | Status | ASSIGNED | POST |
| Jaromir Coufal | 2016-02-16 11:40:21 UTC | CC | jcoufal | |
| Mike Burns | 2016-02-16 13:03:41 UTC | Target Milestone | y3 | z4 |
| Jaromir Coufal | 2016-02-16 14:06:00 UTC | CC | jcoufal | |
| Zane Bitter | 2016-02-16 17:48:43 UTC | CC | zbitter | |
| Doc Text | Cause: If heat-engine's connection to the database is lost during startup, it may fail to start. Consequence: When updating a machine on which both the database and heat-engine are running using yum alone (as is the case when updating a TripleO undercloud), heat-engine may not be running after the update. Workaround (if any): If heat-engine is not running after the yum update (as shown by "systemctl status openstack-heat-engine.service), start heat-engine explicitly using the command "systemctl start openstack-heat-engine.service". Result: heat-engine will be running again. | Cause: If the database is not available while heat-engine is starting up, it will fail to start. Consequence: When updating a machine on which both the database and heat-engine are running using yum alone (as is the case when updating a TripleO undercloud), heat-engine may not be running after the update. Workaround (if any): If heat-engine is not running after the yum update (as shown by "systemctl status openstack-heat-engine.service), start heat-engine explicitly using the command "systemctl start openstack-heat-engine.service". Result: heat-engine will be running again. |
||
| Zane Bitter | 2016-02-16 19:34:31 UTC | Status | POST | MODIFIED |
| Fixed In Version | openstack-heat-2015.1.2-10.el7ost | |||
| Scott Lewis | 2016-02-19 13:38:26 UTC | CC | sclewis | |
| Target Milestone | z4 | async | ||
| errata-xmlrpc | 2016-02-23 14:44:04 UTC | Status | MODIFIED | ON_QA |
| Lon Hohberger | 2016-02-23 22:05:42 UTC | Status | ON_QA | MODIFIED |
| errata-xmlrpc | 2016-02-24 17:40:21 UTC | Status | MODIFIED | ON_QA |
| Amit Ugol | 2016-03-07 17:01:52 UTC | Status | ON_QA | VERIFIED |
| Andrew Dahms | 2016-03-09 23:24:24 UTC | CC | adahms | |
| Doc Text | Cause: If the database is not available while heat-engine is starting up, it will fail to start. Consequence: When updating a machine on which both the database and heat-engine are running using yum alone (as is the case when updating a TripleO undercloud), heat-engine may not be running after the update. Workaround (if any): If heat-engine is not running after the yum update (as shown by "systemctl status openstack-heat-engine.service), start heat-engine explicitly using the command "systemctl start openstack-heat-engine.service". Result: heat-engine will be running again. | If the database is not available when heat-engine starts, heat-engine fails to start, preventing heat-engine from running under certain circumstances. This occurs after you update a machine on which both the database and heat-engine are running using yum alone such as when updating the undercloud. As a workaround, heat-engine must be explicitly started by running 'systemctl start openstack-heat-engine.service'. You can confirm whether heat-engine is running by running 'systemctl status openstack-heat-engine.service'. | ||
| errata-xmlrpc | 2016-03-09 23:36:16 UTC | Status | VERIFIED | RELEASE_PENDING |
| Scott Lewis | 2016-03-10 14:49:37 UTC | Flags | needinfo?(zbitter) | |
| Zane Bitter | 2016-03-10 15:42:51 UTC | Flags | needinfo?(zbitter) | |
| errata-xmlrpc | 2016-03-10 17:07:10 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-02-15 09:34:43 UTC | 2016-03-10 12:07:10 UTC | ||
| Perry Myers | 2016-04-26 23:37:09 UTC | CC | pmyers |
Back to bug 1307125