Hi,
This is a very strange one. On my CA server (which also runs puppet as
an agent to control various things), sometimes a file gets turned into a
directory. It's only this file and on this server (the other puppet
controlled servers don't have this issue).
Using puppet 3.7.3 from the puppe
Thanks for the explanation. It really help me to understand about this.
On Tuesday, December 2, 2014 10:06:30 PM UTC+8, jcbollinger wrote:
>
>
>
> On Monday, December 1, 2014 8:11:54 PM UTC-6, fauzi.p...@gmail.com wrote:
>>
>> thanks for the reply, is it will make puppet connection lost or someth
On 12/2/14 11:04 AM, Riley Shott wrote:
The puppet_stack module will bring up a Puppet Master (additionally
the Foreman, and/or smart-proxy) using RVM, & Gems (Puppet, Facter,
Hiera, Passenger). We're using it for our production infrastructure,
and everything is a lot more performant with Ruby 2.
Hmm..yep. Same here. I need to go think some more.
Thanks!
Leam
On Tue, Dec 2, 2014 at 3:38 PM, Tony Thayer wrote:
> I was able to get my test to work by passing "hiera admins ::fqdn=`facter
> fqdn`"
> The --debug flag clued me in to the fact that it wasn't even looking in the
> nodes folder.
>
I was able to get my test to work by passing "hiera admins ::fqdn=`facter
fqdn`"
The --debug flag clued me in to the fact that it wasn't even looking in the
nodes folder.
On Tuesday, December 2, 2014 11:15:24 AM UTC-8, leam hall wrote:
>
> Hey Tony,
>
> Only one hiera.yaml, this is PE 3. I'm i
You should also make sure that you comb through your Puppet code to bring
it up to compliance with the language changes in Ruby 1.9+. Here are some
examples:
- If you use Hiera with the YAML backend:
- String interpolation in yaml cannot begin on a key, value, or array
member unles
Hey Tony,
Only one hiera.yaml, this is PE 3. I'm in a big company that gets
touchy about sharing hostnames. Really what I did was "mv global.json
node/`facter fqdn`.json". I've also ensured the pe-puppet group has
access to the file.
Leam
On Tue, Dec 2, 2014 at 2:00 PM, Tony Thayer wrote:
> D
The puppet_stack module will bring up a Puppet Master (additionally the
Foreman, and/or smart-proxy) using RVM, & Gems (Puppet, Facter, Hiera,
Passenger). We're using it for our production infrastructure, and everything is
a lot more performant with Ruby 2.0.0.
https://forge.puppetlabs.com/Ginj
Do you still have two separate hiera.yaml configuration files? One lives in
/etc and the one puppet uses is in /etc/puppet. I often forget to replace
the one in /etc with a symlink to the one in /etc/puppet.
What is the actual filename of your node's .json file?
On Tuesday, December 2, 2014 10:
In addition to needing to use three '/'s in your URI as Den mentioned, you
would need to change up your folder path. Modules under /etc/puppet/modules
all have their own structure i.e.
/etc/puppet/modules/modulename/{files,manifests,templates,tests}. When
structuring your URI you need to keep i
Hey Tony,
I made both changes but still getting "nil" for the admin list.
Leam
On Tue, Dec 2, 2014 at 1:32 PM, Tony Thayer wrote:
> You have declared a full folder path instead of a relative one.
> Change "/node/%{fqdn}" to "node/%{fqdn}" and it should work.
> Also as an aside, I would move you
On 12/2/14 10:34 AM, Ramin K wrote:
3. gem install puppet, hiera, and any other gems you currently use.
3. gem install puppet, hiera, and any other gems you currently use into
the Ruby you want to use for your Puppet master.
I knew I'd miss something.
Ramin
--
You received this message bec
On 12/1/14 4:56 PM, josie.worker...@gmail.com wrote:
HI there,
I'm looking for any tips/pointers on how to upgrade an existing
puppetmaster installation (v3.2.3, using system ruby 1.8.7 on Centos 6u3).
We don't have RVM installed on the puppetmaster itself, as it's been
around since 2.x days an
You have declared a full folder path instead of a relative one.
Change "/node/%{fqdn}" to "node/%{fqdn}" and it should work.
Also as an aside, I would move your defaults to the end of the lookup list.
The lookup should go from most specific to least specific.
- Tony
On Tuesday, December 2, 2014
Could you please post the resource definitions that caused this? I ask
because the yum provider should not do this with
ensure => 'absent'
but will with
ensure => 'purged'
while with the rpm provider, if you're forcing it for some reason, you
could probably pass
uninstall_option => '--nodeps
I'm trying to move forward with our PE setup. However, I'm new and it's
going slow. Right now I'm stuck on getting a node based json file to be
read for hiera.
###
# heira.yaml
# restart pe-puppet each time this file has been edited.
---
:backends:
- yaml
- json
:hierarchy:
- defaults
On Dec 2, 2014 4:50 AM, "Clay Stuckey" wrote:
>
> I wrote two manifests for RHEL systems. One removed syslog. The other
installed rsyslog. The syslog removal followed a tragic dependency tree
removing RPMs such as coreutils, rpm, yum and pam. Once the servers
rebooted, they were left in an unusabl
Thank you so much for this reply and thank you for the detailed example.
( I am using deep merge aswell )
On Wednesday, November 26, 2014 10:54:26 AM UTC, Felix.Frank wrote:
> Hi,
>
> please note that
>
> create_resources('iis::manage_site', hiera_hash('iis::sites', []))
>
> is not the mos
On Tuesday, December 2, 2014 8:01:33 AM UTC-5, duke wrote:
>
> On 2014-12-01 22:10, leam hall wrote:
> > I've heard that the goal is to move away from a
> > ~hieradata/{dev|test|prod} directory structure to use Facts. What I
> > haven't seen is how to control module versions with that. If you
>
On Monday, December 1, 2014 8:11:54 PM UTC-6, fauzi.p...@gmail.com wrote:
>
> thanks for the reply, is it will make puppet connection lost or something
> bad happen if we use yum update ?
>
>
Let me be more explicit: you can update Puppet or any other software on the
master via "yum update", b
On 2014-12-01 22:10, leam hall wrote:
I've heard that the goal is to move away from a
~hieradata/{dev|test|prod} directory structure to use Facts. What I
haven't seen is how to control module versions with that. If you
update mymodule and put it in the ~puppet/modules directory, what
makes dev bo
HI there,
I'm looking for any tips/pointers on how to upgrade an existing
puppetmaster installation (v3.2.3, using system ruby 1.8.7 on Centos 6u3).
We don't have RVM installed on the puppetmaster itself, as it's been around
since 2.x days and upgraded over time.
I've installed ruby 1.9.3 from
I wrote two manifests for RHEL systems. One removed syslog. The other
installed rsyslog. The syslog removal followed a tragic dependency tree
removing RPMs such as coreutils, rpm, yum and pam. Once the servers
rebooted, they were left in an unusable state. I had to boot in rescue
mode, manually
I'm just starting out and trying to figure stuff out. Here's one place I'm
stumped and could use some help.
I've heard that the goal is to move away from a ~hieradata/{dev|test|prod}
directory structure to use Facts. What I haven't seen is how to control
module versions with that. If you update
thanks, that would possibly be an option.
Am Montag, 1. Dezember 2014 18:03:12 UTC+1 schrieb Wil Cooley:
>
>
> On Nov 27, 2014 12:54 AM, "Peter Bauer" >
> wrote:
> >
> > i know that PuppetDB is the way to go for the future but currently i am
> forced to use Puppet 2.7 with the Stored Configurati
On 2014-12-02 03:11, fauzi.profit...@gmail.com wrote:
thanks for the reply, is it will make puppet connection lost or
something bad happen if we use yum update ?
That's not really a Puppet question, but a question every sysadmin has
to answer
himself. Which updates are applied in your environmen
26 matches
Mail list logo
