<!-- Verify first that your issue/request is not already reported on GitHub. Also test if the latest release and master branch are affected too. Always add information AFTER of these HTML comments, but no need to delete the comments. -->
##### ISSUE TYPE <!-- Pick one below and delete the rest --> * Improvement Request ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ SecondaryStorage VM ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ 4.11.1 ~~~ ##### CONFIGURATION <!-- Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise --> N/A ##### OS / ENVIRONMENT <!-- Information about the environment if relevant, N/A otherwise --> N/A ##### SUMMARY <!-- Explain the problem/feature briefly --> Debian 9 system VM default NFS version is 4.2. If your NFS server does not support 4.2, the mount may fail (is does in our case). There is a global config `secstorage.nfs.version` to specify the version, but it does only support int values. If you set it to `4` the NFS4 version used is `4.0`. There is currently no way to set a minor version. e.g. `4.1`. :warning: Note that version 3 has no "minor versions". Probably worth considering is to add new configuration field for nfs4 minor versions. e.g. `secstorage.nfs4.minorversion` defaulted to null. NFS4 version shoulld be a combination of `secstorage.nfs.version + '.' + secstorage.nfs4.minorversion`. NFS3 only `secstorage.nfs.version` [ Full content available at: https://github.com/apache/cloudstack/issues/2861 ] This message was relayed via gitbox.apache.org for [email protected]
