Alexandre, I had the same problem. The root cause was that the server
directive in the client's puppet.conf did not match the hostname that
was used in the puppetmaster certificate. Check your puppetmaster
certificate with sudo puppetmaster -p puppetmaster (where
puppetmaster is the hostname of
Maverick has 2.6.1 which contains this upstream fix.
** Changed in: puppet (Ubuntu)
Status: Triaged = Fix Released
--
undefined method `closed?' for nil:NilClass when signing certificate
https://bugs.launchpad.net/bugs/613671
You received this bug notification because you are a member of
puppet 0.25.4-2ubuntu6
--
undefined method `closed?' for nil:NilClass when signing certificate
https://bugs.launchpad.net/bugs/613671
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in ubuntu.
--
Ubuntu-server-bugs mailing list
Could you please include what version of the package you're running?
** Changed in: puppet (Ubuntu)
Importance: Undecided = Medium
** Changed in: puppet (Ubuntu)
Status: New = Triaged
--
undefined method `closed?' for nil:NilClass when signing certificate
