Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1084206

Summary:	[ovirt 3.4] Cannot use ISCSI storage using Fedora 19 and oVirt 3.4
Product:	[Retired] oVirt	Reporter:	Douglas Schilling Landgraf <dougsland>
Component:	vdsm	Assignee:	Nir Soffer <nsoffer>
Status:	CLOSED DUPLICATE	QA Contact:	Gil Klein <gklein>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.4	CC:	acathrow, bazulay, danken, dougsland, gklein, iheim, mgoldboi, yeylon
Target Milestone:	---
Target Release:	3.4.1
Hardware:	Unspecified
OS:	Linux
Whiteboard:	storage
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-04-09 14:32:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Douglas Schilling Landgraf 2014-04-03 20:55:29 UTC

Description of problem:

Trying to attach ISCSI data Storage to oVirt Engine I got:

"VDSM was: Failed to setup iSCSI subsystem"

# cat /etc/redhat-release
Fedora release 19 (Schrödinger’s Cat)

# rpm -qa | grep -i selinux
libselinux-2.1.13-15.fc19.x86_64
libselinux-utils-2.1.13-15.fc19.x86_64
libselinux-python-2.1.13-15.fc19.x86_64
selinux-policy-targeted-3.12.1-74.19.fc19.noarch
selinux-policy-3.12.1-74.19.fc19.noarch

rpm -qa | grep -i multipath
# device-mapper-multipath-0.4.9-51.fc19.x86_64

Version-Release number of selected component (if applicable):
- vdsm-4.14.6-0.fc19
- Cluster in 3.3
- Kernel 3.13.7-100.fc19.x86_64
- oVirt Engine 3.4.0-1.fc19


Steps to Reproduce:
- Step oVirt Engine
- Register an oVirt Node and Approve
- Try to attach a iSCSI storage (it will fail)

Additional tests:
- Added use_lvmetad = 0 to  /etc/lvm/lvm.conf and rebooted the machine. The error still appear.

Comment 1 Nir Soffer 2014-04-07 12:20:58 UTC

(In reply to Douglas Schilling Landgraf from comment #0)

I could reproduce this issue when the host iscsi initiator name was wrong. Setting the right value and restarting iscsid service, I could discover the the luns, login to the storage server, create a storage domain, vms, etc. I had some random errors during this process, that were "fixed" by retrying the operation. Can you check that if this is the case in your machine?

Please attach also vdsm log and /var/log/messages.

Comment 2 Nir Soffer 2014-04-07 13:59:20 UTC

I reproduced this with vdsm-4.13.3 - the laster from ovirt-3.3 repositories.

This seems to be a duplicate of bug 1076603. Can you verify this and close this bug?

Comment 3 Douglas Schilling Landgraf 2014-04-09 14:32:06 UTC

I could attach ISCSI storage again downgrading the iscsi-initiator-utils to:
iscsi-initiator-utils-6.2.0.873-6.fc19.x86_64

Available at: http://koji.fedoraproject.org/koji/buildinfo?buildID=422568

Thanks Nir!

*** This bug has been marked as a duplicate of bug 1076603 ***