Chapter 13. RHBA-2014:1095 - OpenShift Enterprise 2.1.5 Bug Fix and Enhancement Update

Broker

BZ#1123743

If regions did not exist in an OpenShift Enterprise environment, a confusing error message was displayed to users after creating an application. This was due to a bug in the broker's controller library. This bug fix updates the controller logic and now the broker checks to see if regions exist before displaying the error.

Copy to Clipboard Toggle word wrap

BZ#1083380

The broker previously handled logins with different letter cases as distinct user accounts. For example, the broker would store separate accounts for the logins "JDoe" and "jdoe". This issue caused confusion for users when applications were created under different accounts, among other problems. This enhancement allows administrators to enable a selection of default or custom methods on the broker to enforce user login normalization. When normalization methods are set, the broker now handles logins based on these settings. See the OpenShift Enterprise Administration Guide for more information.

Copy to Clipboard Toggle word wrap

BZ#1123944

When the oo-app-info command was used to search for an application by its fully-qualified domain name (FQDN), the domain for the FQDN was assumed to be "rhcloud.com". As a result, the search did not work outside of the OpenShift Online environment. This bug fix updates the search to be generalized for any cloud domain, and searching for an application by its FQDN now works as expected.

Copy to Clipboard Toggle word wrap

BZ#1123353

When the 'oo-admin-ctl-app -c set-multiplier' command was run for the web framework cartridge of a scalable application with only one gear, the MongoDB record for the application was broken, making the application unscalable. This bug fix updates the application model code in the controller, and MongoDB records for applications are no longer susceptible to this issue as a result.

Copy to Clipboard Toggle word wrap

BZ#1109549

The oo-admin-ctl-app command now has the --alias option which allows administrators to add or remove an alias from an application.

Copy to Clipboard Toggle word wrap

BZ#1120825

Previously, domain environment variables were not set when running cartridge install and setup scripts. This was due to a bug in the broker's Application model object. This bug fix updates the Application model, and environment variables are now correctly set before running the install and setup scripts.

Copy to Clipboard Toggle word wrap

BZ#1122496

When creating an application, it was possible in certain situations for a user without the additional storage capability to add storage within a domain. This occurred because the additional storage capability was checked for the wrong user account, which was due to a bug in the broker's controller library. This bug fix updates the controller library and now the domain owner's capabilities are correctly checked.

Copy to Clipboard Toggle word wrap

BZ#1108575

Previously, when users removed additional storage from an application while specifying the HAProxy cartridge, the action completed successfully but the storage removal was not accurately reported. This bug fix updates the broker's controller logic and now storage is accurately reported in this scenario.

Copy to Clipboard Toggle word wrap

BZ#1122935

Previously, if a scalable application was made highly available, gears were removed during scale down events in reverse order of creation without consideration for whether the HAProxy cartridge minimum or HAProxy multiplier were maintained. This issue made it possible for a highly-available application to remove more HAProxy gears than it should when scaling down, potentially rendering the application no longer highly available. This bug fix updates the controller logic, and the gear selected for removal is now chosen to maintain the proper constraints.

Copy to Clipboard Toggle word wrap

Cartridge

BZ#1106414

The rhcsh command that is used for interactive gear logins had a bug in the psql function. This function wraps the actual command-line tool to automatically provide database access credentials, but it always returned exit code 0, even when the command had actually failed. This issue could confuse scripts using the function. This bug fix updates the rhcsh command to preserve the exit code correctly, and the psql function exits as expected as a result. Users must reconnect to their gear using SSH to pick up the new function after applying this fix.

Copy to Clipboard Toggle word wrap

BZ#1105107

A bug in the MySQL and PostgreSQL cartridges prevented the PATH from being set correctly. As a result, the wrong versions of executables could be loaded. This bug fix updates the publish-ld-library-path-info hook to correctly set the PATH. A cartridge upgrade is required after applying this fix.

Copy to Clipboard Toggle word wrap

BZ#1123077

The HAProxy cartridge was missing locking in its reload logic, and a race condition could lead to multiple HAProxy processes inside a gear. This bug fix updates the HAproxy cartridge to add proper locking, and this issue no longer occurs as a result. A cartridge upgrade is required after applying this fix.

Copy to Clipboard Toggle word wrap

BZ#1118275

A bug in the JBoss EWS cartridge caused broken symlinks to be created if configuration files did not exist in a JBoss EWS binary deployment, which caused the application to be unable to deploy. This bug fix updates the control script for the JBoss EWS cartridge to handle scenarios where a deployment archive does not contain configuration files. A cartridge upgrade is required after applying this fix.

Copy to Clipboard Toggle word wrap

BZ#1112152

