Comment 4 for bug 1096983

It gets uglier if you try it again. The next bdm gets the wrong device name:

cory@cfsyn25:~/devstack$ nova volume-attach 68932196-8bf2-4d7d-ba01-eb4a8a3b20cc 2e911a75-08a1-4ca8-a1c5-10fd8d30c99d auto & nova volume-attach f4f6b668-6936-49fe-9ff1-6d0751dfe681 2e911a75-08a1-4ca8-a1c5-10fd8d30c99d auto &
[1] 28200
[2] 28201
cory@cfsyn25:~/devstack$ +----------+--------------------------------------+
| Property | Value |
+----------+--------------------------------------+
| device | /dev/vdc |
| id | 2e911a75-08a1-4ca8-a1c5-10fd8d30c99d |
| serverId | 68932196-8bf2-4d7d-ba01-eb4a8a3b20cc |
| volumeId | 2e911a75-08a1-4ca8-a1c5-10fd8d30c99d |
+----------+--------------------------------------+
+----------+--------------------------------------+
| Property | Value |
+----------+--------------------------------------+
| device | /dev/vdb |
| id | 2e911a75-08a1-4ca8-a1c5-10fd8d30c99d |
| serverId | f4f6b668-6936-49fe-9ff1-6d0751dfe681 |
| volumeId | 2e911a75-08a1-4ca8-a1c5-10fd8d30c99d |
+----------+--------------------------------------+

^^^ /dev/vdb is already in use by the first double attach, so this one doesn't actually get attached by compute.