Bug 1332584

Summary:	RHEV Hypervisor configuration tool : can't add an NFS storage
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	ahauser <alexis.hauser>
Component:	ovirt-node-plugin-hosted-engine	Assignee:	Douglas Schilling Landgraf <dougsland>
Status:	CLOSED WORKSFORME	QA Contact:	wanghui <huiwa>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	unspecified	CC:	gklein, leiwang, rbarry, ycui
Target Milestone:	ovirt-3.6.7
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-05 19:13:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Node	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description ahauser 2016-05-03 14:19:16 UTC

Description of problem:


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

RHEV-Hypervisor 7.2-20160413.0.el7

How reproducible:

Every time

Steps to Reproduce:
1. Go in RHEV-H configuration menu
2. navigate to "remote storage" tab
3. try to enter a NFS FQDN or NFS complete path (FQDN:/export/path)

Actual results:

whatever you type, it isn't recognized as valid


Expected results:

It should be possible to use a NFS remote storage

Additional info:

Comment 1 wanghui 2016-05-04 09:34:22 UTC

In rhev-hypervisor, the nfs storage can not be added through "remote storage" at all. In "remote storage" tab, it can only accept the NFSv4 domain as the input.

Comment 2 ahauser 2016-05-04 15:24:45 UTC

Oh sorry, then I will close this bug.

What will this storage be used for ? It is not very explicit both in the menu and the documentation.

Will this storage be used by the hypervisor or the self-hosted engine ? Will it be used as data domain storage for the manager ?

Comment 3 Douglas Schilling Landgraf 2016-05-05 18:52:18 UTC

(In reply to ahauser from comment #2)
> Oh sorry, then I will close this bug.
> 
> What will this storage be used for ? It is not very explicit both in the
> menu and the documentation.
> 
> Will this storage be used by the hypervisor or the self-hosted engine ? Will
> it be used as data domain storage for the manager ?

It should be used as data domain in the manager.

Comment 4 Ryan Barry 2016-05-05 19:00:50 UTC

(In reply to ahauser from comment #2)
> Oh sorry, then I will close this bug.
> 
> What will this storage be used for ? It is not very explicit both in the
> menu and the documentation.
> 
> Will this storage be used by the hypervisor or the self-hosted engine ? Will
> it be used as data domain storage for the manager ?

The options in the hypervisor for setting the iSCSI initiator name and NFS domain are in case your storage uses authentication.

Storage needs to be added from RHEV-M, since RHEV-H doesn't keep track of storage management.

In the case of hosted engine, the hosted engine setup wizard will prompt you for a storage location.

The documentation here:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/Self-Hosted_Engine_Guide/Configuring_Self-Hosted_Engine_on_Red_Hat_Enterprise_Virtualization_Hypervisor.html

And here:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/Administration_Guide/chap-Storage.html

Should get you started.