Bug 1273828

Summary:	[hosted-engine-setup] [iSCSI support] The LUN where the HE iSCSI domain resides on should be removed from engine DB during upgrade from 3.5 to 3.6
Product:	[oVirt] ovirt-hosted-engine-setup	Reporter:	Elad <ebenahar>
Component:	Plugins.Block	Assignee:	Simone Tiraboschi <stirabos>
Status:	CLOSED DUPLICATE	QA Contact:	Ilanit Stein <istein>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	1.3.0	CC:	bugs, didi, lveyde, rmartins, sbonazzo, stirabos
Target Milestone:	---	Flags:	ebenahar: planning_ack? ebenahar: devel_ack? ebenahar: testing_ack?
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-21 11:27:18 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:

Description Elad 2015-10-21 10:52:50 UTC

Description of problem:
For now, once 3.5 hosted-engine is deployed over iSCSI, the LUN where the HE domain resides on, gets written in the engine DB as a direct LUN. 
This LUN should get cleaned from the DB during upgrade to 3.6 since in 3.6, the HE domain gets imported to the setup and it's not importable in case its LUN is in the DB.

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

How reproducible:
ovirt-hosted-engine-setup-1.3.0-1.el7ev.noarch

Steps to Reproduce:
1. Deploy 3.5 HE over iSCSI 
2. Upgrade the setup to 3.6


Actual results:
The LUN of the HE domain is not removed from the DB

Expected results:
The LUN should get removed during the upgrade

Comment 1 Simone Tiraboschi 2015-10-21 11:27:18 UTC


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