Description of problem: With OpenStack Manila, a user can create a shared file system and have it exported in one of many supported NAS protocols (NFS, CIFS, CEPHFS, MAPRFS, GlusterFS, HDFS, etc.). The choice they really have is among the protocols supported by the backend/s deployed by the cloud deployer/administrator. Deployers have a choice to even limit the protocols made available to end users. In Triple-O, the available protocols is inferred with the backend made available, and Triple-O deployers cannot influence this decision. Version-Release number of selected component (if applicable): 16.x How reproducible: Always Steps to Verify: 1. Deploy a Triple-O environment with the Shared File Systems service (manila) enabled with one or more chosen backends (e.g.: NetApp and CephFS-via-NFS) 2. When the ability exists, override available protocols and set it to NFS 3. Check the deployment with "manila pool-list --detail" to verify supported protocols 4. Check "DEFAULT/enabled_share_protocols" in manila.conf to see enabled protocols.
Tested using: puppet-tripleo-11.5.0-2.20210121034919.6eb6f5b.el8ost.1.noarch
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 (Red Hat OpenStack Platform (RHOSP) 16.2 enhancement 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/RHEA-2021:3483