Well, the good news is you're not crazy :)
I loaded up a 5.7 instance and puppet 2.7.9+ and got the same result as you!
I did a yum update and got the same issue - so it is not a common
issue that is already fixed.
I did a manual rpm --import of the key and the subsequent yum install
worked. It is clearly an OS issue particular to Jenkins rather than a
'puppet' issue (as Puppet installed via yum and installed the key
automagically without an issue).
What I did notice is that a copy of the key jenkins pubkey doesn't get
installed into /etc/pki. But you can query it via rpm -qa gpg-pubkey*:
rpm -qi gpg-pubkey-d50582e6-4a3feef6
So, you could use this to install from scratch:
class jenkins {
exec { "key_import":
command => "/bin/rpm --import
http://pkg.jenkins-ci.org/redhat/jenkins-ci.org.key";
onlyif => 'a test for the existence of rpm -qi
gpg-pubkey-d50582e6-4a3feef6 doesn't exist'
}
yumrepo { "jenkins":
baseurl => "http://pkg.jenkins-ci.org/redhat";,
descr => "Jenkins",
enabled => 1,
gpgcheck => 1,
gpgkey => "http://pkg.jenkins-ci.org/redhat/jenkins-ci.org.key";,
require => Exec["key_import"],
}
package {"jenkins": ensure => latest, require => Yumrepo["jenkins"] }
}
include jenkins
Normally what happens is that if it is 'assumed yes', yum will
automatically accept the public key via the url - I don't know why
Jenkins is different - but it appears to install a new repo file and
try to import the pubkey again on install - maybe this confuses yum?
Just speculating - not going to investigate further :)
Cheers,
Den
On Fri, Apr 27, 2012 at 7:51 AM, Michael Harris
<mich...@twofishcreative.com> wrote:
> On Thursday, 26 April 2012 18:33:18 UTC+10, denmat wrote:
>>
>> Hi, I just spun up a fresh AWS instance and did this:
>>
>> $ cat puppet.repo.pp
>> class jenkins {
>>
>> yumrepo { "jenkins":
>> baseurl => "http://pkg.jenkins-ci.org/redhat";,
>> descr => "Jenkins",
>> enabled => 1,
>> gpgcheck => 1,
>> gpgkey =>
>> "http://pkg.jenkins-ci.org/redhat/jenkins-ci.org.key";,
>> }
>> package {"jenkins": ensure => latest }
>> }
>>
>> include jenkins
>>
>
> I appreciate your help, but with that manifest I get the same error on both
> the node I'm trying to install on and on a fresh CentOS 5.7 with Puppet
> 2.7.9.
>
> err: /Stage[main]/Jenkins/Package[jenkins]/ensure: change from absent to
> latest failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y
> install jenkins' returned 1: warning: rpmts_HdrFromFdno: Header V4 DSA
> signature: NOKEY, key ID d50582e6
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/sVsibb6ExBsJ.
>
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> 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 puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
