Current Series Release Notes

17.0.0-45

New Features

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

Bug Fixes

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

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

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

  • 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