On Mon, 15 Feb 2010 00:24:10 -0600, James Cammarata <[email protected]> wrote: >> that is strange, I know that puppetd does not create certificates when >> running with --noop mode. Seems like it could be related. Does this > machine >> have a signed certificate? >> >> >>> Any ideas? >>> >> >> I would try running the following on the puppet server: >> >>>puppetca --list --all >> >> and make sure that the names of all of the certificates are what you >> expect. > > I don't know about that. I have checked with puppetca on the master before > running the first time (or after --clean) and --noop seems to be creating > the cert. It shows up after the first run when listing the certs, and the > FQDN matches.
This turned out to be user error. As I mentioned this is my sandbox environment, so I had copied the configs in from our development server. The issue was that I set the file bucket server in the main configuration, so my sandbox systems were trying to talk to our dev server to filebucket before replacing, thus the cert issues. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
