Description of problem: hosted-engine deployment fails on NFS due to: [ INFO ] TASK [Add nfs storage domain] [ ERROR ] ValueError: 4 is not a valid NfsVersion [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "4 is not a valid NfsVersion"} Version-Release number of selected component (if applicable): cockpit-ovirt-dashboard.noarch 0.11.17-1.el7.centos How reproducible: 100% Steps to Reproduce: 1. deploy hosted-engine from cockpit 2. choose NFS and set NFSv4 in storage/advanced options section 3. Actual results: [ INFO ] TASK [Add nfs storage domain] [ ERROR ] ValueError: 4 is not a valid NfsVersion [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "4 is not a valid NfsVersion"} Expected results: Successful deployment Additional info: It correctly works on CLI
(In reply to Simone Tiraboschi from comment #0) > [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "4 is not > a valid NfsVersion"} According to http://docs.ansible.com/ansible/latest/ovirt_storage_domains_module.html valid values for version are: auto, v3, v4 or v4_1
Do we feel it's going to make it into 4.2.2? If not, please defer.
This is not a 4.2.2 blocker, "auto" works perfectly fine (and is the default). But I posted a simple patch to fix this if we have another build to put it to.
QE can reproduce this issue. Test version: cockpit-dashboard-160-3.el7.x86_64 cockpit-system-160-3.el7.noarch cockpit-ovirt-dashboard-0.11.17-1.el7ev.noarch cockpit-bridge-160-3.el7.x86_64 cockpit-ws-160-3.el7.x86_64 cockpit-storaged-160-3.el7.noarch cockpit-160-3.el7.x86_64 ovirt-hosted-engine-ha-2.2.7-1.el7ev.noarch ovirt-hosted-engine-setup-2.2.13-1.el7ev.noarch vdsm-http-4.20.22-1.el7ev.noarch vdsm-hook-ethtool-options-4.20.22-1.el7ev.noarch vdsm-network-4.20.22-1.el7ev.x86_64 vdsm-api-4.20.22-1.el7ev.noarch vdsm-python-4.20.22-1.el7ev.noarch vdsm-hook-vmfex-dev-4.20.22-1.el7ev.noarch vdsm-hook-vhostmd-4.20.22-1.el7ev.noarch vdsm-yajsonrpc-4.20.22-1.el7ev.noarch vdsm-client-4.20.22-1.el7ev.noarch vdsm-4.20.22-1.el7ev.x86_64 vdsm-gluster-4.20.22-1.el7ev.noarch vdsm-hook-vfio-mdev-4.20.22-1.el7ev.noarch vdsm-common-4.20.22-1.el7ev.noarch vdsm-hook-openstacknet-4.20.22-1.el7ev.noarch vdsm-jsonrpc-4.20.22-1.el7ev.noarch vdsm-hook-fcoe-4.20.22-1.el7ev.noarch rhvm-appliance-4.2-20180202.0.el7.noarch rhvh-4.2.1.4-0.20180305.0+1 Test result: From the cockpit: [ INFO ] TASK [Fetch datacenter_name] [ INFO ] TASK [Add nfs storage domain] [ ERROR ] ValueError: 4 is not a valid NfsVersion [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "4 is not a valid NfsVersion"}
(In reply to Yaniv Kaul from comment #2) > Do we feel it's going to make it into 4.2.2? If not, please defer. should make it.
Tested with these versions: rhvh-4.2.2.0-0.20180322.0+1 cockpit-ovirt-dashboard-0.11.19-1.el7ev.noarch ovirt-hosted-engine-setup-2.2.14-1.el7ev.noarch ovirt-hosted-engine-ha-2.2.7-1.el7ev.noarch rhvm-appliance-4.2-20180322.0.el7.noarch Tested result: While selecting the NFS v4 storage , [Add nfs storage domain] task works well. From the cockpit: """ [ INFO ] TASK [Fetch Datacenter name] [ INFO ] ok: [localhost] [ INFO ] TASK [Add NFS storage domain] [ INFO ] changed: [localhost] [ INFO ] TASK [Add glusterfs storage domain] """ So, change this bug's status to verified.
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.