Created attachment 888538 [details]
reproduce log

I tried to reproduce, log attached.

Created attachment 888550 [details]
reproduce log

Ups, wrong reproduce. There is a correct one.

[root@jhenner-node-old-permanent-1 ~(keystone_admin)]# lvs
  LV                                          VG             Attr       LSize Pool Origin Data%  Move Log Cpy%Sync Convert
  volume-d68dae61-60d8-44a4-b79e-8d53aa3fc964 cinder-volumes -wi-ao---- 1,00g  

[root@jhenner-node-old-permanent-1 ~(keystone_admin)]# nova volume-attach foo d68dae61-60d8-44a4-b79e-8d53aa3fc964 /dev/vdb
+----------+--------------------------------------+
| Property | Value                                |
+----------+--------------------------------------+
| device   | /dev/sdb                             |
| serverId | d799a8c8-e3fe-4cac-907f-0c2dabcf5c77 |
| id       | d68dae61-60d8-44a4-b79e-8d53aa3fc964 |
| volumeId | d68dae61-60d8-44a4-b79e-8d53aa3fc964 |
+----------+--------------------------------------+

[root@jhenner-node-old-permanent-1 ~(keystone_admin)]# cinder list
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+
|                  ID                  |   Status  | Display Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+
| d68dae61-60d8-44a4-b79e-8d53aa3fc964 | available |     None     |  1   |     None    |  false   |             |
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+

I was able to add a volume that was backed-up as LVM on the controller, but I had to:

1) Enable the access to iSCSI tgtd:
iptables -I INPUT -s 0.0.0.0/0 -p tcp -m multiport --dports 3260,8776 -m comment --comment "001 cinder incoming cinder_1.2.3.4" -j ACCEPT
because Packstack cretes rule like:

iptables -A INPUT -s 1.2.3.4/32 ... -j ACCEPT

2) Add the iSCSI Adapter, as described in
https://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.vsphere.solutions.doc/GUID-3154EDE9-8C1E-4427-8BAE-98B010CB6BF2.html

I am going to open packstack bug for the 1). I think we should include the 2) in the VMWare deployment knowledge base article.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2014-0578.html