RHBA-2019:0929 - Bug Fix Advisory

Topic

Updated OpenStack Block Storage packages that resolve various issues are
now available for Red Hat OpenStack Platform 13.0 (Queens) for RHEL 7.

Description

Red Hat OpenStack Platform provides the facilities for building, deploying
and monitoring a private or public infrastructure-as-a-service (IaaS) cloud
running on commonly available physical hardware. This advisory includes
packages for:

• OpenStack Block Storage service

OpenStack Block Storage (cinder) manages block storage mounting and the
presentation of such mounted block storage to instances. The back-end
physical storage can consist of local disks, Fiber Channel, iSCSI, and/or
NFS mounts attached to Compute nodes. In addition, Block Storage supports
volume backups, and snapshots for temporary save and restore operations.
Programmatic management is available through the Block Storage service's
API.

Changes to the openstack-cinder component:

• Previously, when `destroy_empty_storage_group` was enabled and a storage group was destroyed after it was emptied, the VNX driver or storops cache was not updated and the driver did not recreate the storage group upon subsequent attachment. The storage group cache was not updated, causing the subsequent attachment of volumes to the same host to fail.

With this update, the storage group is updated with poll after deleting it. The storage group is not deleted from cache explicitly, but the status is set to `not-exist`. As a result, subsequent attaching creates the storage group if the latest status is `not-exist`. (BZ#1693338)

• Previously, when authenticating, a string match was performed on the `response-type` string. Performance with this mechanism was not consistent.

With this update, authentication to the array uses the `response-type-numeric` value to determine success, rather than doing a string match against the `response-type` string. (BZ#1676603)

• The following issues with multi-attach have been fixed:

Previously, the call to create attachments returned `HTTP ACCEPTED`. This response should be a 200 because the call is blocking and returns a response body.

With this update, the call to create attachments returns `SUCCESS`.

Previously, when managing a multi-attach volume under volume type with multi-attach extra spec set to `True`, the multi-attach flag was not set correctly in the volume properties and the multi-attach flag was set to `False` after a manage operation.

With this update, when managing a volume, the API sets the multi-attach flag to `True` in the volume properties and the multi-attach attribute is handled correctly when managing existing volumes.

Previously, when retyping a multi-attach volume, the multi-attach flag was not set correctly in the volume properties and the retype flag was set to `False` after a manage operation.

With this update, the return value of `get_by_name_or_id` in the `volume_types` module returns a dictionary. During the function call to `_is_multiattach`, the `getattr()` returns `{}(default value) because a dictionary is passed instead of an object. After importing the `cinder.objects.volume_type` module, the current function call to `get_by_name_or_id()` returns an object, and `getattr()` returns the appropriate `extra_specs` instead of the default value `({})`.

Previously, when migrating attached volumes, all attached volumes resolved to `rw` after a migration.

With this update, migration sets the correct attach mode after migration and migrating a read-only volume correctly resolves to read-only `ro`.

Previously, the Cinder API did not perform a status check when updating attachment objects on a volume and the API allowed volumes in error state to update attachment records.

With this update, the Cinder API checks volume status when creating or updating an attachment. If the volume is in any error state, the call returns an `invalidVolume` exception. (BZ#1692542)

Solution

Before applying this update, ensure all previously released errata relevant
to your system have been applied.

Red Hat OpenStack Platform 13 runs on Red Hat Enterprise Linux 7.6.

The Red Hat OpenStack Platform 13 Release Notes contain the following:

• An explanation of the way in which the provided components interact to

form a working cloud computing environment.

• Technology Previews, Recommended Practices, and Known Issues.
• The channels required for Red Hat OpenStack Platform 13, including which

channels need to be enabled and disabled.

The Release Notes are available at:
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/release_notes/

This update is available through 'yum update' on systems registered through
Red Hat Subscription Manager. For more information about Red Hat
Subscription Manager, see:

https://access.redhat.com/documentation/en-US/Red_Hat_Subscription_Management/1/html/RHSM/index.html

Affected Products

• Red Hat OpenStack for IBM Power 13 ppc64le
• Red Hat OpenStack 13 x86_64

Fixes

• BZ - 1613486 - Backport: Dell EMC SC: Enabled multiattach in Storage Center Driver
• BZ - 1638051 - Backport: Dell EMC Xtremio: Enabled multiattach in volume driver
• BZ - 1639820 - Glance image download leads to unhandled python NoneType error
• BZ - 1676603 - Support for HPE MSA2050 in Queens.
• BZ - 1684208 - [OSP13] VNX driver sends a remove_hba() to storops instead of delete_hba()
• BZ - 1693338 - [OSP13] When a a storagegroup is destroyed because it's empty, VNX driver doesn't recreate it upon subsequent attachment
• BZ - 1694113 - Backport: Dell EMC Unity: Enabled multiattach in Unity Volume Driver
• BZ - 1696662 - Rebase openstack-cinder to 12.0.6

CVEs

(none)

References

(none)