- Issued:
- 2020-04-02
- Updated:
- 2020-04-02
RHBA-2020:1301 - Bug Fix Advisory
Synopsis
openstack-cinder bug fix advisory
Type/Severity
Bug Fix Advisory
Red Hat Lightspeed patch analysis
Identify and remediate systems affected by this advisory.
Topic
Updated OpenStack Block Storage packages that resolve various issues are
now available for Red Hat OpenStack Platform 10.0 (Newton) 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:
- In previous releases, the xtremio driver inaccurately reported the amount of available storage capacity. VMs using the Block Storage back end could fail to provision because the reported capacity was greater than the actual amount of available storage. With this release, the xtremio driver reports the correct amount of available storage capacity. (BZ#1808692)
- In previous releases, the Block Storage NFS volume migration code renamed the volume file on the destination NFS server to match the name on the source NFS server. The volume migration process finished by deleting the source volume. However, when retyping an NFS volume using migration, the source and destination might be the same. When you retyped an NFS volume using migration, the NFS volume file would be inadvertently deleted if the source and destination back ends were on the same NFS server.
With this release, retyping an NFS volume using migration works correctly. When you migrate an NFS volume, the volume file is renamed only when the source and destination files reside on different NFS servers. (BZ#1752560)
Solution
Before applying this update, ensure all previously released errata relevant
to your system have been applied.
Red Hat OpenStack Platform 10 runs on Red Hat Enterprise Linux 7.7.
The Red Hat OpenStack Platform 10 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 10, 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/10/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 10 x86_64
Fixes
- BZ - 1752560 - Cinder retype from non-type to new type on NFS deletes the Volume
- BZ - 1808692 - xtremio is reporting wrong free_capacity_gb
CVEs
(none)
References
(none)
Red Hat OpenStack 10
| SRPM | |
|---|---|
| openstack-cinder-9.1.4-55.el7ost.src.rpm | SHA-256: f9cbd99848992c62e14dcfbdab08770d3d8eb94585a31adb9fffe09484f19b73 |
| x86_64 | |
| openstack-cinder-9.1.4-55.el7ost.noarch.rpm | SHA-256: 3785753c320ecf8892860eaad59758045e1071460c220e539fa5a07d343eeca0 |
| python-cinder-9.1.4-55.el7ost.noarch.rpm | SHA-256: 53c75d415b8fd28105d17c0f864bba40a0c94bf10eb0a7136fa618b20f76661a |
| python-cinder-tests-9.1.4-55.el7ost.noarch.rpm | SHA-256: 08ce76e531fa68ad4a94abe7100c9a46c9126480db3d46de843c01f327d2448a |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.