Bug 1741152

Summary: [downstream clone - 4.3.6] [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: RHV bug bot <rhv-bugzilla-bot>
Component: ovirt-engineAssignee: Fedor Gavrilov <fgavrilo>
Status: CLOSED ERRATA QA Contact: Daniel <dmaaravi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aefrat, bugs, fgavrilo, Rhev-m-bugs, sbonazzo, tnisan
Target Milestone: ovirt-4.3.6Keywords: FutureFeature, ZStream
Target Release: 4.3.6Flags: aefrat: testing_plan_complete+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.6.3 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1690026 Environment:
Last Closed: 2019-10-10 15:36:58 UTC Type: ---
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: 1690026    
Bug Blocks:    

Description RHV bug bot 2019-08-14 11:30:25 UTC
+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1690026 +++
======================================================================

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:

(Originally by Simone Tiraboschi)

Comment 1 RHV bug bot 2019-08-14 11:30:27 UTC
Is this going to be fixed in 4.3.5?

(Originally by Sandro Bonazzola)

Comment 3 Avihai 2019-08-15 15:07:39 UTC
Please take under consideration that although this bug was opened on UI/webadmin.

This should be tested and verified for both UI and restAPI as fixes are in both UI and in RESTAPI.

Comment 5 Daniel 2019-09-02 04:42:10 UTC
I just verified this bug on ovirt-engine-4.3.6.2-0.1.el7.noarch
The fix is included in 4.3.6-2 according to https://gerrit.ovirt.org/#/c/101864/
The NFS storage was created in V4.0 as expected.

Comment 7 errata-xmlrpc 2019-10-10 15:36:58 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, 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/RHEA-2019:3010