Yoga Series Release Notes

5.2.4-1

Bug Fixes

  • Bug #1888675: Fixed in-use volume resize issues caused by the multipath-tools version.

5.2.4

New Features

  • Support separate privsep logging levels. Now services using os-brick can have different log levels for the service and os-brick’s privsep calls. The service usually uses the default “oslo_privsep.daemon” name while os-brick now uses “os_brick.privileged”.

Bug Fixes

  • Bug #1922052: Fixed missing os-brick DEBUG logs on nova compute service.

5.2.3

New Features

  • FC connector: Added support to force and ignore_errors parameters on disconnect_volume method.

5.2.2

Bug Fixes

  • RBD connector bug #1981455: Fixed AttributeError error on disconnect for RBD encrypted volumes not using host attachments.

5.2.1

Bug Fixes

  • NVMe-oF connector bug #1964379: Fixed using non LUKS v1 encrypted volumes, as once one of such volumes is disconnected from a host all successive NVMe-oF attachments would fail.

  • Bug #1967790: Fixed encryptor’s connect_volume returns and the symlink is pointing to the raw block device instead of to the decrypted device mapper device.

5.2.0

Prelude

Welcome to the Yoga release of the os-brick library.

New Features

  • Lightbits LightOS connector: new os-brick connector for Lightbits(TM) LightOS(R). Lightbits Labs (https://www.lightbitslabs.com) LightOS is software-defined, cloud native, high-performance, clustered scale-out and redundant NVMe/TCP storage that performs like local NVMe flash. This connector requires the Lightbits discovery-client, available from Lightbits Labs.

Known Issues

  • At release time, we became aware that recent changes to the nvmeof connector were tested only in configurations where the NVMe storage backend supports namespace AER. One issue arising from this is being tracked by Bug #1961102.

Bug Fixes

  • Bug #1929223: Fixed HTTPS certificate validation was disabled in PowerFlex connector.

  • Bug #1938870: Fixed KumoScale Driver replicated volume missing portals attaches without raid.

  • NVMe-oF connector bug #1943615: Fixed get nvme device failing on kernels with multipath enabled by using the generic form /sys/class/block/<ctrl>n* for finding nvme devices.

  • The nvmeof connector relies on nvme-cli to query the host-nqn. Versions of nvme-cli < 1.10 do not have the ‘show-hostnqn’ command, which could cause the connector to fail to generate the hostnqn. Fixed the connector to either get or generate the hostnqn with versions of nvme-cli<1.10 that do not have ‘show-hostnqn’.