2024.2 Series Release Notes

19.0.1

Bug Fixes

  • When deferred deletion is enabled, Manila will attempt regular deletion. While quota is released, and these objects (shares, snapshots) are hidden from the user. Any error during deferred deletion will put resource in error_deferred_deleting state. After that, it will be handled in periodic task. Also, Manila will make sure snapshot instances are deleted before share instance delete. For more details, please check Launchpad bug 2068043

19.0.0

New Features

  • A new API to start the ensure shares procedure for Manila has been added. Through this API, OpenStack administrators will be able to recalculate the shares’ export location without restarting the shares manager service. Additionally, a new configuration option named update_shares_status_on_ensure is now available to help OpenStack administrators determine whether the shares’ status should be modified during the ensure shares procedure or not.

  • The possibility to specify the desired output format while issuing the manila-manage service list command was added. It is now possible to display the output also in yaml and json formats.

  • Added driver for VastData filesystem.

  • Added share export location metadata capabilities including create, update all, update single, show and delete metadata. Allows configuration of admin_only_el_metadata, such that keys in this list are able to be manipulated only by those with admin privileges. By default, this includes “preferred” key.

  • OpenStack operators can now make use of a new config option named driver_updatable_metadata to determine which share metadata updates the back end driver needs to be notified about. The config option contains list of share metadata keys. When the share’s metadata gets updated and Manila identifies that the new metadata keys match the metadata keys from the provided list, the share back end will be notified and it will apply the necessary changes. The result will be communicated through user messages.

  • It is now possible to specify pre-created NetApp efficiency policies through the use of the netapp:efficiency_policy share type extra spec. In the case of DHSS=True, the share server is not available upfront for efficiency policy creation. Users can retype to apply the policy, or if the share-network is constant (i.e., one share service is created for one share network), they can create an efficiency policy for the share server and apply it to DHSS=True shares.

  • Added support for share server migrations between different physical networks. It is achieved by creating an inactive port binding on the target host during share server migration, then cut it over to target host during migration-complete step.

  • NetApp Driver: The NetApp Driver now supports the creation of WORM shares using the SnapLock feature. To create these shares, set the ‘netapp_snaplock_type’ in the share type extra specs, along with the SnapLock related retention period extra specs.

Upgrade Notes

  • When restarting the service on an upgrade, when ensure shares is being run it will automatically transition the shares status to ensuring. In case you would like to prevent it, please change the value of the update_shares_status_on_ensure configuration option.

  • The service now requires a user’s “scope” to be defined with the OpenStack Identity service (Keystone) by the virtue of default Role Based Access Control (RBAC). This is being done in addition to changing the RBAC rules for GET requests to permit users possessing the “reader” role. The Default value of config options [oslo_policy] enforce_scope and [oslo_policy] oslo_policy.enforce_new_defaults has now changed to True. This means that, if you are using system scoped tokens to access Manila’s API, requests will fail with HTTP 403. Users must obtain a project scoped token to interact with the Manila API. You may also provide users with “reader” role where appropriate if they intend to make read-only API requests to Manila. If you would like to disable these changes, modify manila.conf file to set:

    [oslo_policy]
enforce_new_defaults=False
enforce_scope=False

    However, be aware that you may not be able to disable these options in the future. Please see OpenStack’s Consistent and Secure Default RBAC goal for more details

