RHBA-2015:1865 - Bug Fix Advisory

Topic

Updated OpenStack Orchestration packages that resolve various issues are
now available for Red Hat Enterprise Linux OpenStack Platform 7.0 (Kilo)
for RHEL 7.

Description

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

• OpenStack Orchestration service

OpenStack Orchestration (heat) is a template-driven engine used to specify
and deploy configurations for Compute, Storage, and OpenStack Networking.
It can also be used to automate post-deployment actions, which in turn
allows automated provisioning of infrastructure, services, and
applications. Orchestration can also be integrated with Telemetry alarms to
implement auto-scaling for certain infrastructure resources.

With this update, the Orchestration service is now re-based to upstream
version 2015.1.1 (BZ#1258598). This applies several fixes, including:

• If a resource did not have an associated nested stack, a NotFound

exception would be raised. Whenever this occurred, the 'heat
resource-list' incorrectly associated the NotFound exception with the
root stack rather than the nested stack.

Now, the internal API contract now correctly returns 'None' when there
are missing nested stacks. As such, 'heat resource-list' now works as
expected.(BZ#1244485)

• Orchestration services log rotation used to be done only on schedule,

which made it possible for logs to grow and fill up disk space. This
update sets a log rotation size trigger to prevent this from happening.
(BZ#1254350)

• It was possible for deployment signaling to cause other deployments to

remain in an IN_PROGRESS state until stack timeout. This prevented
deployment data from reaching overcloud nodes, causing the overcloud
deployment to time out and go into a FAILED state.

This issue was caused by legacy code paths, which have now been
disabled. Now, metadata is only updated using the resource-level
locking mechanism. This mechanism correctly handles concurrent metadata
updates.(BZ#1255759)

• On a PATCH update, the existing environment is now retained unless

explicitly overridden. This allows the Orchestration service to re-use
other parts of the environment, not just the parameters that passed
previously (and not overriden).

This suits most common stack update cases, where users prefer to
maintain the current environment (including resource mappings and the
like). (BZ#1257717)

• Null values are now converted to empty strings. This change was done

to prevent validation failures in perfectly valid template resources,
which prevented them from being created in previous releases.
(BZ#1257273)

• Previously, when a stack update failed the Orchestration service

continued to store the old parameter values instead of the ones
supplied with the failed update attempt. Whenever this occurred, the
Orchestration service incorrectly showed the parameter values from the
last successful update. If the parameter schema of the template changed,
attempting to show the failed stack sometimes resulted in an error.

Now, the Orchestration service updates stored parameter values with new
values during and after a failed update. As a result, when showing a
stack, the parameter values will be the last ones supplied even after a
failed update. (BZ#1258967)

• On each resource event, the Orchestration service stores the current

properties of the resource to enable debugging and auditing of the
stack's history. However, the Orchestration service can only store 64kB
(encoded) of such information. As such, stacks with particularly large
properties prevented the Orchestration service from recording events for
the resource in questions, thereby preventing the stack from being
created.

With this release, properties that are too large to store in the event
table are elided. This, in turn, allows users to create stacks regardless
of the size of each resources' properties.(BZ#1261512)

Solution

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

Red Hat Enterprise Linux OpenStack Platform 7 runs on Red Hat Enterprise
Linux 7.1.

The Red Hat Enterprise Linux OpenStack Platform 7 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 Enterprise Linux OpenStack Platform 7,

including which channels need to be enabled and disabled.

The Release Notes are available at:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html/Release_Notes/index.html

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 7 x86_64

Fixes

• BZ - 1244485 - Heat stack partially deleted, it shows in stack-list but isn't found when you do resource-list
• BZ - 1255759 - heat race condition causing deployments to get stuck at various places
• BZ - 1256564 - DELETE_FAILED when trying to delete an already FAILED stack
• BZ - 1257273 - Heat templates fail on validation
• BZ - 1257717 - Environment files must be passed anew on every stack update
• BZ - 1258598 - Rebase openstack-heat to 2015.1.1
• BZ - 1258967 - Parameters in stack-show are not updated after a failed update
• BZ - 1261512 - heat stack create error "Data too long for column 'resource_properties' at row 1"
• BZ - 1265676 - Cannot signal resource during DELETE

CVEs

(none)

References

• http://www.redhat.com/security/updates/classification/#normal