Current Series Release Notes¶

23.0.0-37¶

The VAST Manila driver enhances multitenancy via share types using namespaced extra specs. Administrators can specify different VIP pools per share type using the vast:vippool_name extra spec, enabling network isolation between different tenants or projects. This allows multiple share types to use different VIP pools while sharing the same Manila backend. The configuration parameter vast_vippool_name in manila.conf now serves as a default fallback and is no longer strictly required when VIP pools are specified via share type extra specs.

Newly created Dell PowerScale NFS and CIFS shares and snapshots now deny all client access until an access rule is added. Existing shares and snapshots are not modified.

The VAST driver behavior has changed: new shares are now created with empty ACLs (deny all access) by default, instead of being reachable from any host until the first access rule is applied. Add access rules after creating a share to grant access, as with other Manila drivers.

Support for Python 3.10 has been removed. Now Python 3.11 is the minimum version supported.

Any user was able to manipulate the access rules, create backups or replicas, soft delete or restore public shares they did not own, and read or manipulate the export location metadata of shares they did not own. These operations now enforce ownership, and export location metadata is scoped to the share in the request URL. For details, see Launchpad bug #2161412 and Launchpad bug #2168962.

The Dell PowerScale driver now denies access by default for newly created NFS and CIFS shares and snapshots when no explicit access rules exist. Removing the final access rule also restores the deny-by-default behavior.

The VAST driver now creates new shares with empty ACLs (deny all access) by default. Access must be explicitly granted via Manila access rules, matching the behavior of other Manila drivers. Launchpad bug 2172349.

Hardened SSH command argument handling in share drivers to prevent untrusted access-rule values from being interpreted by remote shells. See bug #2163356 for more details.

The scheduler now correctly propagates goodness_function and filter_function configured in manila.conf to pool-level capabilities for drivers that do not declare these values in their pool data structures (e.g. CephFS). Previously, the goodness weigher would always fall back to a rating of 0 for such drivers, ignoring the configured function entirely. (Bug #2074114)

Fixed a bug where creating a replica of a share originally created from a snapshot incorrectly used reserved_snapshot_percentage instead of reserved_percentage when evaluating host capacity. Also, fixed the HostAffinityWeigher skewing replica placement toward the snapshot’s source host, which is irrelevant and harmful for HA placement. For details, check Bug #2167240

NetApp driver: Fixed share server migration through SVM Migrate, which placed a share server that uses a VLAN share network in the destination cluster’s Default IPspace instead of a custom IPspace named after its Neutron network. The migration compatibility check could fail, and a completed migration could leave the share server’s network interfaces unreachable. For more details, see Launchpad bug #2170655.

Adding a security service to a share network, updating it, and checking an update now only accept security services that belong to the same project. Previously, a project member who knew the ID of another project’s security service could associate it with their own share network and see its stored credentials. Such a security service is now treated as not found. See Launchpad bug 2171016 for more details.

Fixed the generic driver to restore client access when a share extension fails. Previously, a failure during the extension (for example, a Cinder volume extension error) left the share without its exports, disconnecting clients until an administrator intervened. See bug 2173501 for details.

Fixed database migration 805685098bd2 failing with error 1091 (“Can’t DROP FOREIGN KEY”) on MariaDB 12.1.1 and later, which no longer auto-names foreign keys <table>_ibfk_<n>. The migration now looks up the name of the share_servers.share_network_id foreign key instead of assuming share_servers_ibfk_1.

Fixed share snapshot database lookups ignoring their filter and sorting arguments. Asynchronous revert-to-snapshot completion now uses only the snapshot being restored to update the share size and quota, and preserves the states of other snapshots. Requests to include deferred-deletion snapshots and to sort a share’s snapshots are also honored.

Fixed VastData driver issue where changing share access rule level (e.g., from ‘rw’ to ‘ro’) would result in the IP address appearing in both ‘nfs_read_write’ and ‘nfs_read_only’ lists on the VAST cluster. The driver now replaces both lists with the access rules Manila wants on the share. Launchpad bug 2172349.

Share drivers that import manila.ssh_utils without using SSH, such as CephFS, LVM and ZFSonLinux, no longer fail to load when paramiko cannot be imported. A missing paramiko is now reported only when an SSH connection pool is created.