[Pkg-freeipa-devel] Bug#993534: 389-ds-base breaks dogtag-pki autopkgtest: CA spawn failed

Thu Sep 2 20:08:09 BST 2021

Source: 389-ds-base, dogtag-pki
Control: found -1 389-ds-base/1.4.4.16-1
Control: found -1 dogtag-pki/10.10.2-3
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian-ci at lists.debian.org
User: debian-ci at lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of 389-ds-base the autopkgtest of dogtag-pki fails
in testing when that autopkgtest is run with the binary packages of
389-ds-base from unstable. It passes when run with only packages from
testing. In tabular form:

                       pass            fail
389-ds-base            from testing    1.4.4.16-1
dogtag-pki             from testing    10.10.2-3
all others             from testing    from testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of 389-ds-base to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=389-ds-base

https://ci.debian.net/data/autopkgtest/testing/amd64/d/dogtag-pki/14986372/log.gz

autopkgtest [09:10:45]: test pkispawn: [-----------------------
>>>> IP address is 192.168.122.100
>>>> Hostname was:
>>>> /etc/hosts now has:
127.0.0.1	localhost
::1		localhost ip6-localhost ip6-loopback
ff02::1		ip6-allnodes
ff02::2		ip6-allrouters

192.168.122.100 autopkgtest.debci autopkgtest
Starting installation...
Completed installation for pki-tomcat
Notice: Trust flag u is set automatically if the private key is present.
/usr/lib/python3/dist-packages/urllib3/connection.py:455:
SubjectAltNameWarning: Certificate for autopkgtest.debci has no
`subjectAltName`, falling back to check for a `commonName` for now. This
feature is being removed by major browsers and deprecated by RFC 2818.
(See https://github.com/urllib3/urllib3/issues/497 for details.)
  warnings.warn(
Loading deployment configuration from debian/tests/deploy.cfg.
Installation log: /var/log/pki/pki-ca-spawn.20210902091106.log
Installing CA into /var/lib/pki/pki-tomcat.

Installation failed:
<!doctype html><html lang="en"><head><title>HTTP Status 404 – Not
Found</title><style type="text/css">body
{font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b
{color:white;background-color:#525D76;} h1 {font-size:22px;} h2
{font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a
{color:black;} .line
{height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP
Status 404 – Not Found</h1><hr class="line" /><p><b>Type</b> Status
Report</p><p><b>Message</b> The requested resource
[/ca/admin/ca/getStatus] is not
available</p><p><b>Description</b> The origin server did not find a
current representation for the target resource or is not willing to
disclose that one exists.</p><hr class="line" /><h3>Apache Tomcat/9.0.43
(Debian)</h3></body></html>

Please check the CA logs in /var/log/pki/pki-tomcat/ca.
>>>> CA spawn failed:
autopkgtest [09:12:24]: test pkispawn: -----------------------]

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-freeipa-devel/attachments/20210902/cbf242cd/attachment.sig>