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
Director manages the nfs mount. Example config in environments/storage/nova-nfs.yaml
ah, missing some relevant info in the description... this is boot from volume with NFS backed cinder volumes.
Note that's there's a facility for cinder to pass mount options to nova via 'options' in connection_info. We'd have to ask the cinder folks how that's used in practise.
This appears to have landed on master.
Verified (undercloud) [stack@undercloud-0 ~]$ cat virt/extra_templates.yaml parameter_defaults: ComputeExtraConfig: nova::compute::libvirt::nfs_mount_options: "vers=3,lookupcache=pos" [heat-admin@compute-0 ~]$ sudo crudini --get /var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.conf libvirt nfs_mount_options vers=3,lookupcache=pos [heat-admin@compute-1 ~]$ sudo crudini --get /var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.conf libvirt 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:1738
*** Bug 2025843 has been marked as a duplicate of this bug. ***