Default ruby-1.8 applications contained an unnecessary library inclusion, which could result in 503 errors when the library was not available in some environments. This bug fix updates the Ruby cartridge to remove the library reference, and these errors no longer occur on new gears that are created after applying this fix. A workaround for existing gears is to manually remove the library.

Copy to Clipboard Toggle word wrap

BZ#1084950

The PostgreSQL cartridge was not configured properly. Administrators could be confused by an incorrect IPv6 IP range, and the configuration for limiting PostgreSQL connections to only the local socket was incorrect. This bug fix updates the PostgreSQL cartridge, and both of these issues are resolved for the purpose of hardening security. Other security measures prevent these problems from posing actual risk. A cartridge upgrade is required after applying this fix.

Copy to Clipboard Toggle word wrap

BZ#1116823

Due to a default Jenkins setting, an error message appeared in Jenkins logs in environments where UDP was disabled. This bug fix adds a new marker file to disable UDP for Jenkins by default, because it is not required for OpenShift Enterprise, and the errors no longer appear as a result. A cartridge upgrade is required after applying this fix.

Copy to Clipboard Toggle word wrap

BZ#1117949

After adding a customized haproxy_ctld.rb file to a scalable application, the application continued to use the customized file for automatic scaling even after the file had been removed from the application's Git repository. This was due to a bug in the HAProxy cartridge. This bug fix updates the HAProxy cartridge control script to handle the removal of customized haproxy_ctld.rb files, and applications now return to using the default file for automatic scaling after a customized file has been removed. A cartridge upgrade is required after applying this fix.

Copy to Clipboard Toggle word wrap

BZ#1125295

Due to a race condition in the JBoss EWS cartridge control script, the parent EWS process was killed before the child processes in certain situations, causing the control script to report an error. This bug fix improves the fallback process clean-up logic to handle this error, and the issue no longer occurs as a result. A cartridge upgrade is required after applying this fix.

Copy to Clipboard Toggle word wrap

Client Tools

BZ#1006068

Previous versions of the client tools were configured for use with a single OpenShift server at a time. The configuration settings in the ~/.openshift/express.conf file would be overwritten each time the client tools were configured for use with a new server. This enhancement enables the client tools shipped with OpenShift Enterprise to be configured for use with multiple servers, which is useful when using a single workstation to manage different applications hosted across multiple servers. See the OpenShift Enterprise User Guide for more information.

Copy to Clipboard Toggle word wrap

BZ#1109382

Previously, the 'rhc app-show <app_name> --gears' command reported HAProxy cartridges on every gear if the application was scalable. This reporting was not accurate, as each gear in the list should report only the cartridges actually on the gear. This bug fix updates the client tools, and HAProxy cartridges on gears are now accurately reported.

Copy to Clipboard Toggle word wrap

BZ#1128986

The --ssl-client-key-file option was missing in the --help output for the 'rhc server add' and 'rhc server configure' commands. This bug fix updates the --help output for these rhc commands, and the option is now shown as expected.

Copy to Clipboard Toggle word wrap

Node

BZ#1108653

Attempting to scale a custom, non-web-framework cartridge previously resulted in an exception trying to create a web endpoint registry. This bug fix avoids this unnecessary step, and the exceptions no longer occur as a result.

Copy to Clipboard Toggle word wrap

BZ#1108910

Due to a bug in the OpenShift Enterprise runtime, quota settings were not removed when gears were deleted. This bug fix updates the gear deletion logic to include quota configuration removal, and quota settings are now correctly removed when gears are deleted.

Copy to Clipboard Toggle word wrap

BZ#1097748

Previously, it was difficult to distinguish between debug and trace log output on nodes because both log types were written using the local0 facility. This bug fix adds new settings to allow for better distinction between log types. Logs are now written using the facility defined by the PLATFORM_SYSLOG_FACILITY setting (default: LOG_LOCAL0), and, if trace logging is enabled, trace logs are now written using the facility defined by the PLATFORM_SYSLOG_TRACE_FACILITY setting (default: LOG_LOCAL1). Administrators can change these settings from their defaults by adding and defining them in the /etc/openshift/node.conf file.

Copy to Clipboard Toggle word wrap

BZ#1112445

Due to a bug in the Watchman Gear State plug-in, idled applications could not be properly stopped. This bug fix updates the Gear State plug-in to unidle an application's front end before stopping to ensure the proper final state. As a result, idled applications can now be properly stopped.

Copy to Clipboard Toggle word wrap

Management Console

BZ#1111419

The Management Console contained a typo when referring to the client tools option for creating a scalable application. This bug fix updates the Management Console, and the correct client tools option, --scaling, is now shown.

Copy to Clipboard Toggle word wrap