Poor VMware driver exception handling in compute manager
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Another opened bug (https:/
The VMware driver raise exception when we try to pause an instance.
After pause request, the instance state passed to 'pausing' but it stays in this state indefinitely. It didn't come back to the 'running' state.
While with libvirt driver, if we try to pause an instance, the driver raise an APIError exception (it's not implemented). The instance passed to 'pausing' but few second after it came back to 'running' state and log files says:
2011-05-26 15:43:24,014 INFO nova.compute.
2011-05-26 15:43:24,047 INFO nova.compute.
Related branches
- Todd Willey (community): Needs Fixing
- Nova Core security contacts: Pending requested
- Sateesh: Pending requested
-
Diff: 128 lines (+58/-7)3 files modifiednova/tests/test_vmwareapi.py (+3/-3)
nova/virt/vmwareapi/fake.py (+3/-0)
nova/virt/vmwareapi/vmops.py (+52/-4)
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in nova: | |
assignee: | nobody → vivek.ys (vivekys) |
status: | Confirmed → In Progress |
Once the bug /bugs.launchpad .net/bugs/ 790174 gets resolved then adding pause and resume functionality in vmops.py of vmwareapi will resolve this issue. Am I right?
https:/