Bug 1741152 - [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
Summary: [downstream clone - 4.3.6] [RFE] - Creating an NFS storage domain the engine ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.3.6
: 4.3.6
Assignee: Fedor Gavrilov
QA Contact: Daniel
URL:
Whiteboard:
Depends On: 1690026
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-14 11:30 UTC by RHV bug bot
Modified: 2021-09-09 15:35 UTC (History)
6 users (show)

Fixed In Version: ovirt-engine-4.3.6.3
Doc Type: Enhancement
Doc Text:
Clone Of: 1690026
Environment:
Last Closed: 2019-10-10 15:36:58 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:
aefrat: testing_plan_complete+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-43600 0 None None None 2021-09-09 15:35:53 UTC
Red Hat Product Errata RHEA-2019:3010 0 None None None 2019-10-10 15:37:11 UTC
oVirt gerrit 101415 0 'None' MERGED It should be possible to specify exact v4.0 as NFS version 2020-01-26 14:57:44 UTC
oVirt gerrit 101419 0 'None' MERGED core: It should be possible to specify exact v4.0 as NFS version 2020-01-26 14:57:44 UTC
oVirt gerrit 101451 0 'None' MERGED It should be possible to specify exact v4.0 as NFS version 2020-01-26 14:57:44 UTC
oVirt gerrit 101535 0 'None' MERGED Update to model 4.4.4 2020-01-26 14:57:44 UTC
oVirt gerrit 101863 0 'None' ABANDONED restapi: Update to model 4.3.27 2020-01-26 14:57:44 UTC
oVirt gerrit 101864 0 'None' MERGED restapi: Update to model 4.3.27 2020-01-26 14:57:44 UTC
oVirt gerrit 102225 0 'None' MERGED core: It should be possible to specify exact v4.0 as NFS version 2020-01-26 14:57:44 UTC

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
Note You need to log in before you can comment on or make changes to this bug.