Bug Fixes

  • Launchpad bug 1867030 has been fixed for delete share.

  • Fixed an issue that allowed share network subnets to be deleted when they were still related to a share group. An exception will now be raised when Manila identify such existing relationship. For more details, please refer to Launchpad Bug 2004212.

  • Fixed share export location update when subnet is added to a network containing shares. Please refer to the Launchpad bug #2017501 for more details.

  • Launchpad bug 2023754 has been fixed for “next links” broken for limited share replicas api.

  • In case of NetApp ONTAP driver, when snpashots are soft deleted (i.e. they are renamed if delete fails) sometime we face issue in during rename. This is due to busy snapshots. To overcome this, Manila will stop clone split, perform rename and start clone split again. For more details, please refer to launchpad bug 2025641

  • NetApp driver: fixed FlexGroup share creation while modifying the dedup and compression configurations. For more details please refer to launchpad bug #2036931 <https://bugs.launchpad.net/manila/+bug/2036931>

  • The CephFS driver used to set the “preferred” export path incorrectly. It is now fixed to set it as part of export location metadata. See Launchpad bug 2053100 for more details.

  • Share manager drivers can now update export location metadata (such as the preferred attribute) during the ensure_shares routine. (Launchpad bug: 2053100)

  • NetApp driver bug #2058027: Fix the issue for NetApp driver for backup feature. Backup status update used to fail when administrator misconfigured backup settings configuration or SnapMirror relationship created during backup creation was not in healthy state.

  • NetApp driver bug #2058642: Fix the backup delete issue for NetApp driver when source and destination vserver are same. Added the logic in resource cleanup part to delete the vserver peering when source and destination vserver are not same.

  • NetApp driver bug #2059399: Fix the backup restore issue for NetApp driver for REST client. Backup restore is failing across the ONTAP cluster for REST client. Added the logic to use to destination vserver client for REST client to restore the backup and modify the restore lib for cmode REST client accordingly.

  • When reverting shares to snapshots that are larger or smaller than the share, some storage systems such as NetApp ONTAP always defer to the larger of the two sizes. Manila’s share manager interface now accounts for this behavior, and adjusts project quotas appropriately. For more details, please check Launchpad bug 2064502

  • PowerFlex Driver bug #2066840: The default port value of 443 has been added for the PowerFlex NAS backend.

  • Share server deletion happens asynchronously and failure during this delete results in leakage of neutron ports. This is fixed in two steps, first by trying to delete ports before share server deletion. Second, after ports from Manila db entries are deleted, query is made to neutron to get ports which are allocated for share server and missing in db. And then try to delete those ports. For more details please check Launchpad bug 2067266

  • Share and snapshot in deferred deletion states will be hidden from non-admin user in show API along-with existing list API. For more details, please check Launchpad bug 2067456

  • OSprofiler is now initialized after forking because at least its opentelemetry driver loses tracing context when process is forked.

  • NetApp driver bug #2069125: Fixed the issue for the NetApp ONTAP driver in the ZAPI workflow, where certain vserver accounts failed to add access rules for a share when the vserver network interface was not configured with kerberos.

  • NetApp ONTAP driver will now retry the sis operation (e.g. dedupe) if sis operation is currently active. This is needed because NetApp turns on efficiency (by default) on latest hardware which causes conflicting sis operation when Manila tries to turn it off. For more details, please check Launchpad bug #2071359

  • Manila now allows OpenStack administrators to schedule shares on hosts that are currently running and marked as under maintenance (disabled) through the only_host scheduler hint. For more details, please refer to launchpad bug 2072552

  • NetApp driver bug #2073766: Kerberos can only be configured for the SVM data network interface. Therefore, this fix excludes the vserver management network interface for certain SVM accounts when checking the SVM Kerberos configuration for network interfaces.

  • When using Neutron networks tagged as external (unmanaged provider networks) as share networks, Manila now creates ports with admin_state_up=False (disabled). This change addresses ARP failures that can occur when using OVN as the Neutron ML2 plugin. For more information, refer to bug 2074504.

  • When creating access rules with a deletion lock, the shares will also be locked to prevent disconnections. For more details, please refer to launchpad bug 2075967.

  • The NetApp ONTAP driver is now able to update the current snapshot_policy and/or both showmount configurations in a pre-created share. Please use the share metadata set feature to update these values.

  • The periodic database queries made by the share manager service to process deferred deletion of shares has been fixed to consider the host in addition to the share’s state. This both improves performance of the periodic task, as well as fixes incorrect behavior where incorrect shares are retrieved by the query.