Bug 1394328

Summary:	[RFE] EWS 2 cartridge should be able to use EWS 3 binaries.
Product:	OpenShift Container Platform	Reporter:	Eric Rich <erich>
Component:	ImageStreams	Assignee:	Timothy Williams <tiwillia>
Status:	CLOSED ERRATA	QA Contact:	Gaoyun Pei <gpei>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	2.2.0	CC:	adellape, aos-bugs, erich, gpei, jialiu, jokerman, mmccomas, rthrashe, tiwillia
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: EWS Tomcat 7 can now be configured on nodes to use either EWS 2 or EWS 3 channels, allowing an administrator an option on what EWS version they EWS 2 cartridge deploys. Reason: This option was enabled to allow administrators to take advantage of the EWS 3 life cycle and security / bug updates that it receives compared to the maintenance life cycle that EWS 2 is currently receiving. Result: Administrators have options, or can mix and match EWS versions (with node profiles) on what Tomcat version is installed when an EWS 2 cartridge is created.	Story Points:	---
Clone Of:
Clones:	1394396 (view as bug list)		Environment:
Last Closed:	2017-01-04 20:23:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1394396, 1461189

Description Eric Rich 2016-11-11 17:54:17 UTC

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.

Comment 4 Alex Dellapenta 2016-11-23 22:06:07 UTC

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

Comment 6 Gaoyun Pei 2016-12-14 05:57:26 UTC

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

Comment 8 errata-xmlrpc 2017-01-04 20:23:18 UTC

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