RHBA-2014:0209 - Bug Fix Advisory

Topic

OpenShift Enterprise by Red Hat release 2.0.3 is now available with updates to
packages that fix several bugs and introduce feature enhancements.

Description

OpenShift Enterprise by Red Hat is the company's cloud computing
Platform-as-a-Service (PaaS) solution designed for on-premise or private cloud
deployments.

Space precludes documenting all of the bug fixes and enhancements in this
advisory. See the OpenShift Enterprise Technical Notes at
https://access.redhat.com/site/documentation for details about these changes.

All OpenShift Enterprise by Red Hat users are advised to upgrade to these
updated packages.

Solution

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

See the OpenShift Enterprise 2.0 Release Notes at
https://access.redhat.com/site/documentation for instructions on applying this
specific update.

This update is available via the Red Hat Network. Details on how to use the Red
Hat Network to apply this update are available at
https://access.redhat.com/site/articles/11258.

Affected Products

• Red Hat OpenShift Enterprise Infrastructure 2.0 x86_64
• Red Hat OpenShift Enterprise Application Node 2.0 x86_64
• Red Hat OpenShift Enterprise Client Tools 2.0 x86_64

Fixes

• BZ - 988756 - Add Requires: bc to jbosseap and jbossews spec file
• BZ - 1027122 - Running lokkit tools on node will block openshift-iptables-port-proxy service starting.
• BZ - 1032798 - unable to create scaled app because of misconfigured iptables method
• BZ - 1040257 - cannot add an alias that shares the same root of the existing domain
• BZ - 1040824 - openshift-iptables-port-proxy service will return failure when user add iptable rules into NAT tables
• BZ - 1045972 - Modidying configure text file for gear shell message is invalid
• BZ - 1048139 - VALID_SSH_KEY_TYPES related content should be added into broker.conf
• BZ - 1051190 - Provide ability to customize haproxy auto scaling algorithm
• BZ - 1054916 - RFE admin should be able to augment cartridge httpd conf without a custom cartridge
• BZ - 1054944 - If deployment registration fails in a scaled app, haproxy needs restarting
• BZ - 1055675 - ruby193-mcollective sysconfig should handle environment variables better
• BZ - 1056394 - The snapshot save/restore failed after gear is moved
• BZ - 1056899 - Cannot scale up via haproxy_ctld in the secondary haproxy since broker auth does not exist on that gear
• BZ - 1056905 - Error message should be highlighted when adding invalid member to domain.
• BZ - 1057153 - RFE enable administrator to provide default application git templates
• BZ - 1057183 - Backport HAproxy auto-scaling enhancements
• BZ - 1057447 - Rails app can not be restarted when created from code with missing dependency
• BZ - 1057956 - It always exists some error message with "Failed to get information from haproxy" in the scale_events.log as it is normal
• BZ - 1059322 - Fix vhost template hostname logging
• BZ - 1059900 - rhc fails to display correct information
• BZ - 1061422 - empty metadata.json breaks app deployment
• BZ - 1061423 - Gear is not started after restore when hot_deploy marker is present for all cartridges
• BZ - 1061424 - The hot_deploy marker/--hot-deploy option can not take effect when deploying app with binary deployment
• BZ - 1061941 - The broker nsupdate plugin and oo-accept-broker need to allow additonal dns key algorithms
• BZ - 1062844 - Should give a meaningful message when creating one app with an invalid manifest file
• BZ - 1063769 - deployment roll back does not sync contents to every web gears

CVEs

(none)

References

(none)