Description of problem: Due to security issues with the EWS 2 product, the EWS cartridge should have the ability to use EWS 3 binaries, and start a Tomcat 7 instance using the RPMS provided by the EWS 3 channels (with out update to the EWS 2 cartridge). This should be a documented and supported product feature.
Documentation updates for this issue were published this afternoon: https://access.redhat.com/documentation/en-US/OpenShift_Enterprise/2/html-single/2.2_Release_Notes/index.html#appe-Revision_History https://access.redhat.com/documentation/en-US/OpenShift_Enterprise/2/html-single/Deployment_Guide/index.html#appe-Revision_History https://access.redhat.com/documentation/en-US/OpenShift_Enterprise/2/html-single/Administration_Guide/index.html#appe-Revision_History
Verify this bug with puddle 2.2/2016-12-12.1 1. Create one jbossews-2.0 app, make sure it's available [root@broker ~]# rhc app-create jbewstest jbossews-2.0 [root@broker ~]# curl -I http://jbewstest-yes.ose22-auto.com.cn/ HTTP/1.1 200 OK 2. Update tomcat7 package on all nodes [root@node1 ~]# yum update tomcat7 --disablerepo=* --enablerepo=jws-3-for-rhel-6-server-rpms Loaded plugins: priorities, product-id, search-disabled-repos, security, subscription-manager Setting up Update Process jws-3-for-rhel-6-server-rpms | 4.0 kB 00:00 Resolving Dependencies --> Running transaction check ---> Package tomcat7.noarch 0:7.0.54-23_patch_05.ep6.el6 will be updated ---> Package tomcat7.noarch 0:7.0.59-51_patch_01.ep7.el6 will be an update --> Processing Dependency: tomcat7-lib = 7.0.59-51_patch_01.ep7.el6 for package: tomcat7-7.0.59-51_patch_01.ep7.el6.noarch --> Running transaction check ---> Package tomcat7-lib.noarch 0:7.0.54-23_patch_05.ep6.el6 will be updated ---> Package tomcat7-lib.noarch 0:7.0.59-51_patch_01.ep7.el6 will be an update --> Processing Dependency: tomcat7-el-2.2-api = 7.0.59-51_patch_01.ep7.el6 for package: tomcat7-lib-7.0.59-51_patch_01.ep7.el6.noarch --> Processing Dependency: tomcat7-jsp-2.2-api = 7.0.59-51_patch_01.ep7.el6 for package: tomcat7-lib-7.0.59-51_patch_01.ep7.el6.noarch --> Processing Dependency: tomcat7-servlet-3.0-api = 7.0.59-51_patch_01.ep7.el6 for package: tomcat7-lib-7.0.59-51_patch_01.ep7.el6.noarch --> Processing Dependency: apache-commons-collections-tomcat-eap6 >= 3.2.1-18 for package: tomcat7-lib-7.0.59-51_patch_01.ep7.el6.noarch --> Running transaction check ---> Package apache-commons-collections-tomcat-eap6.noarch 0:3.2.1-15.redhat_3.1.ep6.el6 will be updated ---> Package apache-commons-collections-tomcat-eap6.noarch 0:3.2.1-18.redhat_7.1.ep6.el6 will be an update ---> Package tomcat7-el-2.2-api.noarch 0:7.0.54-23_patch_05.ep6.el6 will be updated ---> Package tomcat7-el-2.2-api.noarch 0:7.0.59-51_patch_01.ep7.el6 will be an update ---> Package tomcat7-jsp-2.2-api.noarch 0:7.0.54-23_patch_05.ep6.el6 will be updated ---> Package tomcat7-jsp-2.2-api.noarch 0:7.0.59-51_patch_01.ep7.el6 will be an update ---> Package tomcat7-servlet-3.0-api.noarch 0:7.0.54-23_patch_05.ep6.el6 will be updated ---> Package tomcat7-servlet-3.0-api.noarch 0:7.0.59-51_patch_01.ep7.el6 will be an update --> Finished Dependency Resolution Dependencies Resolved ============================================================================================================================================================================= Package Arch Version Repository Size ============================================================================================================================================================================= Updating: tomcat7 noarch 7.0.59-51_patch_01.ep7.el6 jws-3-for-rhel-6-server-rpms 137 k Updating for dependencies: apache-commons-collections-tomcat-eap6 noarch 3.2.1-18.redhat_7.1.ep6.el6 jws-3-for-rhel-6-server-rpms 22 k tomcat7-el-2.2-api noarch 7.0.59-51_patch_01.ep7.el6 jws-3-for-rhel-6-server-rpms 51 k tomcat7-jsp-2.2-api noarch 7.0.59-51_patch_01.ep7.el6 jws-3-for-rhel-6-server-rpms 80 k tomcat7-lib noarch 7.0.59-51_patch_01.ep7.el6 jws-3-for-rhel-6-server-rpms 2.6 M tomcat7-servlet-3.0-api noarch 7.0.59-51_patch_01.ep7.el6 jws-3-for-rhel-6-server-rpms 184 k ... 3. Restart the app and access it again [root@broker ~]# rhc app-restart jbewstest RESULT: jbewstest restarted [root@broker ~]# curl -I http://jbewstest-yes.ose22-auto.com.cn/ HTTP/1.1 200 OK 4. Create a new jbossews-2.0 application and visit the app [root@broker ~]# rhc app-create jbewstest2 jbossews-2.0 [root@broker ~]# curl -I http://jbewstest2-yes.ose22-auto.com.cn/ HTTP/1.1 200 OK
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0017.html