Bug 1350226

Summary:	Attach disk as VirtIO-ISCSI / SPAPR-VSCSI to a running VM fails
Product:	[oVirt] ovirt-engine	Reporter:	Tal Nisan <tnisan>
Component:	BLL.Storage	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Carlos Mestre González <cmestreg>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.0.0	CC:	acanan, amureini, bugs, ratamir
Target Milestone:	ovirt-4.0.1	Flags:	rule-engine: ovirt-4.0.z+ tnisan: testing_plan_complete? rule-engine: planning_ack+ tnisan: devel_ack+ acanan: testing_ack+
Target Release:	4.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 06:26:46 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 Tal Nisan 2016-06-26 15:05:41 UTC

Description of problem:
When trying to attach a disk with VirtIO-ISCSI / SPAPR-VSCSI interface to a running VM (i.e. hot attach) the operation fails

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Create a floating disk and a VM with one bootable disk
2. Run the VM and wait till it reaches UP status
3. Try to attach the floating disk to the VM with VirtIO-ISCSI interface

Actual results:
The attach will fail

Expected results:
The attach should succeed

Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2016-06-26 15:06:40 UTC

Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 Carlos Mestre González 2016-07-11 09:54:09 UTC

rhevm-4.0.2-0.2.rc1.el7ev.noarch

Comment 3 Sandro Bonazzola 2016-07-19 06:26:46 UTC

Since the problem described in this bug report should be
resolved in oVirt 4.0.1 released on July 19th 2016, it has been closed with a
resolution of CURRENT RELEASE.

For information on the release, and how to update to this release, follow the link below.

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

http://www.ovirt.org/release/4.0.1/