Incorrect Status Transition on instance reboot
Bug #795228 reported by
William Wolf
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Medium
|
Titan | ||
Bug Description
When I reboot a server using v1.1/servers/
Related branches
lp:~rackspace-titan/nova/instance_states
- Vish Ishaya (community): Approve
- Brian Waldon (community): Approve
-
Diff: 2339 lines (+849/-460)20 files modifiednova/api/ec2/cloud.py (+38/-12)
nova/api/openstack/common.py (+54/-28)
nova/api/openstack/servers.py (+9/-13)
nova/api/openstack/views/servers.py (+4/-9)
nova/compute/api.py (+90/-28)
nova/compute/manager.py (+250/-225)
nova/compute/task_states.py (+59/-0)
nova/compute/vm_states.py (+39/-0)
nova/db/sqlalchemy/api.py (+4/-16)
nova/db/sqlalchemy/migrate_repo/versions/044_update_instance_states.py (+138/-0)
nova/db/sqlalchemy/models.py (+3/-13)
nova/exception.py (+1/-1)
nova/scheduler/driver.py (+4/-6)
nova/tests/api/openstack/test_server_actions.py (+22/-33)
nova/tests/api/openstack/test_servers.py (+67/-38)
nova/tests/integrated/test_servers.py (+23/-11)
nova/tests/scheduler/test_scheduler.py (+9/-4)
nova/tests/test_cloud.py (+10/-5)
nova/tests/test_compute.py (+21/-17)
nova/tests/vmwareapi/db_fakes.py (+4/-1)
| Changed in nova: | |
| assignee: | nobody → William Wolf (throughnothing) |
| Changed in nova: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
Revision history for this message
| Thierry Carrez (ttx) wrote | #1 |
| Changed in nova: | |
| assignee: | William Wolf (throughnothing) → nobody |
| assignee: | nobody → Titan (rackspace-titan) |
Revision history for this message
| Brian Waldon (bcwaldon) wrote | #2 |
| Changed in nova: | |
| status: | Confirmed → In Progress |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → diablo-rbp |
| Changed in nova: | |
| milestone: | diablo-rbp → 2011.3 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
@William: are you actually working on this, or should we unassign you to potentially let someone else have a shot at it ?