Fixed, the manifests and configs were copied from our production puppet server and the buckets is still pointing to it, :)
On Wed, Mar 31, 2010 at 7:38 AM, James Cammarata <[email protected]> wrote: > > On Wed, 31 Mar 2010 06:59:07 +0800, pinoyskull <[email protected]> > wrote: >> Cant seem to fix this problem, need help >> >> --- >> Tue Mar 30 11:21:17 +0000 2010 //yumconf/File[/etc/hosts] (debug): >> Creating checksum {md5}0eea71665fb6890c06421fd13aa3f849 >> Tue Mar 30 11:21:17 +0000 2010 >> //yumconf/File[/etc/yum.repos.d/CentOS-Base.repo]/checksum (debug): >> Initializing checksum hash >> Tue Mar 30 11:21:17 +0000 2010 >> //yumconf/File[/etc/yum.repos.d/CentOS-Base.repo] (debug): Creating >> checksum {md5}2b7901ec0211cf889f52cc30e10e49ab >> Tue Mar 30 11:21:17 +0000 2010 >> //yumconf/File[/etc/yum.repos.d/CentOS-Base.repo] (debug): Changing >> content >> Tue Mar 30 11:21:17 +0000 2010 >> //yumconf/File[/etc/yum.repos.d/CentOS-Base.repo] (debug): 1 change(s) >> Tue Mar 30 11:21:17 +0000 2010 >> //yumconf/File[/etc/yum.repos.d/CentOS-Base.repo]/content (err): >> change from {md5}2b7901ec0211cf889f52cc30e10e49ab to >> {md5}fbe55e9468d5b1605fcc17c71614b7d5 failed: Certificates were not >> trusted: certificate verify failed >> Tue Mar 30 11:21:17 +0000 2010 //yumconf/File[/etc/yum.conf]/checksum >> (debug): Initializing checksum hash >> Tue Mar 30 11:21:17 +0000 2010 //yumconf/File[/etc/yum.conf] (debug): >> Creating checksum {md5}1c7caff42d5751bc8d1b23cab946b45e >> Tue Mar 30 11:21:17 +0000 2010 //yumconf/File[/etc/yum.conf] (debug): >> Changing source >> Tue Mar 30 11:21:17 +0000 2010 //yumconf/File[/etc/yum.conf] (debug): >> 1 change(s) >> Tue Mar 30 11:21:17 +0000 2010 //yumconf/File[/etc/yum.conf]/source >> (err): change from {md5}c4e9d839f2019ff8df96daf72a74a9c3 to >> puppet:///general/yum.conf failed: Certificates were not trusted: >> certificate verify failed >> --- > > I had this exact same problem when I had copied my configs from one > environment to another. Turned out I had manually set the filebucket > server in my config, so my new servers were trying to filebucket to my old > environment, thus the cert mismatch. > > Beyond that, every example of this error I could google said that it was > DNS related. > > -- > 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. > > -- 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.
