Bug 1141500

Summary:	Can set dual NFS mount options when creating new NFS data domain
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Aharon Canan <acanan>
Component:	ovirt-engine	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Kevin Alon Goldblatt <kgoldbla>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.5.0	CC:	amureini, ecohen, gklein, iheim, lpeer, rbalakri, Rhev-m-bugs, scohen, tnisan, yeylon
Target Milestone:	---	Flags:	scohen: Triaged+
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	storage
Fixed In Version:	org.ovirt.engine-root-3.5.0-14	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Aharon Canan 2014-09-14 07:11:48 UTC

Description of problem:
We can set dual retrans/timeout values when creating new NFS SD, once using the specific fields and one using the "Additional mount options"

Version-Release number of selected component (if applicable):
3.5 vt2.2

How reproducible:
100%

Steps to Reproduce:
--------------------------
Create new NFS storage domain with below parameters 
NFS version = V4
Retransmissions = 6
Timeout = 10
Additional mount options = retrans=4
Create new NFS storage domain with below parameters 
NFS version = V4
Retransmissions = 6
Timeout = 10
Additional mount options = timeout=4

Actual results:
we do not get CDA for that 

Expected results:
should get CDA

Additional info:

Comment 1 Tal Nisan 2014-10-01 13:08:21 UTC

From what I know "timeout" is not a valid option so it should be blocked, "timeo" is blocked, though upon trying to reproduce I've discovered that the options are not validated case insensitively so "timeO" or "Retrans" will pass validation, this was fixed

Comment 2 Tal Nisan 2014-10-01 13:08:50 UTC

*I meant "timeout" should NOT be blocked

Comment 3 Eyal Edri 2014-10-07 07:12:32 UTC

this bug status was moved to MODIFIED before engine vt5 was built,
hence moving to on_qa, if this was mistake and the fix isn't in,
please contact rhev-integ

Comment 4 Kevin Alon Goldblatt 2014-10-13 10:54:24 UTC

I ran the scenario above and this time the operation was prevented by the GUI.
Tested with version:
rhevm-3.5.0-0.14.beta.el6ev.noarch
vdsm-4.16.6-1.el6ev.x86_64

Moving to Verify.

Comment 5 Allon Mureinik 2015-02-16 19:12:06 UTC

RHEV-M 3.5.0 has been released, closing this bug.

Comment 6 Allon Mureinik 2015-02-16 19:12:08 UTC

RHEV-M 3.5.0 has been released, closing this bug.