#2596 Port to resteasy 3.1.0
Closed: migrated 3 years ago by dmoluguw. Opened 7 years ago by tjaalton.

Resteasy 3.1.0 moved ClientResponseType to resteasy-legacy.jar, so dogtag needs to either use something else or use the legacy jar.


I don't know if that patch is enough, but at least it builds now.

this patch is not enough, pkispawn still fails with just

Log file: /var/log/pki/pki-ca-spawn.20170217194720.log
Loading deployment configuration from /tmp/pkispawn.config.
Installing CA into /var/lib/pki/pki-tomcat.
Storing deployment configuration into /etc/dogtag/tomcat/pki-tomcat/ca/deployment.cfg.
[ ok ] Starting pki-tomcatd (via systemctl): pki-tomcatd.service.

Installation failed:
Traceback (most recent call last):
File "/usr/sbin/pkispawn", line 817, in <module>
main(sys.argv)
File "/usr/sbin/pkispawn", line 535, in main
if r.headers['content-type'] == 'application/json':
File "/usr/lib/python2.7/dist-packages/requests/structures.py", line 54, in getitem
return self._store[key.lower()][1]
KeyError: 'content-type'

and nothing in the logs that I could find relevant

According to tjaalton this problem affects Debian testing (9.0 to be) and unstable, and Ubuntu 17.04.

Fedora/RHEL is still using Resteasy 3.0.x.

Metadata Update from @tjaalton:
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

7 years ago

Moving to 10.4 critical for now although this will probably not be addressed immediately.

Metadata Update from @mharmsen:
- Custom field feature adjusted to ''
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: None
- Issue priority set to: critical
- Issue set to the milestone: 10.4 (was: 0.0 NEEDS_TRIAGE)

6 years ago

Per CS/DS meeting of 04/24/2017: 10.5 critical

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.4)

6 years ago

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

6 years ago

[20171025] - Offline Triage ==> 10.6

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

6 years ago

I see 10.5 was recently released. When is 10.6 expected to come out? Feature freeze of Ubuntu 18.04 is in 2018-03-01: https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule

So having this and https://pagure.io/dogtagpki/issue/2560 fixed by that date would help to ensure 18.04 LTS would still ship freeipa server.

use-resteasy-legacy.diff

Here's a slightly updated version of the patch. Pkispawn now fails with this:

Installation failed:
<!DOCTYPE html><html><head><title>Apache Tomcat/8.0.46 (Debian) - Error report</title><style type="text/css">H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}.line {height: 1px; background-color: #525D76; border: none;}</style> </head><body>

HTTP Status 500 - Servlet execution threw an exception

type Exception report

message <u>Servlet execution threw an exception</u>

description <u>The server encountered an internal error that prevented it from fulfilling this request.</u>

exception

javax.servlet.ServletException: Servlet execution threw an exception
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

root cause

java.lang.AbstractMethodError: javax.ws.rs.core.Response$ResponseBuilder.status(ILjava/lang/String;)Ljavax/ws/rs/core/Response$ResponseBuilder;
javax.ws.rs.core.Response$ResponseBuilder.status(Response.java:921)
javax.ws.rs.core.Response.status(Response.java:592)
javax.ws.rs.core.Response.status(Response.java:603)
javax.ws.rs.core.Response.ok(Response.java:638)
javax.ws.rs.core.Response.ok(Response.java:650)
org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:353)
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:248)
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:235)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:402)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209)
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:227)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

note <u>The full stack trace of the root cause is available in the Apache Tomcat/8.0.46 (Debian) logs.</u>


Apache Tomcat/8.0.46 (Debian)

</body></html>

Please check the CA logs in /var/log/pki/pki-tomcat/ca.

The code doesn't use ClientResponseType anymore, but it still uses RESTEasy 3.0.

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2716

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata
Attachments 1
Attached 6 years ago View Comment