Bug 1133937 - [TEXT] hosted-engine --deploy should provide better error message when iSCSI luns list is empty
Summary: [TEXT] hosted-engine --deploy should provide better error message when iSCSI ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-hosted-engine-setup
Version: 3.5
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 3.5.1
Assignee: Jiri Moskovcak
QA Contact: meital avital
URL:
Whiteboard: integration
Depends On:
Blocks: 1192937
TreeView+ depends on / blocked
 
Reported: 2014-08-26 13:32 UTC by Jiri Moskovcak
Modified: 2015-02-16 09:35 UTC (History)
10 users (show)

Fixed In Version: ovirt-3.5.1_rc1
Clone Of:
Environment:
Last Closed: 2015-01-21 16:06:35 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
script to setup the iscsi target (665 bytes, application/x-shellscript)
2014-08-26 13:32 UTC, Jiri Moskovcak
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 32859 0 master MERGED provide better error message when iSCSI luns list is empty Never
oVirt gerrit 33761 0 None NEW provide better error message when iSCSI luns list is empty Never
oVirt gerrit 35138 0 master MERGED iscsi: detecting empty LUN list Never
oVirt gerrit 35141 0 ovirt-hosted-engine-setup-1.2 MERGED iscsi: detecting empty LUN list Never

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.


Note You need to log in before you can comment on or make changes to this bug.