| 2014-06-16 18:34:15 |
wei du |
bug |
|
|
added bug |
| 2014-06-16 18:34:37 |
wei du |
nova: assignee |
|
wei du (weidu) |
|
| 2014-06-16 18:34:55 |
wei du |
nova: status |
New |
In Progress |
|
| 2014-06-25 19:29:23 |
wei du |
summary |
leave instances in POWEROFF state when nova compute restart with error |
leave instances in original state when nova compute restart with error |
|
| 2014-06-25 19:29:41 |
wei du |
description |
Currently, during nova-compute restart, when CONF.resume_guests_state_on_host_boot is set true, all existing will be put into ERROR state. In the patch, we just leave the instance in POWEROFF state. This way, we can directly run ‘nova reboot’ to get the instance back after errors got fixed. With an instance in ‘ERROR’ state, one has to manually change the DB record to other state before running ‘nova reboot’. |
Currently, during nova-compute restart, when CONF.resume_guests_state_on_host_boot is set true, all existing will be put into ERROR state. In the patch, we just leave the instance in original state. This way, we can directly run ‘nova reboot’ to get the instance back after errors got fixed. With an instance in ‘ERROR’ state, one has to manually change the DB record to other state before running ‘nova reboot’. |
|
| 2014-09-17 20:10:38 |
Sean Dague |
nova: status |
In Progress |
Confirmed |
|
| 2014-09-17 20:10:42 |
Sean Dague |
nova: importance |
Undecided |
High |
|
| 2014-09-17 20:10:44 |
Sean Dague |
nova: assignee |
wei du (weidu) |
|
|
| 2015-08-05 07:20:59 |
venkatesh |
nova: assignee |
|
venkatesh (p-venkatesh551) |
|
| 2015-09-16 09:18:43 |
Markus Zoeller (markus_z) |
tags |
|
compute reboot |
|
| 2016-03-04 02:27:01 |
Davanum Srinivas (DIMS) |
nova: assignee |
venkatesh (p-venkatesh551) |
|
|
| 2016-03-07 02:44:26 |
Jinquan Ni |
nova: assignee |
|
jinquanni（ZTE） (ni-jinquan) |
|
| 2016-03-08 03:55:42 |
OpenStack Infra |
nova: status |
Confirmed |
In Progress |
|
| 2016-04-12 07:47:47 |
Jinquan Ni |
nova: status |
In Progress |
Confirmed |
|
| 2016-04-18 21:45:13 |
Sarafraj Singh |
nova: status |
Confirmed |
In Progress |
|
| 2016-07-07 12:43:43 |
Alex Szarka |
nova: status |
In Progress |
Incomplete |
|
| 2016-07-11 09:05:39 |
OpenStack Infra |
nova: status |
Incomplete |
In Progress |
|
| 2016-07-11 09:07:35 |
Jinquan Ni |
nova: assignee |
Jinquan Ni (ni-jinquan) |
|
|
| 2016-07-11 09:07:51 |
Jinquan Ni |
nova: assignee |
|
Jinquan Ni (ni-jinquan) |
|
| 2016-12-09 20:40:10 |
Sean Dague |
nova: assignee |
Jinquan Ni (ni-jinquan) |
|
|
| 2016-12-09 20:40:14 |
Sean Dague |
nova: status |
In Progress |
Confirmed |
|
| 2017-01-09 06:25:56 |
Nazeema Begum |
nova: assignee |
|
Nazeema Begum (nazeema123) |
|
| 2017-01-09 07:08:02 |
Nazeema Begum |
nova: assignee |
Nazeema Begum (nazeema123) |
|
|
| 2017-01-09 08:24:03 |
Nazeema Begum |
nova: assignee |
|
Nazeema Begum (nazeema123) |
|
| 2017-01-09 09:05:42 |
Nazeema Begum |
nova: assignee |
Nazeema Begum (nazeema123) |
|
|
| 2017-05-17 03:05:58 |
Jay Pipes |
description |
Currently, during nova-compute restart, when CONF.resume_guests_state_on_host_boot is set true, all existing will be put into ERROR state. In the patch, we just leave the instance in original state. This way, we can directly run ‘nova reboot’ to get the instance back after errors got fixed. With an instance in ‘ERROR’ state, one has to manually change the DB record to other state before running ‘nova reboot’. |
Currently, during nova-compute restart, when CONF.resume_guests_state_on_host_boot is set true and there is a problem during a nova-compute restart (for example, a network card has issues), all existing will be put into ERROR state.
In the patch, we just leave the instance in original state. This way, we can directly run ‘nova reboot’ to get the instance back after errors got fixed. With an instance in ‘ERROR’ state, one has to manually change the DB record to other state before running ‘nova reboot’. |
|
| 2017-05-18 06:41:01 |
Jay Pipes |
nova: status |
Confirmed |
Invalid |
|
