dogtag-pki stops working with resteasy newer than 3.0.19-2

Bug #1682149 reported by Łukasz Zemczak on 2017-04-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dogtag-pki (Ubuntu)
resteasy (Ubuntu)
resteasy3.0 (Ubuntu)

Bug Description

With the new resteasy package, dogtag-pki is unable to spawn a CA instance (e.g. pkispawn -s CA) because of the /ca/rest/installer/configure REST endpoint being unavailable. This can be either a regression in resteasy itself or maybe dogtag-pki needs to be somehow updated.

This is also an issue noticed in Debian:

The error can be seen during dogtag-pki autopkgtest runs with the latest resteasy package. The original error message doesn't say much, but tracking it down resulted in this exception being sent out during spawning the configuration scriptlet:

requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://autopkgtest:8443/ca/rest/installer/configure

Łukasz Zemczak (sil2100) wrote :

If anyone is interested, a failed autopkgtest log link can be found below - but as mentioned already, the original error message doesn't say much as it was not meant to handle 404 errors (and breaks during printing the error log).

Changed in dogtag-pki (Ubuntu):
status: New → Confirmed
Łukasz Zemczak (sil2100) wrote :

For now Adam decided to remove the -proposed resteasy version.

Timo Aaltonen (tjaalton) wrote :

yep, well known:

but even after this the bigger issue is getting dogtag/tomcatjss ported to tomcat 8.5:

not sure it'll happen for 17.10 either..

Timo Aaltonen (tjaalton) wrote :

It's clear that even dogtag 10.6.0 doesn't work with resteasy 3.1, so either resteasy3.0 needs to stay in bionic, or src:resteasy will be reverted to 3.0.19.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers