Fix the APIError typo
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
vivek.ys |
Bug Description
I use Nova rev1113 with VMware hypervisor.
I try to use pause/unpause command with OpenStack API, but VMware hypervisor doesn't support it, so it sends an APIError exception :
2011-05-26 12:03:49,137 INFO nova.compute.
2011-05-26 12:03:49,138 INFO nova.compute.
2011-05-26 12:03:49,202 INFO nova.compute.
2011-05-26 12:03:49,202 INFO nova.compute.
2011-05-26 12:03:49,202 INFO nova.compute.
2011-05-26 12:03:49,261 AUDIT nova.compute.
2011-05-26 12:03:49,809 ERROR nova.exception [-] Uncaught exception
(nova.exception): TRACE: Traceback (most recent call last):
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: return f(*args, **kw)
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: function(self, context, instance_id, *args, **kwargs)
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: lambda result: self._update_
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: self._vmops.
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: raise exception.
(nova.exception): TRACE: AttributeError: 'module' object has no attribute 'APIError'
(nova.exception): TRACE:
2011-05-26 12:03:49,810 ERROR nova [-] Exception during message handling
(nova): TRACE: Traceback (most recent call last):
(nova): TRACE: File "/usr/lib/
(nova): TRACE: rval = node_func(
(nova): TRACE: File "/usr/lib/
(nova): TRACE: raise Error(str(e))
(nova): TRACE: Error: 'module' object has no attribute 'APIError'
(nova): TRACE:
The instance still running (ping or ssh OK) but the instance status is pausing/BUILD for Nova:
$ nova list
+----+-
| ID | Name | Status | Public IP | Private IP |
+----+-
| 29 | Server 29 | BUILD | | 172.16.1.4 |
+----+-
$ euca-describe-
RESERVATION r-srnudn54 simple default
INSTANCE i-0000001d ami-00000001 172.16.1.4 172.16.1.4 pausing key (simple, p-novavmware) 0 m1.small 2011-05-
In the same tenant, if an instance is running and if we try to resume it, nova-compute raise a InstanceResumeF
2011-05-26 12:17:17,837 INFO nova.compute.
2011-05-26 12:17:17,838 INFO nova.compute.
2011-05-26 12:17:17,901 INFO nova.compute.
2011-05-26 12:17:17,901 INFO nova.compute.
2011-05-26 12:17:17,902 INFO nova.compute.
2011-05-26 12:17:17,962 AUDIT nova.compute.
2011-05-26 12:17:18,361 ERROR nova.exception [-] Uncaught exception
(nova.exception): TRACE: Traceback (most recent call last):
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: return f(*args, **kw)
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: function(self, context, instance_id, *args, **kwargs)
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: lambda result: self._update_
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: self._vmops.
(nova.exception): TRACE: File "/usr/lib/
(nova.exception): TRACE: raise exception.
(nova.exception): TRACE: InstanceResumeF
(nova.exception): TRACE:
2011-05-26 12:17:18,362 ERROR nova [-] Exception during message handling
(nova): TRACE: Traceback (most recent call last):
(nova): TRACE: File "/usr/lib/
(nova): TRACE: rval = node_func(
(nova): TRACE: File "/usr/lib/
(nova): TRACE: raise Error(str(e))
(nova): TRACE: Error: Failed to resume server: instance is not in a suspended state.
The instance still running (ping or ssh OK) but it is in state resuming/BUILD for Nova.
Related branches
- Alex Meade (community): Approve
- Devin Carlen (community): Approve
- Brian Waldon (community): Approve
-
Diff: 38 lines (+4/-3)2 files modifiedAuthors (+1/-0)
nova/virt/vmwareapi/vmops.py (+3/-3)
Changed in nova: | |
assignee: | nobody → vivek.ys (vivekys) |
Changed in nova: | |
status: | Triaged → In Progress |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → diablo-1 |
Changed in nova: | |
milestone: | diablo-1 → 2011.3 |
status: | Fix Committed → Fix Released |
The first exception referring to the APIError is actually just a typo. It should be "ApiError". Even when that is fixed, it appears we still dont support 'pause' on that hypervisor.
As for the second issue, an instance must have the status 'suspended' to be able to resume it.