2.2. Notable Technical Changes

OpenShift Enterprise 2.2 includes the following notable technical changes:
New OpenShift Enterprise 2.2 Channels

Distinct channels have been created for OpenShift Enterprise 2.2 for both RHN Classic and Red Hat Subscription Management. See the OpenShift Enterprise Deployment Guide [1] for an updated list of channel names and for more information on available repositories.

Default Front-end Server Proxy Plug-in

Starting with OpenShift Enterprise 2.2, the apache-mod-rewrite front-end server proxy plug-in is deprecated. New deployments of OpenShift Enterprise 2.2 now use the apache-vhost plug-in as the default.

Important

Any new nodes added to your deployment after an upgrade to 2.2 will use the apache-vhost plug-in by default. The apache-mod-rewrite plug-in is incompatible with the apache-vhost plug-in, and the front-end server configuration on all nodes across a deployment must be consistent. See the OpenShift Enterprise Deployment Guide for more information on upgrading from 2.1 to 2.2.
If your OpenShift Enterprise 2.1 deployment was configured to use the apache-mod-rewrite plug-in before starting the 2.2 upgrade, you can optionally allow the ose-upgrade tool to migrate your node hosts to the apache-vhost plug-in while upgrading to 2.2. The default behavior of the ose-upgrade tool, however, is to leave the apache-mod-rewrite plug-in in place, if installed. See the OpenShift Enterprise Deployment Guide for more information.
Rsyslog7 Packages

OpenShift Enterprise (OSE) 2.1 was originally released on Red Hat Enterprise Linux (RHEL) 6.5. In order for the mmopenshift plug-in to work, the rsyslog7 package from RHEL 7 was shipped in the OSE 2.1 channel. Later, RHEL 6.6 shipped its own rsyslog7 package that was incompatible with the one from OSE. This created many edge cases for RPM conflicts and confusing configurations.

This release updates the rsyslog7-mmopenshift package for compatibility with RHEL 6.6. The openshift.sh installation script and the ose-upgrade tool used for upgrading from 2.1 to 2.2 have been updated to handle the configuration changes as well. The rsyslog7 package from RHEL 6.6 conflicts with the base rsyslog package. A manual upgrade can be done with the following steps: 
# cp -f /etc/rsyslog7.d/* /etc/rsyslog.d/

# yum shell --disableplugin=priorities -y <<YUM
# erase rsyslog rsyslog7-7.4.7 rsyslog7-mmopenshift-7.4.7
# install rsyslog7 rsyslog7-mmopenshift
# transaction run
# YUM

# sed -i 's/rsyslog7.d/rsyslog.d/' /etc/rsyslog.conf
# service rsyslog start