2024.1 Series Release Notes

18.2.1-1

Bug Fixes

  • Added db_retry on deadlock for various database update methods. Please check launchpad bug 2084529 for more details.

18.2.1

Bug Fixes

  • 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.

18.2.0

Bug Fixes

  • 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.

  • 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.

  • 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

  • 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

  • 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

  • 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.

  • 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.

18.0.1

New Features

  • Added a new field ‘disabled_reason’ to services table. Users can set ‘disabled_reason’ when disabling a service, and query the disabled reason while listing services. When re-enabling the service, the disabled reason will be cleared. See bug 2037700 for more details.

  • With deferred deletion, when resource(share or snapshot) is deleted, the quota is freed immediately and periodic tasks will delete the resource (i.e. share or snapshot) in driver. The resources errored during deletion are retried for deletion after some time in the same periodic tasks.

  • A human readable mount_point_name can now be specified while creating shares through the mount_point_name parameter. Manila will prepend a prefix to the mount point name which can be configured through the provisioning:mount_point_prefix share type extra spec. In case this extra spec is not available in the share type, Manila will prepend a project identification to the mount point name. Project id will be added to this friendly name provisioning:mount_point_prefix share type is not provided during provisioning. The LVM driver now supports human readable export locations.

  • Now the manila-wsgi WSGI application records all options and loaded values to its log file, when debug log is enabled.

  • The NetApp ONTAP driver now supports the common capability “mount_point_name_support”. It allows users to specify a custom “mount_point_name” when creating shares.

  • Add new config option ‘service_network_host’ for service instance with ‘dhss’=True. This helps us to define network host for ports and able to seperate from manila host.

  • The NetApp ONTAP driver now supports driver-advantaged share backup. NetApp SnapVault technology is used to create and restore backups for NetApp ONTAP shares. Backup delete workflow just deletes the transferred snapshots from destination backup volume. How to get the config data for backup, refer https://etherpad.opendev.org/p/manila-share-backup link.

Upgrade Notes

  • Shares created using the CEPHFS Native protocol will now have a new __mount_options metadata containing the cephfs_filesystem_name to enhance usability while mounting shares. Existing shares will be updated through the ensure shares workflow. To preserve backwards compatibility, this metadata is mutable by end users. It is strongly recommended that administrators include “__mount_options” in the [DEFAULT]/admin_only_metadata_keys configuration option.

  • The emc_share_backend option no longer supports vmax. Use powermax instead.

Deprecation Notes

  • Usage of the NFSProtocolHelper with the CephFS driver has been deprecated and it will be removed in the next skip-level release.

  • The Dell EMC VNX share driver has been deprecated because the product has reached its EOL. The driver will be removed in a future release.

  • The GlusterFS driver the GlusterFS Native driver have been deprecated. These drivers will be removed in a future release.

  • The Tegile share driver has been deprecated and will be removed in a future release.

  • The Windows SMB share driver has been deprecated and will be removed in a future release.

Bug Fixes

  • Fixed bug #1886690 that was a misleading user message when share services are down. The message is now clear and descriptive.

  • Bug #1900755: When failing to create shares using security services due to insufficient privileges or wrong credentials, the NetApp ONTAP driver will now report more accurate information on the failure.

  • NetApp driver: it is not reporting the home state of the aggregate pool. Operators may want to know this information to avoid those kind of pools during maintenance task. The patch adds the boolean capability netapp_is_home enabling the requester to avoid not home pools using the scheduler CapabilitiesFilter and share_type extra_specs. For more details, please refer to launchpad bug #1927823

  • Changed the error and status code that was raised when share types are not handled in shares api

  • Role based access control is enforced on the POST /shares/{share_id}/action API to reset status, task state, replica state and similar fields. This prevents the situation where deployments allow some users access to these APIs, but they don’t belong to projects where the resources exist. See bug 1955627 for more context.

  • Make snapshot names in CephFS drivers shorter to avoid limitation in Ceph clusters which truncates the subvolume name and makes the snapshots inaccesible.

  • NetApp driver bug #1982808: Fixed issue to add the retry logic to delete and release the snapmirror relationship. Delete the vserver pairing when there is no snapmirror relationship exist on source and destination cluster.

  • Metadata APIs have been fixed to respond with HTTP 404 / Not Found when the requester does not have access to a resource that the metadata pertains to.

  • NetApp driver: Fixed NetApp ipspace naming to follow the neutron network id, instead of the neutron subnet id as before. For more details please refer to launchpad bug #2007560 <https://bugs.launchpad.net/manila/+bug/2007560>.

  • The “replica_state” attribute of “active” replicas cannot be modified. Please see Launchpad bug 2015328 for more details.

  • Fix BadRequest error from share-server-migration-get-progress. For more details please refer to launchpad bug #2025075 <https://bugs.launchpad.net/manila/+bug/2025075>

  • Fixed cleanup of share network security service associations at network delete. See Launchpad bug 2029366 <https://bugs.launchpad.net/manila/+bug/2029366> for more details.

  • Pure Storage FlashBlade driver: Retry login for periodic task should network issue cause loss of connection. See launchpad bug 2032681 for more details.

  • The ‘count’ returned by shares and snapshots list API is fixed to provide correct value i.e. count of shares/snapshots instead of shareInstances/shareSnapshotInstances respectively. Please refer to the Launchpad bug #2033604 for more details.

  • The CephFS driver uses a RemoveExport DBUS API call to the NFS/Ganesha service when a user deletes an access rule, or when deleting the share. If this call fails, the driver now provides a log of the failure, and continues cleaning up. Prior to this change, share deletion could fail if the service failed the DBUS command to drop the export. This would leave the share with an “error_deleting” status, needing administrator intervention. See bug #2035572 for more information.

  • NetApp ONTAP driver during migration uses share server id which was causing failure for migrate a share server that had been migrated before. Fixed it by using share server identifier instead of id. Please refer to the Launchpad bug #2037109 for more details.

  • Now, default share network subnet is deleted when share network is deleted, in case it is the only subnet present in share network. Please refer to the Launchpad bug #2037422 for more details.

  • bug 2038607: Fixed parse of the protocol_access_mapping option and the backup_protocol_access_mapping option. This change requires that the values used for these options should be formatted like key0=[value00, value01],key1=[value10].

  • Manila will retry neutron API calls e.g. create_port(), show_port() in case of keystoneauth1 connection error. For more details, please refer to launchpad bug #2049507

  • bug 2051691: Fixed the default values of the following options.

    • [cors] allowed_headers

    • [cors] expose_headers

    • [cors] allow_methods

  • Fix share server manager API match of identifiers by preffix. “Invalid input received Error” now raises only if the identifiers suffixes matches. For more details, please refer to launchpad bug #1982429

  • On NetApp ONTAP backend, if share created from snapshot is deleted while clone split job is in progress, the deletion fails due to unmount error. Fixed this issue by stopping clone split if its in progress and then move to unmount of share. For more details, please check Launchpad Bug #1960239

  • Driver-advantaged share backups can now have a “backup_type”. It is also possible to create share backups in environments that support hard multi-tenancy (driver_handles_share_servers=True).