Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1690026

Summary:	[RFE] - Creating an NFS storage domain the engine should let the user specify exact NFS version v4.0 and not just v4
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Simone Tiraboschi <stirabos>
Component:	ovirt-engine	Assignee:	Fedor Gavrilov <fgavrilo>
Status:	CLOSED ERRATA	QA Contact:	meital avital <mavital>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	bugs, eshenitz, fgavrilo, tnisan
Target Milestone:	ovirt-4.4.0	Keywords:	FutureFeature, ZStream
Target Release:	---	Flags:	dmaaravi: testing_plan_complete+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1741152 (view as bug list)		Environment:
Last Closed:	2020-08-04 13:16:55 UTC	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:
Bug Depends On:
Bug Blocks:	1603591, 1741152

Description Simone Tiraboschi 2019-03-18 15:41:11 UTC

Description of problem:
Creating an NFS storage domain the engine let the user choose:
auto, v3, v4, v4_1, v4_2.
http://ovirt.github.io/ovirt-engine-api-model/master/#types/nfs_version

v4 will try to negotiate highest possible 4.x version so we also need v4_0 to let the user force NFS 4.0.

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

How reproducible:
100%

Steps to Reproduce:
1. try to create an NFS v4.0 (not v4) storage domain
2.
3.

Actual results:
auto, v3, v4, v4_1, v4_2.

Expected results:
auto, v3, v4, v4_0, v4_1, v4_2.

Additional info:

Comment 1 Sandro Bonazzola 2019-06-21 13:58:45 UTC

Is this going to be fixed in 4.3.5?

Comment 6 RHV bug bot 2019-12-13 13:15:13 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 7 RHV bug bot 2019-12-20 17:44:55 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 8 Daniel 2020-01-01 10:04:38 UTC

Verified via web-admin on version 4.4.0-0.13.master.el7.

Comment 9 RHV bug bot 2020-01-08 14:49:10 UTC

WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 10 RHV bug bot 2020-01-08 15:16:20 UTC

WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 11 RHV bug bot 2020-01-24 19:51:00 UTC

WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 16 errata-xmlrpc 2020-08-04 13:16:55 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:3247