Hello All,
Puppet Labs will be dropping support for Puppet 2.7 and Puppet Enterprise
2.8, in the next major release of Puppet Labs modules. Puppet Enterprise
2.8 being the last PE release that included Puppet 2.7.
New releases of Puppet Labs modules will drop support for 2.7. While this
will
FOUND IT!
It was a comedy of errors. The perms on the node.rb script were wrong (not
sure how they got that way, but...) and not only that there was some
residual configuration issues from an experiment I did two weeks ago that
was pointing to the hostname pocforman. instead of the FQDN of the
Fo
Probably the simplest approach would be to write an exec resource using the
command
/usr/bin/apt-get install --only-upgrade
for apt packages.
Charles Yeomans
> On Feb 24, 2015, at 10:47 AM, Ximena Cardinali
> wrote:
>
> I just want to upgrade specific Packages.
>
> The idea is somethi
I just want to upgrade specific Packages.
The idea is something like : ensure=>latest, onlyif=>present
Cheers,
Ximena.
On Tuesday, 24 February 2015 16:43:06 UTC+1, David Schmitt wrote:
>
> On 2015-02-24 16:28, Ximena Cardinali wrote:
> > Hello There,
> >
> > I'm trying to write a module to up
On 2015-02-24 16:28, Ximena Cardinali wrote:
Hello There,
I'm trying to write a module to update certain vulnerable packages in
Debian Systems.
My idea is to update them only and only if they are *installed*. Is
there any exec command or any other tricks that you may know to do that?
So far, I'
On 2015-02-24 16:09, Peter Berghold wrote:
What it looks like to me is going on is the YML file for the host ends
up on the Remote Master (which I can verify by looking for it) and the
node.rb is running on the Grand Master. Since the YML files isn't on the
Grand Master the lookup (of course) fai
Hello There,
I'm trying to write a module to update certain vulnerable packages in
Debian Systems.
My idea is to update them only and only if they are *installed*. Is there
any exec command or any other tricks that you may know to do that?
So far, I've got the basics: :$
package { '$pa
thank you, completely missed it.
On Tuesday, February 24, 2015 at 3:06:34 PM UTC, Josh Cooper wrote:
>
>
>
> On Tuesday, February 24, 2015, Helen Paterson > wrote:
>
>> Hi,
>>
>> When i add the user attribute to Scheduled_task, the scheduled task is
>> not created, but if i comment out the user
What it looks like to me is going on is the YML file for the host ends up
on the Remote Master (which I can verify by looking for it) and the node.rb
is running on the Grand Master. Since the YML files isn't on the Grand
Master the lookup (of course) fails. So the real question is can we make
the
On Tuesday, February 24, 2015, Helen Paterson
wrote:
> Hi,
>
> When i add the user attribute to Scheduled_task, the scheduled task is not
> created, but if i comment out the user attribute the scheduled task is
> created running as system.
>
> This doesn't seem to work
>
> scheduled_task { 'Cop
Hi,
When i add the user attribute to Scheduled_task, the scheduled task is not
created, but if i comment out the user attribute the scheduled task is
created running as system.
This doesn't seem to work
scheduled_task { 'CopyCF11ReposFromDR':
ensure => present,
enabled
On Tuesday, February 24, 2015 at 1:08:17 AM UTC-6, Raj Raju wrote:
>
> Hi,
>
> I am tried to creating the user account on puppet agent.puppet agent is
> not reflecting my changes.
>
> Edited */etc/puppetlabs/puppet*/*manifests/site.pp* file as follows:
>
> node 'puppet.client.net' {
> include
Hi Peter,
you might be running into http://projects.theforeman.org/issues/5925 .
I'm wondering whether subsequent runs work.
Also, the node.rb will run on the remote client's puppet master, so,
probably your "Remote Master". Since the default node.rb from foreman
requires this yaml file, it'l
Using crude ascii art, here is what I have set up so far in my lab..
[Foreman/Puppet Grand Master] <-- foreman-proxy here
^
|
V
Hi,
I am having problems installing a kernel from backports on Debian Wheezy with
Puppet 3.7.4
I am using puppetlabs/apt to manage Debian repositories and have the following
code for my note
notice("getting kernel from backports...")
apt::force { 'linux-image-amd64':
release => 'wh
15 matches
Mail list logo
