Comment 2 for bug 1255977

I've also been experiencing this exact same problem with attaching volumes to virtual instances. When I try to attach a volume with the following command:
=============+
root@ts036953:/home/pssuser# nova volume-attach fedora1 08d565c2-e5ee-4ca1-8deb-27235396751f /dev/vdb
ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-008288f6-039c-4052-960f-521838515ac0)
=============+

And then when I try to attach to device that the instance already has I get the following message. Which kind of indicates that the instance is a least getting touched by the "nova volume-attach" command. What logs can I look into to see more detailed messages on what could be going wrong during this volume-attach attempt?

=============+
root@ts036953:/home/pssuser# nova volume-attach fedora1 08d565c2-e5ee-4ca1-8deb-27235396751f /dev/vda
ERROR: The supplied device path (/dev/vda) is in use. (HTTP 409) (Request-ID: req-83c8afe9-d515-4f7c-9ccd-8d9e37a0f2e5)
=============+