Bug 1069432

Summary: VMware: iscsi target discovery fails while attaching volumes
Product: Red Hat OpenStack Reporter: Tracy Jones <tjones>
Component: openstack-novaAssignee: Matthew Booth <mbooth>
Status: CLOSED ERRATA QA Contact: Jaroslav Henner <jhenner>
Severity: high Docs Contact:
Priority: high    
Version: 4.0CC: breeler, jhenner, ndipanov, sgordon, xqueralt, yeylon
Target Milestone: z4Keywords: ZStream
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-nova-2013.2.3-2.el6ost Doc Type: Bug Fix
Doc Text:
Cause: The Nova vmware driver was not passing the iscsi server location to the instance. Consequence: It was not possible to add a cinder iscsi disk to a VMware instance. Fix: The nova vmware driver now correctly passes the iscsi server location to the instance. Result: It is possible to add a cinder iscsi disk to a VMware instance.
Story Points: ---
Clone Of:
: 1092008 (view as bug list) Environment:
Last Closed: 2014-05-29 20:35:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1055536, 1092008    
Attachments:
Description Flags
reproduce log
none
reproduce log none

Description Tracy Jones 2014-02-25 02:20:38 UTC
https://review.openstack.org/#/c/49692/

Comment 3 Jaroslav Henner 2014-04-22 15:25:41 UTC
Created attachment 888538 [details]
reproduce log

I tried to reproduce, log attached.

Comment 4 Jaroslav Henner 2014-04-22 15:31:27 UTC
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   |             |
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+

Comment 5 Jaroslav Henner 2014-04-28 13:26:48 UTC
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.

Comment 7 errata-xmlrpc 2014-05-29 20:35:16 UTC
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