John,
thank you for pointing me in the right direction. The problem was that each
time I made changes to hiera.yaml file I'll restart the master with service
puppetmaster restart.
Well apparently the master was not really restarting even though it was
saying it was. So it was going into this st
On Tuesday, January 7, 2014 11:39:14 AM UTC-6, kai wrote:
>
> What version of Puppet are you running?
>> *3.4.1 for both master and agent*
>> As what user is the master running? (Typically an unprivileged user
>> named 'puppet'.)
>> *The master is running as user puppet*
>> As what user are you
---
:backends:
- yaml
- file
:hierarchy:
- defaults
- "%{clientcert}"
- "%{::domain}/%{::environment}/%{::osfamily}/%{::lsbdistcodename}"
- global
:yaml:
:datadir: /etc/puppet/data
On Tuesday, January 7, 2014 12:05:46 PM UTC-6, Andrew wrote:
>
>
> Content of the yaml file - any quo
I actually have both variables.
On Tuesday, January 7, 2014 11:54:38 AM UTC-6, Jose Luis Ledesma wrote:
>
> Mmm the error is about ssh_package_name, but you have tried the puppet
> apply with ssh_service_name. could be this the problem?
--
You received this message because you are subscribed to
Content of the yaml file - any quotes there which might cause issues?
Try puppet master compile for the node - is it failing as well?
> What version of Puppet are you running?
> *3.4.1 for both master and agent*
> As what user is the master running? (Typically an unprivileged user named
> 'puppet
One more thing to mention is that if I change the hierarchy from being a
directory as mentioned above to just a file like so:
:hierarchy:
- "%{::environment}_%{::osfamily}_%{::lsbdistcodename}"
both puppet apply and puppet agent are able to find the variable.
However if I prepend the "domai
It is worth mentioning that if I replace this hierarchy:
- "%{::environment}/%{::osfamily}/%{::lsbdistcodename}"
which uses directories with just a single file like so:
- "%{::environment}_%{::osfamily}_%{::lsbdistcodename}"
both puppet apply and puppet agent are able to find the variable.
If
Mmm the error is about ssh_package_name, but you have tried the puppet apply
with ssh_service_name. could be this the problem?
--
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, sen
>
> What version of Puppet are you running?
> *3.4.1 for both master and agent*
> As what user is the master running? (Typically an unprivileged user named
> 'puppet'.)
> *The master is running as user puppet*
> As what user are you running the agent in your tests?
> *I am running the agent and
On Monday, January 6, 2014 4:42:54 PM UTC-6, kai wrote:
>
> Hm nothing in the logs. It's worth mentioning that I run this on the
> puppet master. Here's the config in case I missed something there:
>
>
What version of Puppet are you running?
As what user is the master running? (Typically an u
Hm nothing in the logs. It's worth mentioning that I run this on the puppet
master. Here's the config in case I missed something there:
[main]
pluginsync = true
factpath = /lib/facter
[agent]
environment = production
server = puppetmaster.loc.example.com
runinterval = 360
splay = true
configtim
On Monday, January 6, 2014 4:02:54 PM UTC-6, Andrew wrote:
>
> Anything in the puppet master logs?
>
> Not sure, but i think puppet apply - hiera lookup is done by client,
> puppet agent - lookup is done by puppet master.
>
That was the area I was about to prod, too. The hiera lookup is perfo
Anything in the puppet master logs?
Not sure, but i think puppet apply - hiera lookup is done by client,
puppet agent - lookup is done by puppet master.
Andrey
On 6 Jan 2014 21:33, "kai" wrote:
> Yes it's defined in :
>
> *"%{::domain}/%{::environment}/%{::osfamily}/%{::lsbdistcodename}"*
>
>
Yes it's defined in :
*"%{::domain}/%{::environment}/%{::osfamily}/%{::lsbdistcodename}"*
which is expanded to loc.example.com/production/Debian/wheezy.yaml
The problem is that when I run:
$ puppet apply --environment=production -e '$test =
hiera('ssh_service_config') notify { $test: }'
Debug
I assume "ssh_service_config" is indeed defined in your yaml file?
I would suggest to define it in the top level hierarchy in "defaults" and
then gradually move 1 level down until you find when it "disappears".
Andrey
On 6 January 2014 19:20, kai wrote:
> I have the following hiera.yaml file:
I have the following hiera.yaml file:
---
:backends:
- yaml
- file
:hierarchy:
- defaults
- "%{clientcert}"
* - "%{::domain}/%{::environment}/%{::osfamily}/%{::lsbdistcodename}"*
- global
:yaml:
:datadir: /etc/puppet/data
and the following in /etc/puppet/data:
*loc.example.com/pro
16 matches
Mail list logo
