Bug 1471893

Summary:	[RFE] Tomcat exact version in label for jboss-webserver-3/webserver31-tomcat7-openshift image
Product:	[JBoss] JBoss Enterprise Web Server 2	Reporter:	Vladislav Walek <vwalek>
Component:	tomcat7	Assignee:	Coty Sutherland <csutherl>
Status:	CLOSED WONTFIX	QA Contact:	Michal Karm Babacek <mbabacek>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.0.0	CC:	aos-bugs, jdoyle, jokerman, mmccomas, pslavice, pweil, rsvoboda, sspeiche
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-30 15:31:51 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:

Description Vladislav Walek 2017-07-17 15:26:41 UTC

Description of problem:

Could you please attach to the image label which shows the exact version of Tomcat7, which is included in image? 
Customer can't see the version unless running the image. Then it is visible in logs.
This info is useful for production planning.

Version-Release number of selected component (if applicable):
OpenShift Container Platfrom 3.5
jboss-webserver-3/webserver31-tomcat7-openshift:latest

Comment 1 kconner 2017-07-19 13:46:54 UTC

The information is present in the images through their environment variables, it should be possible to query this from the command line.

For examples:

docker inspect registry.access.redhat.com/jboss-webserver-3/webserver31-tomcat7-openshift | egrep 'PRODUCT_VERSION|JBOSS_WEBSERVER_VERSION'

would result in

                "JBOSS_WEBSERVER_VERSION=3.1.0",
                "PRODUCT_VERSION=3.1.0",
                "JBOSS_WEBSERVER_VERSION=3.1.0",
                "PRODUCT_VERSION=3.1.0",

Comment 2 kconner 2017-07-19 13:49:12 UTC

P.S. All the xPaaS images should contain PRODUCT_VERSION but the other variable will differ depending on the product, e.g. the eap variable would be JBOSS_EAP_VERSION.

Comment 3 kconner 2017-07-19 13:53:06 UTC

Apologies, I've just realised you were asking about the Tomcat version, not the actual product version.  I'll see what can be done about this.

Comment 4 kconner 2017-07-19 15:19:22 UTC

While we look into this issue you could advise them to do the following as a workaround.


docker run -it --rm registry.access.redhat.com/jboss-webserver-3/webserver31-tomcat7-openshift java -cp /opt/webserver/lib/catalina.jar org.apache.catalina.util.ServerInfo

This will display output similar to the following

Server version: Apache Tomcat/7.0.70
Server built:   Jan 12 2017 14:59:11 UTC
Server number:  7.0.70-16.ep7.el7.0
OS Name:        Linux
OS Version:     3.10.0-514.26.2.el7.x86_64
Architecture:   amd64
JVM Version:    1.8.0_131-b12
JVM Vendor:     Oracle Corporation

Comment 5 kconner 2017-07-19 15:19:23 UTC

While we look into this issue you could advise them to do the following as a workaround.


docker run -it --rm registry.access.redhat.com/jboss-webserver-3/webserver31-tomcat7-openshift java -cp /opt/webserver/lib/catalina.jar org.apache.catalina.util.ServerInfo

This will display output similar to the following

Server version: Apache Tomcat/7.0.70
Server built:   Jan 12 2017 14:59:11 UTC
Server number:  7.0.70-16.ep7.el7.0
OS Name:        Linux
OS Version:     3.10.0-514.26.2.el7.x86_64
Architecture:   amd64
JVM Version:    1.8.0_131-b12
JVM Vendor:     Oracle Corporation

Comment 6 Steve Speicher 2018-07-30 14:10:39 UTC

Reassigning to JWS/tomcat team