Rebooting not allowed for instances stuck in rebooting_hard state
Bug #982108 reported by
Peng Yong
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Rafi Khardalian |
Bug Description
i have a rebooting an instance in one compute. and it's failed.
the task_state is always rebooting_hard, and i can't recover it any more.
i can't reboot it on dashboard or nova-client:
# nova reboot tt
ERROR: Cannot 'reboot' while instance is in task_state rebooting (HTTP 409)
finally, i update the database, and it works again:
mysql> update instances set task_state=NULL where uuid='2aef3845-
Changed in nova: | |
importance: | Undecided → Low |
status: | New → Triaged |
summary: |
- rebooting server failed when it's in rebooting_hard state + Rebooting not allowed for instances stuck in rebooting_hard state |
Changed in nova: | |
importance: | Low → High |
Changed in nova: | |
assignee: | nobody → Rafi Khardalian (rkhardalian) |
status: | Triaged → In Progress |
Changed in nova: | |
milestone: | none → grizzly-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-3 → 2013.1 |
To post a comment you must log in.
i checked commit 26227b79e9246a8 7eeb83766cfcc8e 96d294d28b, it remove many scheduler_api.
git log -p 26227b79
- @exception. novaclient_ converter api.redirect_ handler reboot( self, req, id, body):
valid_ reboot_ types = ['HARD', 'SOFT']
- @scheduler_
def _action_
if 'reboot' in body and 'type' in body['reboot']:
and i can't find any schedule api in openstack any more.