Bug 1208485

Summary: [TEXT ONLY] - Hosted Engine - Instructions for handling Invalid Storage Domain error
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-hosted-engine-setupAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED WORKSFORME QA Contact: Elad <ebenahar>
Severity: low Docs Contact:
Priority: medium    
Version: 3.5.1CC: aburden, acanan, amureini, ebenahar, ecohen, gklein, istein, lsurette, sbonazzo, sherold, stirabos, ylavi
Target Milestone: ---Keywords: EasyFix, StringChange, ZStream
Target Release: 3.5.3Flags: ylavi: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: Doc Type: Bug Fix
Doc Text:
The error message has been updated to be more specific and helpful when deployment of the Self-Hosted Engine on iSCSI fails due to a dirty LUN.
 Story Points: ---
Clone Of: 1201196 Environment:
Last Closed: 2015-05-27 05:15:23 UTC Type: ---
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: 1201196    
Bug Blocks: 1218280    
Attachments:
Description Flags
/var/log/ 20.5.15
none
logs none

Comment 3 Elad 2015-05-20 10:07:04 UTC 
Simone,

I'm getting the following error message while deploying HE over a dirty LUN:

[ ERROR ] Failed to execute stage 'Misc configuration': Wrong Master domain or its version: 'SD=9a519263-688c-47a0-b543-f38d23a92404, pool=2bfc7e4c-e62b-4bc0-a883-100439c183db'

I guess it is not the desired behaviour, but maybe my test wasn't according to what you meant. 

Steps:
1) Had an iSCSI storage domain on a RHEV setup
2) Deactivated the domain
3) Initiated hosted-engine --deploy on a separate host, using the same LUN used by the other setup for storage domain


I checked it using rhev 3.5.3 vt15

vdsm-4.16.16-1.el7ev.x86_64
ovirt-hosted-engine-setup-1.2.4-1.el7ev.noarch
Comment 4 Simone Tiraboschi 2015-05-20 10:39:53 UTC 
No, it's not but probably it's failing earlier for a similar issue.
Could you please attach the logs?
Comment 5 Elad 2015-05-20 17:17:33 UTC 
Created attachment 1027819 [details]
/var/log/ 20.5.15

Attached /var/log/ from the host
Comment 6 Simone Tiraboschi 2015-05-26 12:55:25 UTC 
This one is different scenario cause is failing on a different point. I created a new bug for it.
https://bugzilla.redhat.com/1225011

Can you please try to verify this one with this sequence?
1. Try to deploy hosted-engine over iSCSI on a clean LUN.
2. Forcefully interrupt the setup as soon as you see '[ INFO ] Creating Storage Domain'
3. Try to deploy again on the same LUN without passing the answerfile
Comment 7 Elad 2015-05-26 15:25:24 UTC 
Created attachment 1030001 [details]
logs

(In reply to Simone Tiraboschi from comment #6)
> This one is different scenario cause is failing on a different point. I
> created a new bug for it.
> https://bugzilla.redhat.com/1225011
> 
> Can you please try to verify this one with this sequence?
> 1. Try to deploy hosted-engine over iSCSI on a clean LUN.
> 2. Forcefully interrupt the setup as soon as you see '[ INFO ] Creating
> Storage Domain'
> 3. Try to deploy again on the same LUN without passing the answerfile

Followed you instructions. An attempt to deploy on the same LUN went fine:

1) Interrupted the setup: 

 [ INFO  ] Creating Storage Domain
^C[ ERROR ] Failed to execute stage 'Misc configuration': SIG2


2) Tried to deploy again on the same LUN without passing the answerfile:

The specified storage location already contains a data domain. Is this an additional host setup (Yes, No)[Yes]? no


Storage domain seems to be functional. Image creation succeeds.
Deployment succeeded (aborted it after the image creation finished). therefore, I'm unable to reproduce.

Attaching the logs
Comment 8 Simone Tiraboschi 2015-05-26 16:36:43 UTC 
On my opinion we can close it as VERIFIED or as CLOSED/WORKSFORME cause I have no other clear way to reproduce it.
Comment 9 Aharon Canan 2015-05-27 05:15:23 UTC 
Based on comment #8 and as this issue severity is low - closing as WORKSFORME