Bug 2063515

Summary:	[RHV-M] [Direct LUN] Update enabled functionalities without restarting or powering off the VM.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	José Enrique <josgutie>
Component:	ovirt-engine	Assignee:	Mark Kemel <mkemel>
Status:	CLOSED DUPLICATE	QA Contact:	Evelina Shames <eshames>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.4.10	CC:	aefrat, ahadas, mavital, nashok
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-16 07:41:32 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 José Enrique 2022-03-13 11:10:24 UTC

Description of problem:


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


How reproducible:

Re-attatch a Direct Lun disk with updated parameters and they are not updated to the xml definition file until the vm is power on and power off.

Steps to Reproduce:
1. Create a new Direct LUN virtual disk
2. Don't check "Enable SCSI Pass-Through"
3. Select LUN and press OK.
4. Remove disk from VM
5. Create a new disk with the same Direct Lun
6. Check options "Enable SCSI Pass-Through", "Allow Privileged SCSI I/O" and "Using SCSI Reservation"
7. XML definition file updated with the "new" disk but not enabled "SCSI Reservation" functionality
8. Functionality enabled after "Power-Off"/"Power-On" of the VM.

Actual results:

To refresh the new functionality of a Direct LUN disk the VM xml definition file has to be powered off.

Expected results:

Reflect the enabled functionalities of a Direct LUN disk without restarting or powering off the VM.
Additional info:

Comment 1 nijin ashok 2022-03-15 06:35:25 UTC

Dup of bug 2028481?

Comment 2 Arik 2022-03-16 07:41:32 UTC

(In reply to nijin ashok from comment #1)
> Dup of bug 2028481?

Indeed, thanks

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