- Issued:
- 2019-01-16
- Updated:
- 2019-01-16
RHBA-2019:0074 - Bug Fix Advisory
Synopsis
openstack-nova bug fix advisory
Type/Severity
Bug Fix Advisory
Red Hat Insights patch analysis
Identify and remediate systems affected by this advisory.
Topic
Updated OpenStack Compute 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 Compute service
OpenStack Compute (nova) launches and schedules large networks of virtual
machines, creating a redundant and scalable cloud computing platform.
Compute provides the software, control panels, and APIs required to
orchestrate a cloud, including running virtual machine instances and
controlling access through users and projects.
Changes to the openstack-nova component:
- With this update, Nova screens for the NUMA affinity of host huge pages when booting instances with huge pages. Nova rejects NUMA nodes with insufficient huge pages.
Prior to this update, Nova did not screen for NUMA affinity of huge pages. If the host had insufficient NUMA pages, even with sufficient CPUs, the instance boot would fail. (BZ#1519540)
- This update introduces vrouter mulitqueue support required by a Juniper plug-in.
One of Juniper's plugins relies on nova to create interfaces with the correct mode - multi-queue or single-queue.
vrouter VIFs (OpenContrail) now support multiqueue mode, which allows network performance to scale across multiple vCPUs.
To use this feature, create an instance with more than 1 vCPU from an image that has the `hw_vif_multiqueue_enabled` property set to `true`. (BZ#1608521)
- This update introduces a new config option, cpu_pinning_migration_quick_fail.
The option only applies to instances with pinned CPUs. It controls the failing of live migrations in the scheduler if the required CPUs aren't available on the destination host.
When an instance with CPU pinning is live migrated, the upstream behavior is to keep the CPU mapping on the destination identical to the source. This can result in multiple instances pinned to the same host CPUs. OSP contains a downstream workaround (absent from upstream OpenStack) that prevents live migration if the required CPUs aren't available on the destination host.
The workaround's implementation places the same destination CPU availability restrictions on all other operations that involve scheduling an instance on a new host. These are cold migration, evacuation, resize and unshelve. For these operations, the instance CPU pinning is recalculated to fit the new host, making the restrictions unnecessary. For example, if the exact CPUs needed by an instance are not available on any compute host, a cold migration would fail. Without the workaround, a host would be found that can accept the instance by recalculating its CPU pinning.
You can disable this workaround by setting cpu_pinning_migration_quick_fail to False. With the quick-fail workaround disabled, live migration with CPU pinning reverts to the upstream behavior, but the restrictions are lifted from all other move operations, allowing them to work correctly. (BZ#1613242)
- This update fixes issues that could leave an instance record in an inconsistent state after failure of a volume API (Cinder) call during a live migration.
Prior to this update, if the volume API call failed, the live migration didn't finish correctly and the instance record was left in an inconsistent state in the database.
With this update, the instance record is updated correctly in such cases. The volume API error is logged. Administrators may need to clean up the instance's volume attachments. (BZ#1636102)
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.5.
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/red-hat-openstack-platform/10/paged/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 - 1519540 - [rhos10] nova reporting incorrect available memory
- BZ - 1532683 - Virtual Device Role Tagging does not work with interfaces of vnic-type: direct-physical
- BZ - 1608521 - Backport libvirt virt dirver vrouter multiqueue support
- BZ - 1613242 - Cold Migration fails with NUMATopologyFilter and CPU pinning
- BZ - 1633117 - after successful resize Nova recreates instance directory was showing disk already existed
- BZ - 1636102 - Update instance host and task state when post live migration fails
CVEs
(none)
Red Hat OpenStack 10
SRPM | |
---|---|
openstack-nova-14.1.0-35.el7ost.src.rpm | SHA-256: a3b71a62581251506673e786fca5c09f3f74faed221ac5546ae0a6ffeba33815 |
x86_64 | |
openstack-nova-14.1.0-35.el7ost.noarch.rpm | SHA-256: b3ced1d295a7f6873b9927cdd98809bc5f0e768764ccf71c13e02af32afa9968 |
openstack-nova-api-14.1.0-35.el7ost.noarch.rpm | SHA-256: c9e0feb33523bab6865a817fa9ecff9caceba4c7f0c414dbc8493c915a82a659 |
openstack-nova-cells-14.1.0-35.el7ost.noarch.rpm | SHA-256: 251c9c00b2fb13787ad6a14ea63d3d69209aa8275dc643ef87c8e0ea4322612b |
openstack-nova-cert-14.1.0-35.el7ost.noarch.rpm | SHA-256: 210cf2f8dc961e69ca3afe1370719051a5558cc380697f72dd4d5fa88d31d63a |
openstack-nova-common-14.1.0-35.el7ost.noarch.rpm | SHA-256: eda18ddf89f77d01cb73d7cc2a9bae9c4677b7d161017f9d284245137a30daea |
openstack-nova-compute-14.1.0-35.el7ost.noarch.rpm | SHA-256: ff6429c5aa30ec1092b4dd412d6c66d882fed8811dcf75d8f978b60dee602c80 |
openstack-nova-conductor-14.1.0-35.el7ost.noarch.rpm | SHA-256: 6ed2a0e5e74f06d943e048791762f03aaff8959abaad5433b4771e4b2b388953 |
openstack-nova-console-14.1.0-35.el7ost.noarch.rpm | SHA-256: a98401eee7b73f4308186ebda51bbb3f85883fc77ee02805e240481c2dbe931c |
openstack-nova-migration-14.1.0-35.el7ost.noarch.rpm | SHA-256: b05cabcea780dd5627fe5ef83048c27851a48e7fa8414b74056b6857ac1ccaf1 |
openstack-nova-network-14.1.0-35.el7ost.noarch.rpm | SHA-256: fe2d93cd550450661c96e0bba97fa973c74adfd15ae35a4c9e3f52f73a713e49 |
openstack-nova-novncproxy-14.1.0-35.el7ost.noarch.rpm | SHA-256: 4f337f11cc9a1c2cf1a337cd7eea9df812505d9917c0289caec6baef5484e238 |
openstack-nova-placement-api-14.1.0-35.el7ost.noarch.rpm | SHA-256: e83a411a42b7f6ff873656e30b8b0de63791677380990d1836e9d3f6e2ce3408 |
openstack-nova-scheduler-14.1.0-35.el7ost.noarch.rpm | SHA-256: dff7fe3e9c6b2d5899ae6ba717f7b5fef91cf3eabcf15779d0c1205c2d5bc692 |
openstack-nova-serialproxy-14.1.0-35.el7ost.noarch.rpm | SHA-256: 0243e740c54cd269fe314b32bcd3f29a5b386a39ba045b9339daddefc053c27c |
openstack-nova-spicehtml5proxy-14.1.0-35.el7ost.noarch.rpm | SHA-256: 616c791b429db85c0d1ebc7353028938cb62d9cded3017dbf2209f8f20471f60 |
python-nova-14.1.0-35.el7ost.noarch.rpm | SHA-256: 42f5dabeaed28602a40c42d89e811234447e8075cc986d59f960ea64bead42f8 |
python-nova-tests-14.1.0-35.el7ost.noarch.rpm | SHA-256: a7888192aaa09e8c64dc5b294cfe9778926eef16783a530dd6ecd0b8770a501c |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.