Bug 1133937

Summary: [TEXT] hosted-engine --deploy should provide better error message when iSCSI luns list is empty
Product: [Retired] oVirt Reporter: Jiri Moskovcak <jmoskovc>
Component: ovirt-hosted-engine-setupAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED CURRENTRELEASE QA Contact: meital avital <mavital>
Severity: low Docs Contact:
Priority: medium    
Version: 3.5CC: acathrow, amureini, bugs, dfediuck, ecohen, gklein, iheim, jmoskovc, sbonazzo, yeylon
Target Milestone: ---Keywords: CodeChange
Target Release: 3.5.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: ovirt-3.5.1_rc1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-21 16:06:35 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:
Bug Depends On:    
Bug Blocks: 1192937    
Attachments:
Description Flags
script to setup the iscsi target none

Description Jiri Moskovcak 2014-08-26 13:32:17 UTC
Created attachment 930983 [details]
script to setup the iscsi target

Description of problem:
When trying to setup HE on iscsi I get stuck on:

Please specify the lun id () [@DEFAULT@]

where I don't know what to enter.

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup-1.2.0-0.1.master.20140820130617.gitd832f86.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. hosted-engine --deploy
2. select iscsi as the storage backend
3.

Actual results:
Please specify the lun id () [@DEFAULT@]

Expected results:


Additional info:
see the attached script which I use to create the iscsi target

Comment 1 Sandro Bonazzola 2014-08-27 12:10:11 UTC
Can you please attach also vdsm logs and the output of 'vdsClient -s 0 getDeviceList' command?

Comment 2 Sandro Bonazzola 2014-08-27 12:44:16 UTC
Can't reproduce on F19:

          During customization use CTRL-D to abort.
          Please specify the storage you would like to use (iscsi, nfs3, nfs4)[nfs3]: iscsi
          Please specify the iSCSI portal IP address: 192.168.1.106
          Please specify the iSCSI portal port [3260]: 
          Please specify the iSCSI portal user: engine
          Please specify the iSCSI portal password: 
          Please specify the target name (iqn.2009-02.com.example:for.all) [iqn.2009-02.com.example:for.all]: 
[ INFO  ] Discovering iSCSI node
[ INFO  ] Connecting to the storage server
          The following luns have been found on the requested target:
          	 1 - sdb - 50000MB
          Please specify the lun id (1) [1]: 
[ INFO  ] Installing on first host
          Please provide storage domain name. [hosted_storage]: 

However, using your script, I had to call
"setenforce 0" since /pub didn't have right selinux rules in order to be used by tgtd.

Can you reproduce ensuring selinux is happy with the location you choose for tgtd?

Comment 3 Jiri Moskovcak 2014-08-27 14:01:16 UTC
(In reply to Sandro Bonazzola from comment #2)
> Can't reproduce on F19:
> 
>           During customization use CTRL-D to abort.
>           Please specify the storage you would like to use (iscsi, nfs3,
> nfs4)[nfs3]: iscsi
>           Please specify the iSCSI portal IP address: 192.168.1.106
>           Please specify the iSCSI portal port [3260]: 
>           Please specify the iSCSI portal user: engine
>           Please specify the iSCSI portal password: 
>           Please specify the target name (iqn.2009-02.com.example:for.all)
> [iqn.2009-02.com.example:for.all]: 
> [ INFO  ] Discovering iSCSI node
> [ INFO  ] Connecting to the storage server
>           The following luns have been found on the requested target:
>           	 1 - sdb - 50000MB
>           Please specify the lun id (1) [1]: 
> [ INFO  ] Installing on first host
>           Please provide storage domain name. [hosted_storage]: 
> 
> However, using your script, I had to call
> "setenforce 0" since /pub didn't have right selinux rules in order to be
> used by tgtd.
> 
> Can you reproduce ensuring selinux is happy with the location you choose for
> tgtd?

selinux is set to permissive on that machine(In reply to Sandro Bonazzola from comment #1)

> Can you please attach also vdsm logs and the output of 'vdsClient -s 0
> getDeviceList' command?

- no, I had to test something else and reinstalled the machine, but if you want I can give you access to it and you can try to reproduce it yourself

Comment 4 Sandro Bonazzola 2014-08-29 11:20:22 UTC
Can't reproduce on EL6 too. Please reopen and attach the setup and vdsm logs if you can reproduce.

Comment 5 Jiri Moskovcak 2014-09-10 10:57:41 UTC
This is caused by a selinux. I can reliably reproduce it on my machine and I believe it should be handled better in the setup - e.g. Die with some warning taht the LUN can't be listed and provide a hint to check the selinux.

Comment 6 Sandro Bonazzola 2014-09-12 07:07:26 UTC
Since this is not a bug on hosted-engine setup not able to use iSCSI but just an expected behaviour with error message to be improved I reduced the severity and updated the subject. Postponing to 3.5.1 too.

Comment 7 Sandro Bonazzola 2015-01-15 14:36:09 UTC
This is an automated message: 
This bug should be fixed in oVirt 3.5.1 RC1, moving to QA

Comment 8 Sandro Bonazzola 2015-01-21 16:06:35 UTC
oVirt 3.5.1 has been released. If problems still persist, please make note of it in this bug report.