Due to upgrading to Debian 7 Wheezy , I choose to rebuilt our puppet setup.
Now all went well except that I have one issue , changes made via puppet
dashboard do not get pushed to the client.
I have used the APT repository from puppetlabs to install all the servers
and clients.
I can run puppe
Hi I have seen numerous posts via Google saying this is an issue but not
found a puppet based solution for it.
Does anyone have an idea how I can make this work ? I do realize I am
looking at separate versions and was playing with the idea to force a more
locked down versioning to keep them the
As far as I know there is still a compatibility issue between puppet 3.0
and ruby 1.9.3, I also need this to work due to needing 1.9.3 for
a application targeted to run on the same machine as my puppet environment
but thus far it has been a no go.
Some googling has given me some options to lin
Hi all,
I have been kinda stuck with the following few issues (all related to one
and other)
What I want ot ddo is define a couple of standard actions in puppet that I
can use across all my classes.
So for example I define a exec for apt-get update , or a reload. When built
in to a class it w
Hi , Yes this is to be expected as RHEL 7 does away with some of the
dependencies like ifconfig etc. You will have to install thoose after.
For that you will also have to install some extra repos if I recall right.
You will have to install bind-utils and net-tools for all to function
normal agai
Been fighting witht his now for a bit , and IRC didnt seem to have any
answers so thought I would ask here.
I have 2 platforms , one prod one pre-prod the pre-prod runs basiclly the
latest versions puppetdb 2 and puppet 3.62 for clients and master. This
platform is also where I am having proble
http://pastebin.com/UnNxw0n6
There you go all in one
Cleaned soem comments out to reduce the size a bit , but I think it is
relativlly vanilla
On Wednesday, June 25, 2014 7:25:57 PM UTC+2, Ken Barber wrote:
>
> > Been fighting witht his now for a bit , and IRC didnt seem to have any
> > answer
Ok your route is the wrong way around , puppetdb wont play nice with sub
3.5.1 in my experience so your puppet master should be upgraded first when
it is upgraded then do the rest, and why not version pin your clients via a
puppet class ?
My experience is that the 2.x client will give you troub
