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:
Is this going to be fixed in 4.3.5?
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
Verified via web-admin on version 4.4.0-0.13.master.el7.
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
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