Bug 1603591

Summary: [RFE] - Hosted-engine deployment on NFS should have option to specify exact NFS version v4.0.
Product: Red Hat Enterprise Virtualization Manager Reporter: Ameya Charekar <achareka>
Component: ovirt-hosted-engine-setupAssignee: Evgeny Slutsky <eslutsky>
Status: CLOSED ERRATA QA Contact: Nikolai Sednev <nsednev>
Severity: medium Docs Contact:
Priority: low    
Version: 4.2.4CC: achareka, eslutsky, lsurette, mtessun, stirabos, tnisan
Target Milestone: ovirt-4.4.0Keywords: FutureFeature
Target Release: 4.4.0Flags: lsvaty: testing_plan_complete-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.14.3, ovirt-ansible-hosted-engine-setup-1.1.1, ovirt-hosted-engine-setup-2.4.4 Doc Type: Enhancement
Doc Text:
With this enhancement, while using cockpit or engine-setup to deploy RHV Manager as a Self-Hosted Engine, the options for specifying the NFS version include two additional versions, 4.0 and 4.2.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-04 13:26:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1690026    
Bug Blocks:    

Description Ameya Charekar 2018-07-19 16:42:29 UTC
Description of problem:

Hosted-engine deployment does not have option to explicitly mention 4.0 version. The menu should also explain the meaning if settings like "v4".


Version-Release number of selected component (if applicable):
rhvm-4.2.4.5-0.1.el7_3.noarch

How reproducible:
Always.

Steps to Reproduce:
1. Deploy hosted-engine with NFS storage.
2.
3.

Actual results:
Available options are auto, v3, v4, v4_1.

Expected results:
Additionally option v4.0 should be available.


Additional info:
The menu should also explain the meaning if settings like "v4". If the meaning is negotiate the highest 4.x version, the menu should say so.

Comment 3 Yaniv Lavi 2018-07-23 07:29:10 UTC
Is the fix for BZ #1547506 good enough for this use case?
Why do you want to hard code the NFS version?

Comment 6 Sandro Bonazzola 2019-01-21 08:28:40 UTC
re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0.
If you think this bug should block 4.3.0 please re-target and set blocker flag.

Comment 8 Simone Tiraboschi 2019-02-14 09:54:35 UTC
AFAIK this is still not available on engine side: http://ovirt.github.io/ovirt-engine-api-model/4.3/#types/nfs_version

We can just choose between auto, v3, v4, v4_1, v4_2 but not v4_0.

Comment 9 Sandro Bonazzola 2019-03-12 13:52:36 UTC
(In reply to Simone Tiraboschi from comment #8)
> AFAIK this is still not available on engine side:
> http://ovirt.github.io/ovirt-engine-api-model/4.3/#types/nfs_version
> 
> We can just choose between auto, v3, v4, v4_1, v4_2 but not v4_0.

Please open a bz on engine and make it blocking this one.

Comment 10 Sandro Bonazzola 2019-03-25 09:19:38 UTC
Moving to 4.3.4 since engine side support for this is still missing

Comment 12 Sandro Bonazzola 2019-04-23 12:57:24 UTC
dropping from 4.3.4, pending storage team to target bug #1690026

Comment 13 Sandro Bonazzola 2019-05-03 09:23:26 UTC
Targeting to 4.3.5 being bug #1690026 now targeted to 4.3.5.

Comment 14 Sandro Bonazzola 2019-07-30 10:23:20 UTC
Moved out to 4.4 being low priority and an RFE

Comment 15 Sandro Bonazzola 2019-11-18 10:12:19 UTC
Bug #1690026 is on QA. We can proceed working on this on our side.

Comment 18 Nikolai Sednev 2020-04-01 14:47:29 UTC
Worked for me on fresh and clean environment, deployment of HE 4.4 was performed on NFS.

[ INFO  ] skipping: [localhost]
          Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: 
          Please specify the nfs version you would like to use (auto, v3, v4, v4_0, v4_1, v4_2)[auto]: 
          Please specify the full shared storage connection path to use (example: host:/path):

Tested on host with these components:
rhvm-appliance.x86_64 2:4.4-20200326.0.el8ev
ovirt-hosted-engine-setup-2.4.4-1.el8ev.noarch
ovirt-hosted-engine-ha-2.4.2-1.el8ev.noarch
Red Hat Enterprise Linux release 8.2 Beta (Ootpa)
Linux 4.18.0-193.el8.x86_64 #1 SMP Fri Mar 27 14:35:58 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Engine:
ovirt-engine-setup-base-4.4.0-0.26.master.el8ev.noarch
ovirt-engine-4.4.0-0.26.master.el8ev.noarch
openvswitch2.11-2.11.0-48.el8fdp.x86_64
Linux 4.18.0-192.el8.x86_64 #1 SMP Tue Mar 24 14:06:40 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux release 8.2 Beta (Ootpa)

Comment 27 errata-xmlrpc 2020-08-04 13:26:06 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 (RHV RHEL Host (ovirt-host) 4.4), 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-2020:3246