Chapter 8. RHBA-2015:0019 - OpenShift Enterprise 2.2.3 Bug Fix and Enhancement Update

Broker

BZ#1165775

Previously, the oo-admin-ctl-team command did not parse uniqueMember LDAP attributes correctly. As a result, the command failed when administrators provided a full DN when specifying uniqueMember attributes. This bug fix updates the oo-admin-ctl-team command to split uniqueMember attributes at the first ',' character, and uniqueMember attributes can now contain a full DN.

BZ#1163473

Previously, binary deployments using an artifact_url with special characters in the URL would fail due to the artifact_url not being properly decoded. This bug fix updates the deployment process so that the artifact_url is properly URI encoded, and as a result this deployment scenario now works as expected.

Cartridge

BZ#1089967

The Ruby Bundler for ruby18 applications was out of date and had compatibility issues with rubygems.org. This issue caused ruby18 applications that used 'bundle install' to take prohibitively long to deploy. This bug fix updates Ruby Bundler, and as a result 'bundle install' now completes in a timely manner.

BZ#1170789

The Node.js cartridge was not configured properly on all possible cartridge upgrade paths. This issue made it possible for environments skipping intermediate updates to not have a properly configured Node.js deployment. This bug fix updates the Node.js cartridge so that all upgrade paths configure Node.js properly, and as a result this issue no longer occurs.

BZ#1170784

Due to a bug in the MySQL cartridge, the OPENSHIFT_MYSQL_VERSION environment variable was previously not set during MySQL cartridge updates in all cases. As a result, gears trying to use the variable may not have the expected value. This bug fix updates the MySQL cartridge to ensure that the variable is set in all cases, and as a result the variable now contains the expected value.

Command Line Interface

BZ#1154344

A node host's root user must have SSH keys in place in order to clone an application from a Git repository over SSH. However, it is not common for developers who are deploying applications to have the ability to deploy SSH keys to the root user. As a result, cloning applications over SSH is not supported. This bug fix updates the node logic to provide a more appropriate error message in this scenario indicating the developer should clone over a non-SSH protocol.

Installer

BZ#1166277

The subscription-manager package version 1.10.7 and higher now incorporates the "content override" feature, which typically requires network communication with a back-end server. As a result, certain oo-admin-yum-validator functions related to subscription-manager, which had previously only operated on the local file system in older subscription-manager versions, could now raise unhandled exceptions due to network failures. This bug fix wraps routines depending on subscription-manager in exception-handling blocks, and scripts which depend on the oo-admin-yum-validator command can now detect that it failed due to network errors. Administrators are now presented with a relevant error message instead of a confusing stack trace.

BZ#1167247

In a previous release, changes were made so that certain messages, in particular "exclude" suggestions made by the oo-admin-yum-validator command, contained improperly quoted portions. This issue could lead administrators to break their RHN configurations. This bug fix updates the logic for quoting parameters so that it can be enabled only when appropriate. As a result, these suggestions generated by the oo-admin-yum-validator command are now accurate.

BZ#1174486

Previously, attempting to upgrade puppet to version 3.x on node hosts would fail with dependency errors related to the version of facter shipped in the OpenShift Enterprise Node channel. This bug fix updates the oo-admin-yum-validator command's yum configuration suggestions to exclude the facter package, which is no longer used by OpenShift Enterprise. As a result, puppet can now be upgraded to version 3.x on node hosts.

Node

BZ#1171254

Watchman logs were previously named cgroups.log and cgroups-trace.log. This feature renames these files to watchman.log and watchman-trace.log, respectively, for increased clarity.

BZ#1169303

Previously, Watchman did not clean up empty front end configuration directories for scalable database gears. As a result, empty directories remained in place after applications had been deleted. This bug fix updates Watchman to now properly remove these directories in this case.

BZ#1173246

Previously, the Watchman OOM plug-in waited unnecessarily for pkill to exit, which could take a long time and block other tasks. This bug fix updates Watchman to now run pkill tasks in the background. As a result, Watchman now continues processing other tasks while pkill operations are processed in the background.

BZ#1173026

Previously, Watchman deleted front end configuration directories for secondary gears before the gears were removed. As a result, Watchman could yield a broken front end configuration. This bug fix updates Watchman to now only remove configuration directories which have no references in other configuration files, and Watchman no longer prematurely removes front end configurations for secondary gears.

BZ#1171257

The oo-admin-cartridge command did not return a proper exit status after cartridge installation failures. Scripted cartridge installation may have failed silently as a result. This bug fix updates the oo-admin-cartridge command to now only return 0 if at least one cartridge installed properly. As a result, scripts installing a single cartridge can now handle installation failures properly.