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

Bug #1682149 reported by Łukasz Zemczak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dogtag-pki (Ubuntu)
Fix Released
Undecided
Unassigned
resteasy (Ubuntu)
Won't Fix
Undecided
Unassigned
resteasy3.0 (Ubuntu)
Fix Released
Undecided
Unassigned

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:
https://anonscm.debian.org/cgit/pkg-freeipa/dogtag-pki.git/commit/?id=2378d68da68f79719e884bd72766e7b2ddc6fcfc

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

Tags: zesty
Revision history for this message
Ł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).

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/d/dogtag-pki/20170329_083759_02353@/log.gz

Changed in dogtag-pki (Ubuntu):
status: New → Confirmed
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

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

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

yep, well known:

https://pagure.io/dogtagpki/issue/2596

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

https://pagure.io/tomcatjss/issue/1
https://pagure.io/tomcatjss/issue/3
https://pagure.io/dogtagpki/issue/2560

not sure it'll happen for 17.10 either..

Revision history for this message
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.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

this was resolved by packaging a separate resteasy3.0

Changed in dogtag-pki (Ubuntu):
status: Confirmed → Fix Released
Changed in resteasy3.0 (Ubuntu):
status: New → Fix Released
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

and upstream probably won't move to a newer resteasy base

Changed in resteasy (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.