Red Hat OpenShift Enterprise release 2.2.1 is now available with updates topackages that fix several bugs and introduce a feature enhancement.

OpenShift Enterprise by Red Hat is the company’s cloud computingPlatform-as-a-Service (PaaS) solution designed for on-premise or private clouddeployments.This update fixes the following bugs:* During application or gear restarts, the MongoDB cartridge did not ensure thatusers could authenticate to MongoDB prior to reporting a successful connection.As a result, applications that made use of MongoDB could attempt to connect toMongoDB before it was finished initializing, causing a “command denied” error.This bug fix updates the MongoDB cartridge, and now applications that make useof MongoDB wait until MongoDB is fully initialized before attempting to connect.After applying this fix, a cartridge upgrade is required. (BZ#1156106)* Previously, the jenkins-plugin-openshift package did not require the wgetpackage. When the jenkins-plugin-openshift package was installed using a methodthat did not require wget, such as Puppet, this caused the Jenkins plug-in tofail to retrieve remote resources due to the missing wget package, and Jenkinsbuilds failed as a result. This bug fix updates the jenkins-plugin-openshiftpackage to add the wget package as a dependency, and Jenkins builds now triggerproperly regardless of the installation method. (BZ#1161372)* When Red Hat Enterprise Linux (RHEL) Server 6.6 was released, the ose-upgradetool required an update for compatibility with the latest subscription-managerRPM package. Because the ose-upgrade tool ships with theopenshift-enterprise-release package, adding the dependency in that packagecauses problems for administrators that maintain their own stream of RHEL 6.This bug fix updates the openshift-enterprise-release package to remove theexplicit dependency on the subscription-manager package. As a result, theose-upgrade tool now works with all RHEL 6 versions of the subscription-managerpackage. (BZ#1163500)* A race condition existed between destroy-app and configure actions for thesame application. When the configure action timed out in MCollective and thebroker tried to destroy the application, it was possible for artifacts to beleft behind in apache-vhost configuration files. As a result, applications couldbecome unreachable. This bug fix updates the apache-vhost front-end serverplug-in to verify whether the directory exists before configuring apache-vhostconfiguration files, and the artifacts are no longer left behind. (BZ#1157643)This update also adds the following enhancement:* Previously in the apache-vhost front-end server plug-in, theSSLCertificateChainFile setting in the frontend-vhost-https-template.erb filewas set to the same value as the SSLCertificateFile setting. This enhancementupdates the plug-in so that SSLCertificateChainFile is a configurable setting.As part of this enhancement, the following new configuration parameters havebeen added to the /etc/openshift/node.conf file on node hosts, which use thefollowing default values when undefined:OPENSHIFT_DEFAULT_SSL_KEY_PATH=”/etc/pki/tls/private/localhost.key”OPENSHIFT_DEFAULT_SSL_CRT_PATH=”/etc/pki/tls/certs/localhost.crt”OPENSHIFT_DEFAULT_SSL_CRT_CHAIN_PATH=”/etc/pki/tls/certs/localhost.crt”(BZ#1160300)All OpenShift Enterprise users are advised to upgrade to these updated packages.
Red Hat OpenShift Enterprise 2

SRPMS:
jenkins-plugin-openshift-0.6.40.2-0.el6op.src.rpm
    MD5: 65169f8928ec599b0c95fdb8339ad8f0SHA-256: 73b57d0f8277e459e758104d214fd758aba9ac61e0a7d8076dafae3d237d4bab
openshift-enterprise-upgrade-2.2.1-1.el6op.src.rpm
    MD5: 06bd7b7031f587be21ebd95067cb6aedSHA-256: f726d82538dfa6af34806a76d7e573326d45b49312a9ba74601c419c1c37dac2
openshift-origin-cartridge-mongodb-1.23.2.2-1.el6op.src.rpm
    MD5: 80689a0f39f0b7bb294d2f118c17aa12SHA-256: 9772e6da812370535699354810443a7f470680602574eaade679dde22eb5075b
rubygem-openshift-origin-frontend-apache-vhost-0.10.1.4-1.el6op.src.rpm
    MD5: c3649ba3d227fe611344673e58470741SHA-256: f5a4a89d805c2df8f55fc19f152e8ca7cc76471e42100a45db2aae7e43a57bcf
rubygem-openshift-origin-node-1.31.3.7-1.el6op.src.rpm
    MD5: 58302e539e8cbba52b8e9f90787d7731SHA-256: 4fbdeef00415c98c23b6b08bef62001363e32b34de60a535f2e576b86d54a20f
 
x86_64:
jenkins-plugin-openshift-0.6.40.2-0.el6op.x86_64.rpm
    MD5: e303a779fc57fe7ff43c63e6005d45c7SHA-256: 78aa4142bd0bc42b8ebf305cd28f554f3064ddf383edba0944e8de7746396c80
openshift-enterprise-release-2.2.1-1.el6op.noarch.rpm
    MD5: a4edee6d8ebf8679a954b44b5c44c08aSHA-256: a80f80806f63acb59cbd44e8c68dedaa45880d8dcaa244083edfdbb5cd006e8d
openshift-enterprise-upgrade-broker-2.2.1-1.el6op.noarch.rpm
    MD5: f5280aba7cbef69041b470ba330e00c4SHA-256: 44f2806e0961f86db8dfe9b4befa60f066aded0000e321daf355a7f27de5d980
openshift-enterprise-upgrade-node-2.2.1-1.el6op.noarch.rpm
    MD5: 65627ac16a14ef24f6a4969105b63285SHA-256: 2d39b24a4e6bd35ede90d831ad7c42a139e750e5346830d30647f0f984cf084f
openshift-enterprise-yum-validator-2.2.1-1.el6op.noarch.rpm
    MD5: c1f2ac74595e3528e7151a2ad7c6683eSHA-256: 09d1c1fd07aab0d71b7772c0f3bfda0abbfebe99f0f50c7685c725010fd516ef
openshift-origin-cartridge-mongodb-1.23.2.2-1.el6op.noarch.rpm
    MD5: 47ca5470affbf5860f36c005fc1d5997SHA-256: c7a44120f71362d880b2ac8be282f080d1af9849a6e08962e10dce1d820d1ae1
rubygem-openshift-origin-frontend-apache-vhost-0.10.1.4-1.el6op.noarch.rpm
    MD5: 44e577e1f072d6e253f113976d7224b4SHA-256: b9251c8c919604a7ec8633d6241dbb87c1db7db7064700ebb840b8807d601dfe
rubygem-openshift-origin-node-1.31.3.7-1.el6op.noarch.rpm
    MD5: 1e9c3d561197833d99a12a52cf643496SHA-256: 05a5a45dc2d3b4f3db35b2965d3da24b64514b4dfb4af04fc9961e6689723fb2
 
(The unlinked packages above are only available from the Red Hat Network)
1156106 – MongoDB failed to make an initial connection when the cartridge restarts1157643 – Race condition between destroy-app and configure leaves broken vhost conf1160300 – make the default crt/key/chain file to be configurable in vhost template1161372 – Can not trigger jenkins build due to lack of wget package1163500 – Remove explicit dependency on RHEL 6.6’s subscription-manager package

These packages are GPG signed by Red Hat for security. Our key and
details on how to verify the signature are available from:

Leave a Reply