Chapter 15. RHBA-2014:0781 - OpenShift Enterprise 2.1.2 Bug Fix Update

Broker

BZ#1102430

When the sample routing plug-in was configured with an array of ActiveMQ brokers, the broker service would not start properly. This bug fix adds support to interpret the ACTIVEMQ_HOST parameter in the /etc/openshift/plugins.d/openshift-origin-routing-activemq.conf file as a comma-separated list of host:port pairs, and use this list of hosts when connecting to ActiveMQ for redundancy. The broker service now starts properly, and the sample routing plug-in can now be configured with more than one ActiveMQ broker.

Copy to Clipboard Toggle word wrap

BZ#1084292

If a customized gear placement plug-in was incorrectly configured and returned an invalid node host name, creating a new application reported a communication error when it could not find the node on which to place gears. However, a record for the failed application was created in the MongoDB datastore, even though related gears did not exist on any nodes. This bug fix adds logic to validate the node host name returned by the gear placement plug-in. If the validation fails, the application creation is rolled back completely and datastore records for failed applications are no longer created.

Copy to Clipboard Toggle word wrap

BZ#1100169

After a custom SSL certificate for an alias was added to an application, the oo-diagnostics tool reported warning messages that the permissions on configuration files were not correct. This was due to the oo-diagnostics tool running a test that checked for more than was actually required. This bug fix updates the oo-diagnostics tool to only check files that Apache actually reads at runtime, and the warnings no longer occur for alias certificates.

Copy to Clipboard Toggle word wrap

BZ#1102303

If an authorization token was created containing scopes for multiple domains, it was possible for the domain scopes to interfere with each other and cause queries using the token to not return the full list of authorized applications. This bug fix adds logic to ensure that queries are accurately returned when using authorization tokens with multiple domain scopes.

Copy to Clipboard Toggle word wrap

Cartridge

BZ#1044980

A change to Passenger caused applications using Ruby 1.8 or 1.9 cartridges to report pre-starting errors, and applications would only start after a first request was made. The issue was fixed for Ruby 1.9 cartridges in an earlier release of OpenShift Enterprise; this bug fix updates Passenger to correct the issue for Ruby 1.8 cartridges as well. Pre-starting now functions properly for both Ruby cartridges, and the previous errors no longer occur.

Copy to Clipboard Toggle word wrap

Command Line Interface

BZ#1102736

The client tools RPM package that shipped with OpenShift Enterprise release 2.1 did not include full support for managing teams. Team management was previously only available using the upstream client tools gem or using the REST API. This bug fix adds full team management support to the RPM package starting in rhc-1.24.3.1-1.el6op; see the following section of the OpenShift Enterprise User Guide for more usage information:

https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/2/html-single/User_Guide/index.html#sect-Team_Management

Copy to Clipboard Toggle word wrap

BZ#1007454

Previously, using the oo-admin-ctl-app command with the `-c status` option only returned the state of the application and any of its add-on cartridges, for example whether they were running or stopped. This bug fix updates the oo-admin-ctl-app command and now the `-c status` option also returns the application UUID and each of its gear UUIDs.

Copy to Clipboard Toggle word wrap

Installer

BZ#1097844

The oo-admin-yum-validator tool that shipped with OpenShift Enterprise release 2.1 did not automatically detect the installed product version, which is the default behavior when run without any arguments. Because the oo-diagnostics tool runs the oo-admin-yum-validator tool without any arguments, running the oo-diagnostics tool on release 2.1 reported a warning that it could not detect the product version. This bug fix adds this detection back into the oo-admin-yum-validator tool for release 2.1, and the oo-diagnostics tool no longer reports the warning.

Copy to Clipboard Toggle word wrap

Management Console

BZ#1100507

When choosing an application type to create on the /console/application_types page of the Management Console, the JBoss Enterprise Application Platform 6 cartridge is placed in the "Other types" group instead of in the "Java" group. This was due to how tags were parsed for cartridges with multiple tags. This bug fix improves application type grouping and the JBoss EAP 6 cartridge now appears in the "Java" group.

Copy to Clipboard Toggle word wrap

Node

BZ#1070629

If quotas were not set for a gear, the oo-accept-node command reported the issue without any suggested solutions. This bug fix updates the oo-accept-node command to provide in these cases a suggested oo-devel-node command, either based on quota settings in the /etc/openshift/resource_limits.conf file or default values, that can be run to address the issue.

Copy to Clipboard Toggle word wrap

BZ#1103138

Starting the openshift-node-web-proxy service under certain conditions, in particular when using the oo-install installation utility, caused the service to be immediately killed when the user ended their session. This bug fix corrects this issue and the service now starts normally, including when using the installation utility.

Copy to Clipboard Toggle word wrap

BZ#1102325

When using the apache-vhost front-end proxy plug-in on nodes, the application was unreachable for a short period of time when changes were pushed using Git, caused by the Apache back end being temporarily disabled. This bug fix updates the plug-in to ensure that the back end is not disabled in these cases, and applications are now immediately reachable after changes are pushed.

While this bug fix applies to any newly created gears, for the updated package to take effect for existing gears, the following commands must be run on affected node hosts. These steps are recommended only for systems where the rubygem-openshift-origin-frontend-apache-vhost package is installed. Please note that this will cause a node outage, and should be performed during a planned broker maintenance outage. See the OpenShift Enterprise Administration Guide for full documentation on modifying the front-end proxy server plug-in configuration.

# oo-frontend-plugin-modify --save > filename
# oo-frontend-plugin-modify --delete
# oo-frontend-plugin-modify --restore < filename

Copy to Clipboard Toggle word wrap

BZ#1101524

Deploying a downloadable cartridge that had a malformed manifest to an application reported an error, however the cartridge was still added to the application. As a result, the application could no longer be deleted using the client tools. This bug fix updates manifest validation when adding cartridges; adding a downloadable cartridge with a malformed manifest now provides better information on problematic entries and the cartridge is no longer added to the application.

Copy to Clipboard Toggle word wrap

BZ#1103294

If the /var/log/openshift/node/ruby193-mcollective.log file on a node host was missing, the oo-diagnostics tool hung during the test_node_mco_log check. This bug fix updates the oo-diagnostics tool to fail gracefully when the file is missing and report the error, and the tool no longer hangs as a result.

Copy to Clipboard Toggle word wrap

BZ#1107840

The rsyslog7 RPM package did not have an explicit version set for its libestr dependency, which caused problems if the build time version was not available at runtime. This bug fix adds an explicit version dependency of "libestr >= 0.1.9" for the rsyslog7 RPM package and these issues no longer occur.

Copy to Clipboard Toggle word wrap