Expected exception on volume attach leaves traceback in the logs.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Vish Ishaya | ||
Folsom |
Fix Released
|
Medium
|
Vish Ishaya |
Bug Description
Repro steps:
Attempt to attach volume to an in use device
$ nova volume-attach bar c3e6b09b-
ERROR: The supplied device path (/dev/vda) is in use. (HTTP 400) (Request-ID: req-d2cfbc33-
Exceptions are correct but we get a large traceback in the logs:
2013-03-14 13:25:24.996 DEBUG nova.api.
Traceback (most recent call last):
File "/opt/stack/
rval = self.proxy.
File "/opt/stack/
return getattr(proxyobj, method)(ctxt, **kwargs)
File "/opt/stack/
temp_level, payload)
File "/usr/lib/
self.gen.next()
File "/opt/stack/
return f(self, context, *args, **kw)
File "/opt/stack/
pass
File "/usr/lib/
self.gen.next()
File "/opt/stack/
return function(self, context, *args, **kwargs)
File "/opt/stack/
e, sys.exc_info())
File "/usr/lib/
self.gen.next()
File "/opt/stack/
return function(self, context, *args, **kwargs)
File "/opt/stack/
return do_reserve()
File "/opt/stack/
retval = f(*args, **kwargs)
File "/opt/stack/
context, instance, bdms, device)
File "/opt/stack/
raise exception.
DevicePathInUse: The supplied device path (/dev/vda) is in use.
These exceptions are expected so there is no need for traceback.
Changed in nova: | |
importance: | Undecided → Medium |
milestone: | none → grizzly-rc1 |
assignee: | nobody → Vish Ishaya (vishvananda) |
status: | New → Triaged |
description: | updated |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-rc1 → 2013.1 |
Fix proposed to branch: master /review. openstack. org/24475
Review: https:/