+++ This bug was initially created as a clone of Bug #1715094 +++ +++ This bug was initially created as a clone of Bug #1650949 +++ It would be requested to have the option to modify the 'nfs_mount_options' in the [libvirt] section of the nova.conf during the overcloud deployment. ~~~ [libvirt] # Mount options passed to the NFS client. See section of the nfs man page # for details. # # Mount options controls the way the filesystem is mounted and how the # NFS client behaves when accessing files on this mount point. # # Possible values: # # * Any string representing mount options separated by commas. # * Example string: vers=3,lookupcache=pos # (string value) #nfs_mount_options=<None> ~~~ I could not find this parameter within THT or the openstack-puppet modules. Cheers, Marc Methot
Verified by adding the following parameters to overcloud_deploy: parameter_defaults: ComputeExtraConfig: nova::compute::libvirt::nfs_mount_options: "vers=3,lookupcache=pos" After deployment we can see the values in the nova.conf on compute nodes: [heat-admin@compute-0 ~]$ sudo docker exec nova_compute grep nfs_mount_options /etc/nova/nova.conf #nfs_mount_options=<None> nfs_mount_options=vers=3,lookupcache=pos
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/RHBA-2019:1672