| 2014-03-26 20:59:20 |
Chris Friesen |
bug |
|
|
added bug |
| 2014-03-27 16:32:33 |
Tracy Jones |
tags |
|
compute |
|
| 2014-04-03 21:48:40 |
melanie witt |
nova: importance |
Undecided |
Medium |
|
| 2014-04-03 21:48:40 |
melanie witt |
nova: status |
New |
Confirmed |
|
| 2014-04-03 21:49:00 |
melanie witt |
tags |
compute |
api compute |
|
| 2014-04-07 18:12:14 |
Chris Friesen |
nova: assignee |
|
Chris Friesen (cbf123) |
|
| 2014-06-18 14:31:24 |
OpenStack Infra |
nova: status |
Confirmed |
In Progress |
|
| 2014-06-25 03:48:37 |
OpenStack Infra |
nova: status |
In Progress |
Fix Committed |
|
| 2014-07-23 14:56:36 |
Russell Bryant |
nova: status |
Fix Committed |
Fix Released |
|
| 2014-07-23 14:56:36 |
Russell Bryant |
nova: milestone |
|
juno-2 |
|
| 2014-10-16 08:38:34 |
Thierry Carrez |
nova: milestone |
juno-2 |
2014.2 |
|
| 2016-09-13 07:15:13 |
Liang Chen |
description |
We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once.
We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node.
This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). |
[Impact]
* Instances in error state cannot be evacuated.
[Test Case]
* nova evacuate <error_state_instance> <another_compute_host>
* nova refuses to evacuate the instance because of its state
[Regression Potential]
* None
We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once.
We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node.
This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). |
|
| 2016-09-13 07:16:01 |
Liang Chen |
tags |
api compute |
api compute sts |
|
| 2016-09-13 07:26:33 |
Liang Chen |
attachment added |
|
debdiff for trusty https://bugs.launchpad.net/nova/+bug/1298061/+attachment/4739730/+files/trusty_fix.patch |
|
| 2016-09-13 07:29:47 |
Louis Bouchard |
bug task added |
|
nova (Ubuntu) |
|
| 2016-09-13 07:30:01 |
Louis Bouchard |
nominated for series |
|
Ubuntu Trusty |
|
| 2016-09-13 07:30:01 |
Louis Bouchard |
bug task added |
|
nova (Ubuntu Trusty) |
|
| 2016-09-13 07:32:31 |
Liang Chen |
nova (Ubuntu Trusty): assignee |
|
Liang Chen (cbjchen) |
|
| 2016-09-13 07:32:37 |
Liang Chen |
nova (Ubuntu Trusty): status |
New |
In Progress |
|
| 2016-09-13 07:38:49 |
James Page |
nova (Ubuntu): status |
New |
Fix Released |
|
| 2016-09-13 07:38:55 |
James Page |
nova (Ubuntu Trusty): importance |
Undecided |
Medium |
|
| 2016-09-13 07:39:00 |
James Page |
nova (Ubuntu): importance |
Undecided |
Medium |
|
| 2016-09-13 13:46:48 |
Liang Chen |
description |
[Impact]
* Instances in error state cannot be evacuated.
[Test Case]
* nova evacuate <error_state_instance> <another_compute_host>
* nova refuses to evacuate the instance because of its state
[Regression Potential]
* None
We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once.
We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node.
This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). |
[Impact]
* Instances in error state cannot be evacuated.
[Test Case]
* nova evacuate <error_state_instance> <another_compute_host>
* nova refuses to evacuate the instance because of its state
[Regression Potential]
* None
* Passed tempest smoke tests locally.
We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once.
We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node.
This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). |
|
| 2016-09-14 07:50:11 |
Liang Chen |
description |
[Impact]
* Instances in error state cannot be evacuated.
[Test Case]
* nova evacuate <error_state_instance> <another_compute_host>
* nova refuses to evacuate the instance because of its state
[Regression Potential]
* None
* Passed tempest smoke tests locally.
We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once.
We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node.
This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). |
[Impact]
* Instances in error state cannot be evacuated.
[Test Case]
* nova evacuate <error_state_instance> <another_compute_host>
* nova refuses to evacuate the instance because of its state
[Regression Potential]
* None
* Passed tempest smoke tests locally.
Note: one simple way to put an instance into error state is to directly change its database record, for example update instances set vm_state='error' where uuid='XXXXXXXX'
We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once.
We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node.
This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). |
|
| 2016-09-14 07:50:31 |
Liang Chen |
description |
[Impact]
* Instances in error state cannot be evacuated.
[Test Case]
* nova evacuate <error_state_instance> <another_compute_host>
* nova refuses to evacuate the instance because of its state
[Regression Potential]
* None
* Passed tempest smoke tests locally.
Note: one simple way to put an instance into error state is to directly change its database record, for example update instances set vm_state='error' where uuid='XXXXXXXX'
We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once.
We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node.
This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). |
[Impact]
* Instances in error state cannot be evacuated.
[Test Case]
* nova evacuate <error_state_instance> <another_compute_host>
* nova refuses to evacuate the instance because of its state
[Regression Potential]
* None
* Passed tempest smoke tests locally.
Note: one simple way to put an instance into error state is to directly change its database record, for example "update instances set vm_state='error' where uuid='XXXXXXXX'"
We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once.
We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node.
This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). |
|
| 2016-09-14 07:50:49 |
Liang Chen |
description |
[Impact]
* Instances in error state cannot be evacuated.
[Test Case]
* nova evacuate <error_state_instance> <another_compute_host>
* nova refuses to evacuate the instance because of its state
[Regression Potential]
* None
* Passed tempest smoke tests locally.
Note: one simple way to put an instance into error state is to directly change its database record, for example "update instances set vm_state='error' where uuid='XXXXXXXX'"
We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once.
We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node.
This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). |
[Impact]
* Instances in error state cannot be evacuated.
[Test Case]
* nova evacuate <error_state_instance> <another_compute_host>
* nova refuses to evacuate the instance because of its state
[Regression Potential]
* None
* Passed tempest smoke tests locally.
Note: one simple way to put an instance into error state is to directly change its database record, for example "update instances set vm_state='error' where uuid='XXXXXXXX'"
We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once.
We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node.
This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). |
|
| 2016-09-29 02:55:06 |
Yoshi Kadokawa |
bug |
|
|
added subscriber Yoshi Kadokawa |
| 2016-11-17 16:11:45 |
Seyeong Kim |
tags |
api compute sts |
api compute sts sts-sru |
|
| 2016-11-17 16:11:56 |
Seyeong Kim |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2016-11-17 16:12:11 |
Seyeong Kim |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-11-17 16:56:39 |
Seyeong Kim |
bug |
|
|
added subscriber Seyeong Kim |
| 2017-01-18 21:31:25 |
Corey Bryant |
bug task added |
|
cloud-archive |
|
| 2017-01-18 21:32:10 |
Corey Bryant |
bug task deleted |
cloud-archive |
|
|
| 2017-01-18 21:33:52 |
Corey Bryant |
bug task added |
|
cloud-archive |
|
| 2017-01-18 21:34:04 |
Corey Bryant |
nominated for series |
|
cloud-archive/icehouse |
|
| 2017-01-18 21:34:04 |
Corey Bryant |
bug task added |
|
cloud-archive/icehouse |
|
| 2017-01-18 21:34:15 |
Corey Bryant |
cloud-archive: status |
New |
Invalid |
|
| 2017-01-18 21:34:19 |
Corey Bryant |
cloud-archive: status |
Invalid |
Fix Released |
|
| 2017-01-18 21:34:26 |
Corey Bryant |
cloud-archive/icehouse: status |
New |
In Progress |
|
| 2017-01-18 21:34:33 |
Corey Bryant |
cloud-archive/icehouse: importance |
Undecided |
Medium |
|
| 2017-01-18 21:34:36 |
Corey Bryant |
cloud-archive: importance |
Undecided |
Medium |
|
| 2017-01-18 21:57:30 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-server-dev/nova/icehouse |
|
| 2017-01-25 13:42:53 |
Robie Basak |
nova (Ubuntu Trusty): status |
In Progress |
Incomplete |
|
| 2017-01-26 07:59:35 |
Seyeong Kim |
description |
[Impact]
* Instances in error state cannot be evacuated.
[Test Case]
* nova evacuate <error_state_instance> <another_compute_host>
* nova refuses to evacuate the instance because of its state
[Regression Potential]
* None
* Passed tempest smoke tests locally.
Note: one simple way to put an instance into error state is to directly change its database record, for example "update instances set vm_state='error' where uuid='XXXXXXXX'"
We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once.
We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node.
This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). |
[Impact]
* Instances in error state cannot be evacuated.
[Test Case]
* nova evacuate <error_state_instance> <another_compute_host>
* nova refuses to evacuate the instance because of its state
[Regression Potential]
* Cherry picked from upstream
- removed unnecessary argument passing
- add allowing ERROR state before evacuating.
* actually, in code, added one parameter, and removed unused one.
so very low regression possibility.
* Tested on juju+maas test env.
* Passed tempest smoke tests locally.
Note: one simple way to put an instance into error state is to directly change its database record, for example "update instances set vm_state='error' where uuid='XXXXXXXX'"
We currently allow reboot/rebuild/rescue for an instance in the Error state if the instance has successfully booted at least once.
We should allow "evacuate" as well, since it is essentially a "rebuild" on a different compute node.
This would be useful in a number of cases, in particular if an initial evacuation attempt fails (putting the instance into the Error state). |
|
| 2017-01-26 08:04:53 |
Seyeong Kim |
nova (Ubuntu Trusty): status |
Incomplete |
In Progress |
|
| 2017-01-26 08:04:58 |
Seyeong Kim |
nova (Ubuntu Trusty): assignee |
Liang Chen (cbjchen) |
Seyeong Kim (xtrusia) |
|
| 2017-01-26 19:27:25 |
Brian Murray |
nova (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2017-01-26 19:27:32 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2017-01-26 19:27:37 |
Brian Murray |
tags |
api compute sts sts-sru |
api compute sts sts-sru verification-needed |
|
| 2017-01-26 19:28:02 |
Brian Murray |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2017-01-27 00:25:18 |
Seyeong Kim |
tags |
api compute sts sts-sru verification-needed |
api compute sts sts-sru verification-done |
|
| 2017-02-02 22:04:36 |
Launchpad Janitor |
nova (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2017-02-02 22:04:47 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-03-22 15:44:19 |
Louis Bouchard |
tags |
api compute sts sts-sru verification-done |
api compute sts sts-sru-done verification-done |
|
| 2019-06-04 18:44:22 |
Dan Streetman |
tags |
api compute sts sts-sru-done verification-done |
api compute sts-sru-done verification-done |
|
