On 2023-02-27 17:29:17, Bastian Blank wrote: > On Mon, Feb 27, 2023 at 10:14:33AM -0500, Jérôme Charaoui wrote: >> Unfortunately I'm unable to reproduce this issue. Is this a new puppetserver >> installation, or an upgrade from puppet-master 5.5? > > This is a new installation. > > However I found the reason. The hostname setup is incomplete. The > server considers the name for the certificate to be "debian-sid." and > uses files "debian-sid..crt" (aka it adds a trailing dot). > > The agent seems to be not that kind and tries to get a new certificate, > which fails as the CN is already in use.
Oh this is interesting. Is not having a FQDN even supported in Puppet? Maybe this could warrant a severity downgrade too... Seems like an edge case...