Chapter 17. RHBA-2014:0102 - OpenShift Enterprise 2.0.2 Bug Fix and Enhancement Update

Broker

BZ#1049566

Routing SPI messages are now updated to include gear UUIDs, which allows administrators to address specific gears within an application. This is useful, for example, for adding dynamic DNS entries or adding gears to a load balancing pool. These updates, along with other changes pertaining to the sample ActiveMQ routing plug-in, are now documented in the OpenShift Enterprise Deployment Guide.

BZ#1048943

The oo-admin-ctl-user tool would only allow administrators to edit user information for one user at a time. This has been fixed and administrators can now update user information for multiple users at a time. See the OpenShift Enterprise Administration Guide for more information on how to use the oo-admin-ctl-user tool.

BZ#1017656

Users experienced failures when attempting to create multiple domains in the Management Console because a required method was missing from the code base. This issue has been fixed and users are now able to create multiple domains with the Management Console.

BZ#1049741

When users clicked “Share this link” while creating a new application with a custom cartridge manifest in the Management Console, a name in the “Public URL” field was generated that incorrectly included the suffix from the URL or path of the manifest. This issue has been fixed so that suggested names are generated without these suffixes.

BZ#1050179

The page title for the OpenShift Enterprise Administration Console was incorrectly labeled OpenShift Origin. This has been fixed and the correct product name is now displayed.

BZ#1038558

When creating domains in the Management Console, the invalid input field was highlighted when an invalid domain name was specified. However, the corresponding error message was not highlighted, causing confusion for users because the error was not immediately recognized. This has been fixed and the corresponding error message is now highlighted when an invalid domain name is specified.

BZ#1034647

Invalid UTF-8 characters were accepted as values for environment variables, causing errors during operations that utilized those variables. The input validation for environment variables that are configured by users now includes UTF-8 encoding, and as a result invalid UTF-8 characters are now rejected.

Node

BZ#1033146

The MAVEN_ARGS environment variable could not be set with JBoss EWS cartridges because it would reset to the default value of the cartridge when application changes were pushed. This fix updates the build script for the JBoss EWS cartridge so that the default value of the cartridge is only used if MAVEN_ARGS is not defined. If it is defined, the user configuration is used.

BZ#1047440

Jenkins builds could not access the ./perl/perl5lib/lib/perl5/ directory due to missing symlinks in the managed_files.yml file of the Perl cartridge. This fix adds the required symlinks to the managed_files.yml file so that new applications that are deployed with the updated Perl cartridge are correctly built in Jenkins. Note that the ruby193-mcollective service must be restarted on node hosts after applying this fix.

BZ#1032920

The Python cartridge included files and directories from the upstream community cartridge that were not applicable to OpenShift Enterprise. The unnecessary community files and directories have been removed from the current version of the Python cartridge.

BZ#998995

When a cartridge was installed with the oo-admin-cartridge tool, the SELinux contexts were preserved on files installed with the cartridge instead of being set to the appropriate context for the install destination. This caused a mismatch between broker and node hosts because the cartridge list was not updated correctly on node hosts. This issue has been fixed and the SELinux contexts are now set correctly, allowing the cartridge list to be correctly updated, and the mismatch between broker and node hosts no longer occurs.

BZ#1048952

While logged into a gear, if a file was edited with vim, vim would attempt to write to the ~/.viminfo file. However, users would receive an error message because they did not have write permissions to that file. This fix points the .vimrc file to ~/data/.viminfo, and this error message no longer occurs because users are able to write to that file.