Rocky Series Release Notes¶
This release corrects a problem with the fix for Bug #1823200 in the previous release. If you are running OpenStack on Python 3, you should not be impacted by this bug. If you are not using Dell EMC VxFlex OS (ScaleIO) Storage as a backend for Cinder, you do not need to upgrade to this release.
Dell EMC VxFlex OS driver: This release corrects an issue where the fix for Bug #1823200 did not run correctly when using Python 2.7. If you are interested in this release because of OSSN-0086, be aware that you must also deploy a configuration file on compute nodes, cinder nodes, and anywhere you would perform a volume attachment in your deployment. Please see the release notes for the previous release for details.
Bug #1823200: Prior fixes for this bug changed the connection properties but did not take into account an upgrade scenario in which currently attached volumes had the old format connection properties and could fail on detatch with “KeyError: ‘config_group’”. This release updates the ‘scaleio’ connector to handle this situation. It is only applicable to deployments using a Dell EMC PowerFlex/VxFlex OS/ScaleIO backend.
Bug #1883654: The fix for Bug #1823200 in the previous release used a Python 3-specific language feature and thus did not run correctly when used with Python 2.7. The problem has been corrected in this release.
Fix an issue where SCSI LUN scans for FC were unnecessarily too broad. Now OS-Brick will not use wildcards unless it doesn’t find any target ports in sysfs and the Cinder driver doesn’t disable them.
Always check if we are dealing with a single WWNN Fibre Channel target, even when we receive an initiator_target_map. This allows us to exclude unconnected HBAs from our scan for storage arrays that automatically connect all target ports (due to their architecture and design) even if the Cinder driver returns the initiator_target_map, provided the target has a single WWNN. Excluding these HBAs prevents undesired volumes from being connected.
Under certain conditions detaching a multipath device may result in failure when flushing one of the individual paths, but the disconnect should have succeeded, because there were other paths available to flush all the data.
The multipath disconnect mechanism is now more robust and will only fail when disconnecting if multipath would lose data.
Added ability to extend attached ScaleIO volumes