Description of problem: Manila has support for bringing shares under manila management and taking shares out of manila management: https://docs.openstack.org/manila/latest/admin/shared-file-systems-manage-and-unmanage-share.html https://docs.openstack.org/api-ref/shared-file-system/#manage-share-since-api-v2-7 https://docs.openstack.org/api-ref/shared-file-system/#unmanage-share-since-api-v2-7 This has been supported for a long time in Manila. Support for this feature with DHSS=False https://docs.openstack.org/manila/latest/admin/share_back_ends_feature_support_mapping.html#mapping-of-share-drivers-and-share-features-support Support for DHSS=True manage/unmanage was added with API version 2.49: https://docs.openstack.org/manila/latest/contributor/api_microversion_history.html#maximum-in-stein
Feature is already available in upstream Wallaby, moving to POST
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 (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), 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-2023:4577