Found the issue. The node in question was running an older (2.7) Puppet
agent.
On Friday, September 18, 2015 at 9:28:08 PM UTC+1, Garrett Honeycutt wrote:
>
> On 9/18/15 1:55 PM, Alexander Dacre wrote:
> > Hi,
> >
> > I'm having some difficulty with specifying a nogpgcheck option when
> > installing custom RPM packages via Puppet. The problem is that the
> > install_options do not get picked up by the agent.
> >
> > I've tried the following syntax:
> >
> > package { blah:
> > ensure => latest,
> > install_options => [ '--nogpgcheck'],
> > }
> >
> > package { blah:
> > ensure => latest,
> > install_options => '--nogpgcheck',
> > }
> >
> > But the client just doesn't pick it up and the run fails due to the
> > package not being signed.
> >
> > Any suggestions?
> >
> > Thanks,
> > A
> >
>
>
> Hi,
>
> Suggest signing the packages ;>
>
> But in efforts to help with your Puppet configuration, it seems that the
> provider might not understand the install option. What messages do you
> get when running with --debug? What type of system is this? Which
> package system are you using?
>
> Best regards,
> -g
>
> --
> Garrett Honeycutt
> @learnpuppet
> Puppet Training with LearnPuppet.com
> Mobile: +1.206.414.8658
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/106df4b4-d830-4f36-9876-a8cf48850d91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
