[Pkg-puppet-devel] autopkgtest issues in Ubuntu
Apollon Oikonomopoulos
apoikos at debian.org
Fri Feb 24 09:48:45 UTC 2017
Hi Nish,
On 13:48 Thu 23 Feb , Nish Aravamudan wrote:
> Ok, so adding ca-certificates did not seem to make any difference (and
> in fact, it seems like it is already installed in the Ubuntu autopkgtest
> environment so that was a red herring anyways). Any ideas why, e.g.:
Puppet has its own CA system and does not rely on ca-certificates on any
way, so having ca-certificates installed or not should not make a
difference.
>
> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty-nacc-lp1570472/zesty/amd64/p/puppet/20170223_203421_4dd8e@/log.gz
>
> there is no certificate for the hostname by default on Ubuntu but there
> is on Debian? I don't see anything in the tests that ensure it exists
> and only puppet-master-passenger generates it in a postinst (hence those
> tests now pass, but I think it's technically incidental and dependent on
> the .postinst's behavior, which might be fine).
The certificate should have been generated by the master process itself
if it does not exist, using Puppet's CA. Could you get the list of files
under /var/lib/puppet/ssl and /var/cache/puppet/ssl at the end of the
test?
Thanks,
Apollon
More information about the Pkg-puppet-devel
mailing list