Details:
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.
It was discovered that a user could temporarily be able to see the URL of a provider template used in another tenant. If the template itself could be accessed, then additional information could be leaked that would otherwise not be visible. (CVE-2014-3801)
The openstack-heat packages have been upgraded to upstream version 2013.2.4, which provides a number of bug fixes and enhancements over the previous version. The most notable enhancements are:
This update also fixes the following bugs:
Prior to this update, Qpid would attempt to reconnect to a broken message broker, even though multiple hosts were configured. With this update, reconnect() selects the next broker in the list for each connection attempt. (BZ#1082672)
Prior to this update, certain Qpid exceptions were not properly handled by the Qpid driver. As a result, the Qpid connection would fail and stop processing subsequent messages. With this update, all possible exceptions are handled to ensure the Qpid driver does not enter an unrecoverable failure loop. Consequently, Orchestration (heat) will continue to process Qpid messages, even after a major exception occur. (BZ#1085996)
The Qpid driver's v2 topology has been introduced to specifically address the slow growth of orphaned direct exchanges over time. By default, however, services still used the original v1 topology...
0:2013.2.4-1.el6ost0:2013.2.4-1.el6ost0:2013.2.4-1.el6ost0:2013.2.4-1.el6ost0:2013.2.4-1.el6ost0:2013.2.4-1.el6ost