2024.1 Series Release Notes

6.7.0

Upgrade Notes

  • Starting with this release, we removed checks for the LVM features having versions < 2.02.115. It includes the following:

    • LV activation support (2.02.91)

    • Thin provisioning (2.02.95)

    • –ignoreactivationskip (2.02.99)

    • lvcreate -l 100%FREE (2.02.115)

    Now the minimum supported LVM version is 2.02.115 which was released in 2015.

Deprecation Notes

  • Support for Windows operating systems has been deprecated, because of retirement of the Winstackers project.

Bug Fixes

  • PowerFlex driver bug #2004630: Fixed regression which caused the PowerFlex (ScaleIO) connector to login multiple times, even with an existing valid token. The ScaleIO connector now caches and reuses the token.

  • FC connector bug #2051237: Fix issue with fibre channel connector scanning partial targets. We search for target information in sysfs, first in fc_transport and then in fc_report_ports.

6.6.0

New Features

  • NVMe-oF connector: Improved speed of creation of the /etc/nvme/hostnqn file.

  • NVMe-oF connector: Always write the same value in the same system for the /etc/nvme/hostnqn file in older nvme-cli versions when system UUID can be read from DMI.

Bug Fixes

  • Dell PowerFlex driver Bug #2046810: Added new error code for PowerFlex 4.x which was causing this error. Added handling for the new error code returned from PowerFlex v4.x and allow the driver to ignore and skip a disconnect operation when the volume is not mapped.

  • NVMe-oF connector bug #2035695: Fixed attaching volumes when all portals of a subsystem are reconnecting at the time of the request.

  • NVMe-oF connector bug #2035811: Fixed attaching volumes on systems using newer NVMe kernel modules that present additional information in /sys/class/nvme/nvme#/address.

  • NVMe-oF connector bug #2035606: Fixed generation of hostnqn file on old nvme-cli versions.

  • NVMe-oF connector bug #1961222: Fixed support of newer NVMe CLI v2.

6.5.0

Bug Fixes

  • PowerFlex driver Bug #2013749: Added new error code for powerflex 4.x which was causing this error. Added handling for the new error code returned from Powerflex 4.x when a we try to map a volume which is already mapped.