Hi, Debian updated resteasy to 3.1.0 and it broke dogtag. I filed a ticket(*) and attached a patch to fix the build, but pkispawn still fails: root@zesty:~# pkispawn -f /tmp/pkispawn.config Subsystem (CA/KRA/OCSP/TKS/TPS) [CA]: Begin installation (Yes/No/Quit)? yes 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' The last thing in pki-ca-spawn logfile is: 2017-02-17 19:47:23 pkispawn : INFO ....... executing '/etc/init.d/pki-tomcatd start pki-tomcat' 2017-02-17 19:47:30 pkispawn : DEBUG ........... <?xml version="1.0" encoding="UTF-8"?><XMLResponse><State>0</State><Type>CA</Type><Status>running</Status><Version>10.3.5+12</Version></XMLResponse> 2017-02-17 19:47:31 pkispawn : INFO ....... constructing PKI configuration data. 2017-02-17 19:47:31 pkispawn : INFO ....... executing 'certutil -R -d /root/.dogtag/pki-tomcat/ca/alias -s cn=PKI Administrator,e=caadmin@tyrell,ou=pki-tomcat,o=tyrell Security Domain -k rsa -g 2048 -z /root/.dogtag/pki-tomcat/ca/alias/noise -f /root/.dogtag/pki-tomcat/ca/password.conf -o /root/.dogtag/pki-tomcat/ca/alias/admin_pkcs10.bin' 2017-02-17 19:47:31 pkispawn : INFO ....... rm -f /root/.dogtag/pki-tomcat/ca/alias/noise 2017-02-17 19:47:31 pkispawn : INFO ....... BtoA /root/.dogtag/pki-tomcat/ca/alias/admin_pkcs10.bin /root/.dogtag/pki-tomcat/ca/alias/admin_pkcs10.bin.asc 2017-02-17 19:47:31 pkispawn : INFO ....... configuring PKI configuration data. The instance is running, and catalina.out looks pretty normal like when the instance isn't configured yet. So I'm stuck trying to figure out what's broken... Any ideas? * https://fedorahosted.org/pki/ticket/2596 -- t