Bug 1411738

Summary:	Please update tomcat to >= 7.0.70 to fix ASF Bugzilla – Bug 59619
Product:	Red Hat Enterprise Linux 7	Reporter:	Miska Husgafvel <miska.husgafvel>
Component:	tomcat	Assignee:	Coty Sutherland <csutherl>
Status:	CLOSED ERRATA	QA Contact:	tomcat-qe
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	mbabacek
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 23:16:34 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:	1414895
Bug Blocks:	1414894

Description Miska Husgafvel 2017-01-10 12:08:08 UTC

Description of problem:

I have a Shibboleth IdP installation on CentOS Linux release 7.3.1611 (Core). After updating tomcat from 7.0.54-8.el7_2 to 7.0.69-10.el7 I started experiencing the issue described in https://bz.apache.org/bugzilla/show_bug.cgi?id=59619 . According to the bug report in ASF Bugzilla the issue is fixed in version >= 7.0.70. Would it be possible to update tomcat to version >= 7.0.70?


Version-Release number of selected component (if applicable): 7.0.69-10.el7


How reproducible:
Not reproducible trivially, requires installation and configuration of Shibboleth IdP.


Steps to Reproduce:
1. yum install tomcat
2. Install and configure Shibboleth IdP
3. systemctl start tomcat.service


Actual results:

Tomcat fails to start Shibboleth IdP container.


Expected results:

Shibboleth IdP container starts.

Comment 6 errata-xmlrpc 2017-08-01 23:16:34 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://access.redhat.com/errata/RHSA-2017:2247