date:20160603

I'm having a little trouble verify via the command line because we are 
using the 'module_data' backend so the hiera data in question is specific 
to the module. But when I query the data via the module directly it works 
as expected

% hiera --hash -c ./hiera.yaml rabbitmq_profile::vhosts
WARN: 2016-06-03 15:52:02 -0400: Not using Hiera::Puppet_logger. It does 
not report itself to be suitable.
{"/"=>{"ensure"=>"present"},
 "p2"=>{"ensure"=>"present"},
 "test"=>{"ensure"=>"present"}}

So it might be something with the way module_data is requesting.

On Friday, June 3, 2016 at 2:42:45 PM UTC-4, Leonard Smith wrote:
>
> I've been trying to track down a problem with hiera_hash not merging.
>
> puppet-3.8.6-1.el7
> hiera-1.3.4-1.el7
>
> ## hiera.yaml
> :hierarchy:
>   - test
>   - common
>
> ## test.yaml
> ---
> rabbitmq_profile::vhosts:
>   'test' :
> ensure: present
>
> ## common.yaml
> ---
> rabbitmq_profile::vhosts:
>   '/' :
> ensure: present
>
> ## rabbitmq_profile.pp
>
> class rabbitmq_profile (
>
> $vhosts = hiera_hash('rabbitmq_profile::vhosts',{})
>
> ) {
>
>   notify { "<>$vhosts": }
>   create_resources(rabbitmq_vhost, $vhosts )
> }
>
> ## END
>
>
> When I apply the manifest it creates the vhost specified in test.yaml but 
> not the one in comon.yaml. I expected it to merge the has from both yamls 
> and create the '/' and 'test' vhosts.
>
>  If I remove test from hiera.yaml it creates the '/' vhost fine. I've 
> tried setting the merge_behavior explicitly to native, deep and deeper, but 
> I still see the behavior where it picks up the hash form the first yaml 
> file it encounters and ignores the rest.
>
>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/e8f77b9d-a0e3-48ee-a6e0-7eb8cd64f8e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Trouble creating a release RPM from puppetlabs/puppet source repo

2016-06-03 Thread Stefan Heijmans

Have you tried using the source RPMs from here;

https://yum.puppetlabs.com/el/6/PC1/SRPMS/


On Friday, June 3, 2016 at 8:44:20 PM UTC+2, Matt Larson wrote:
>
>
> I'm trying to create an RPM from source on a stock RHEL6-based (CentOS6) 
> instance, but I'm seeing errors.  I also posted in 
> https://ask.puppet.com/question/26388/trouble-creating-a-release-rpm-from-puppetlabspuppet-source-repo/
>  
>
> The output actually gets pretty far along, but stops at with this error: 
> "install: cannot stat ext/redhat/puppet.conf: no such file or directory". 
> If I fix that problem by manually editing the SPEC file, I just get more 
> errors, so clearly there is no need to go down a rabbit hole since this 
> must work for someone else, right?
>
> I'm also posted in 
> https://ask.puppet.com/question/26388/trouble-creating-a-release-rpm-from-puppetlabspuppet-source-repo/
>
> Ideas?
>
> Thanks in Advance,
> Matt
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/89acad2c-e900-4629-978c-db1b24dd1cf6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera Hash Merge Issues

2016-06-03 Thread Ramin K

That looks correct and you are also correct that the deep merge gem is
not required for simple top level key merges. Only for sub keys. I
believe the hiera_hash merge example here is still valid,

https://ask.puppet.com/question/13592/when-to-use-hiera-hiera_array-and-hiera_hash/

## rabbitmq_profile.pp
class rabbitmq_profile (
$vhosts = hiera_hash('rabbitmq_profile::vhosts',{})
) {

I'd make sure that actually the code you're using. If you're using hiera
or databindings it'll default to hiera() as well. That would certainly
explain the behavior you're seeing.

You might try running the master in debug so you can see the hiera
lookups it's attempting.

Ramin

On 6/3/16 11:57 AM, Leonard Smith wrote:

Deep gem is installed. However this should work with native correct if
all I am looking to have it do is create both '/' and 'test' vhost,
without ovverriding each other.

On Friday, June 3, 2016 at 2:47:45 PM UTC-4, Peter Kristolaitis wrote:

Did you install the deep_merge gem when using the deeper merge
option? The gem is required when using deep or deeper merging.

On 2016-06-03 02:38 PM, Leonard Smith wrote:

I've been trying to track down a problem with hiera_hash not merging.

puppet-3.8.6-1.el7
hiera-1.3.4-1.el7

## hiera.yaml
:hierarchy:
- test
- common

## test.yaml
---
rabbitmq_profile::vhosts:
'test' :
ensure: present

## common.yaml
---
rabbitmq_profile::vhosts:
'/' :
ensure: present

## rabbitmq_profile.pp

class rabbitmq_profile (

$vhosts = hiera_hash('rabbitmq_profile::vhosts',{})

) {

notify { "<>$vhosts": }
create_resources(rabbitmq_vhost, $vhosts )
}

## END

When I apply the manifest it creates the vhost specified in
test.yaml but not the one in comon.yaml. I expected it to merge
the has from both yamls and create the '/' and 'test' vhosts.

If I remove test from hiera.yaml it creates the '/' vhost fine.
I've tried setting the merge_behavior explicitly to native, deep
and deeper, but I still see the behavior where it picks up the
hash form the first yaml file it encounters and ignores the rest.

https://groups.google.com/d/msgid/puppet-users/9073d972-61d4-4454-bf0a-8dad4f889062%40googlegroups.com

.
For more options, visit https://groups.google.com/d/optout
.

--
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 puppet-users+unsubscr...@googlegroups.com
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/dda7b1bd-3380-48dc-89d8-5a5c64d5fce0%40googlegroups.com
.
For more options, visit https://groups.google.com/d/optout.

--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/299bd1e5-719f-8d0b-44af-e5da6dda0a78%40badapple.net.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera Hash Merge Issues

Try command line. Use the debug option
Dan White | d_e_wh...@icloud.com

“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.” (Bill Waterson: Calvin &
Hobbes)

On Jun 03, 2016, at 03:03 PM, Leonard Smith wrote:

Clarificaiton. I had tried in the hiera.yaml setting

:merge_behavior: deeper
the
:merge_behavior: deep

and

:merge_behavior: native.

I unset it as well as from my understanding, from the documentation I am not
concerned with deep merging. I just want to be able to specify two
non-colliding 'vhosts' in two different YAML files and have both be created.
The deep/deeper is only needed if the same key exists and I want to merge the
underlying key/values.

On Friday, June 3, 2016 at 2:42:45 PM UTC-4, Leonard Smith wrote:
I've been trying to track down a problem with hiera_hash not merging.

puppet-3.8.6-1.el7
hiera-1.3.4-1.el7

## hiera.yaml
:hierarchy:
- test
- common

## test.yaml
---
rabbitmq_profile::vhosts:
'test' :
ensure: present

## common.yaml
---
rabbitmq_profile::vhosts:
'/' :
ensure: present

## rabbitmq_profile.pp

class rabbitmq_profile (

$vhosts = hiera_hash('rabbitmq_profile::vhosts',{})

) {

notify { "<>$vhosts": }
create_resources(rabbitmq_vhost, $vhosts )
}

## END

When I apply the manifest it creates the vhost specified in test.yaml but not
the one in comon.yaml. I expected it to merge the has from both yamls and
create the '/' and 'test' vhosts.

If I remove test from hiera.yaml it creates the '/' vhost fine. I've tried
setting the merge_behavior explicitly to native, deep and deeper, but I still
see the behavior where it picks up the hash form the first yaml file it
encounters and ignores the rest.

--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/ad8306b9-a2ef-4d8b-8f2b-2f54196b6844%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/45e7dc49-245d-4d67-9ff4-028c67a95ec1%40me.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Hiera Hash Merge Issues

Clarificaiton. I had tried in the hiera.yaml setting

:merge_behavior: deeper
 
the 
:merge_behavior: deep

and

:merge_behavior: native.

I unset it as well as from my understanding, from the documentation I am 
not concerned with deep merging. I just want to be able to specify two 
non-colliding 'vhosts' in two different YAML files and have both be 
created. The deep/deeper is only needed if the same key  exists and I want 
to merge the underlying key/values. 


On Friday, June 3, 2016 at 2:42:45 PM UTC-4, Leonard Smith wrote:
>
> I've been trying to track down a problem with hiera_hash not merging.
>
> puppet-3.8.6-1.el7
> hiera-1.3.4-1.el7
>
> ## hiera.yaml
> :hierarchy:
>   - test
>   - common
>
> ## test.yaml
> ---
> rabbitmq_profile::vhosts:
>   'test' :
> ensure: present
>
> ## common.yaml
> ---
> rabbitmq_profile::vhosts:
>   '/' :
> ensure: present
>
> ## rabbitmq_profile.pp
>
> class rabbitmq_profile (
>
> $vhosts = hiera_hash('rabbitmq_profile::vhosts',{})
>
> ) {
>
>   notify { "<>$vhosts": }
>   create_resources(rabbitmq_vhost, $vhosts )
> }
>
> ## END
>
>
> When I apply the manifest it creates the vhost specified in test.yaml but 
> not the one in comon.yaml. I expected it to merge the has from both yamls 
> and create the '/' and 'test' vhosts.
>
>  If I remove test from hiera.yaml it creates the '/' vhost fine. I've 
> tried setting the merge_behavior explicitly to native, deep and deeper, but 
> I still see the behavior where it picks up the hash form the first yaml 
> file it encounters and ignores the rest.
>
>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/ad8306b9-a2ef-4d8b-8f2b-2f54196b6844%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera Hash Merge Issues

UNless the hiera.yaml you provided is incomplete, you did not tur on deep
merging.

https://docs.puppet.com/hiera/3.1/configuring.html#deepmergeoptions
Dan White | d_e_wh...@icloud.com

“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.” (Bill Waterson: Calvin &
Hobbes)

On Jun 03, 2016, at 02:57 PM, Leonard Smith wrote:

Deep gem is installed. However this should work with native correct if all I am
looking to have it do is create both '/' and 'test' vhost, without ovverriding
each other.

On Friday, June 3, 2016 at 2:47:45 PM UTC-4, Peter Kristolaitis wrote:
Did you install the deep_merge gem when using the deeper merge option? The gem
is required when using deep or deeper merging.

On 2016-06-03 02:38 PM, Leonard Smith wrote:
I've been trying to track down a problem with hiera_hash not merging.

puppet-3.8.6-1.el7
hiera-1.3.4-1.el7

## hiera.yaml
:hierarchy:
- test
- common

## test.yaml
---
rabbitmq_profile::vhosts:
'test' :
ensure: present

## common.yaml
---
rabbitmq_profile::vhosts:
'/' :
ensure: present

## rabbitmq_profile.pp

class rabbitmq_profile (

$vhosts = hiera_hash('rabbitmq_profile::vhosts',{})

) {

notify { "<>$vhosts": }
create_resources(rabbitmq_vhost, $vhosts )
}

## END

When I apply the manifest it creates the vhost specified in test.yaml but not
the one in comon.yaml. I expected it to merge the has from both yamls and
create the '/' and 'test' vhosts.

If I remove test from hiera.yaml it creates the '/' vhost fine. I've tried
setting the merge_behavior explicitly to native, deep and deeper, but I still
see the behavior where it picks up the hash form the first yaml file it
encounters and ignores the rest.

--
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 puppet-users...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/9073d972-61d4-4454-bf0a-8dad4f889062%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/dda7b1bd-3380-48dc-89d8-5a5c64d5fce0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/e77e61c8-54c8-408c-b865-e213c9368beb%40me.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera Hash Merge Issues

Deep gem is installed. However this should work with native correct if all 
I am looking to have it do is create both '/' and 'test' vhost, without 
ovverriding each other.



On Friday, June 3, 2016 at 2:47:45 PM UTC-4, Peter Kristolaitis wrote:
>
> Did you install the deep_merge gem when using the deeper merge option?  
> The gem is required when using deep or deeper merging.
>
>
> On 2016-06-03 02:38 PM, Leonard Smith wrote:
>
> I've been trying to track down a problem with hiera_hash not merging. 
>
> puppet-3.8.6-1.el7
> hiera-1.3.4-1.el7
>
> ## hiera.yaml
> :hierarchy:
>   - test
>   - common
>
> ## test.yaml
> ---
> rabbitmq_profile::vhosts:
>   'test' :
> ensure: present
>
> ## common.yaml
> ---
> rabbitmq_profile::vhosts:
>   '/' :
> ensure: present
>
> ## rabbitmq_profile.pp
>
> class rabbitmq_profile (
>
> $vhosts = hiera_hash('rabbitmq_profile::vhosts',{})
>
> ) {
>
>   notify { "<>$vhosts": }
>   create_resources(rabbitmq_vhost, $vhosts )
> }
>
> ## END
>
>
> When I apply the manifest it creates the vhost specified in test.yaml but 
> not the one in comon.yaml. I expected it to merge the has from both yamls 
> and create the '/' and 'test' vhosts.
>
>  If I remove test from hiera.yaml it creates the '/' vhost fine. I've 
> tried setting the merge_behavior explicitly to native, deep and deeper, but 
> I still see the behavior where it picks up the hash form the first yaml 
> file it encounters and ignores the rest.
>
>
> -- 
> 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 puppet-users...@googlegroups.com .
> To view this discussion on the web visit 
> 
> https://groups.google.com/d/msgid/puppet-users/9073d972-61d4-4454-bf0a-8dad4f889062%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/dda7b1bd-3380-48dc-89d8-5a5c64d5fce0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Trouble creating a release RPM from puppetlabs/puppet source repo


First Silly Question: Why ?
What do you need to do that cannot be done with the RPM's from a Puppetlabs 
repo ?
Dan White | d_e_wh...@icloud.com

“Sometimes I think the surest sign that intelligent life exists elsewhere in the 
universe is that none of it has tried to contact us.”  (Bill Waterson: Calvin & 
Hobbes)

On Jun 03, 2016, at 02:44 PM, Matt Larson  wrote:


I'm trying to create an RPM from source on a stock RHEL6-based (CentOS6) instance, but I'm seeing errors.  I also posted in https://ask.puppet.com/question/26388/trouble-creating-a-release-rpm-from-puppetlabspuppet-source-repo/ 


The output actually gets pretty far along, but stops at with this error: "install: 
cannot stat ext/redhat/puppet.conf: no such file or directory". If I fix that 
problem by manually editing the SPEC file, I just get more errors, so clearly there is no 
need to go down a rabbit hole since this must work for someone else, right?

I'm also posted in 
https://ask.puppet.com/question/26388/trouble-creating-a-release-rpm-from-puppetlabspuppet-source-repo/

Ideas?

Thanks in Advance,
Matt

--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8d532582-be4b-4e58-813e-0e3519043a3f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/ae44b8cd-f8a9-4f2a-b983-17c31dc61438%40me.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera Hash Merge Issues

Better suggestion.
Thanks, Peter.
Dan White | d_e_wh...@icloud.com

“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.” (Bill Waterson: Calvin &
Hobbes)

On Jun 03, 2016, at 02:47 PM, Peter Kristolaitis wrote:

Did you install the deep_merge gem when using the deeper merge option? The gem
is required when using deep or deeper merging.

On 2016-06-03 02:38 PM, Leonard Smith wrote:
I've been trying to track down a problem with hiera_hash not merging.

puppet-3.8.6-1.el7
hiera-1.3.4-1.el7

## hiera.yaml
:hierarchy:
- test
- common

## test.yaml
---
rabbitmq_profile::vhosts:
'test' :
ensure: present

## common.yaml
---
rabbitmq_profile::vhosts:
'/' :
ensure: present

## rabbitmq_profile.pp

class rabbitmq_profile (

$vhosts = hiera_hash('rabbitmq_profile::vhosts',{})

) {

notify { "<>$vhosts": }
create_resources(rabbitmq_vhost, $vhosts )
}

## END

When I apply the manifest it creates the vhost specified in test.yaml but not
the one in comon.yaml. I expected it to merge the has from both yamls and
create the '/' and 'test' vhosts.

If I remove test from hiera.yaml it creates the '/' vhost fine. I've tried
setting the merge_behavior explicitly to native, deep and deeper, but I still
see the behavior where it picks up the hash form the first yaml file it
encounters and ignores the rest.

--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/9073d972-61d4-4454-bf0a-8dad4f889062%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/5751D0C8.2030806%40alter3d.ca.
For more options, visit https://groups.google.com/d/optout.

--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/88383a91-f48a-42fd-a512-cfe0d469665f%40me.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera Hash Merge Issues

2016-06-03 Thread Peter Kristolaitis

Did you install the deep_merge gem when using the deeper merge option?
The gem is required when using deep or deeper merging.

On 2016-06-03 02:38 PM, Leonard Smith wrote:

I've been trying to track down a problem with hiera_hash not merging.

puppet-3.8.6-1.el7
hiera-1.3.4-1.el7

## hiera.yaml
:hierarchy:
- test
- common

## test.yaml
---
rabbitmq_profile::vhosts:
'test' :
ensure: present

## common.yaml
---
rabbitmq_profile::vhosts:
'/' :
ensure: present

## rabbitmq_profile.pp

class rabbitmq_profile (

$vhosts = hiera_hash('rabbitmq_profile::vhosts',{})

) {

notify { "<>$vhosts": }
create_resources(rabbitmq_vhost, $vhosts )
}

## END

When I apply the manifest it creates the vhost specified in test.yaml
but not the one in comon.yaml. I expected it to merge the has from
both yamls and create the '/' and 'test' vhosts.

If I remove test from hiera.yaml it creates the '/' vhost fine. I've
tried setting the merge_behavior explicitly to native, deep and
deeper, but I still see the behavior where it picks up the hash form
the first yaml file it encounters and ignores the rest.

--
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 puppet-users+unsubscr...@googlegroups.com
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/9073d972-61d4-4454-bf0a-8dad4f889062%40googlegroups.com
.

For more options, visit https://groups.google.com/d/optout.

--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/5751D0C8.2030806%40alter3d.ca.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera Hash Merge Issues

Have you tried hiera command line debugging ?
Dan White | d_e_wh...@icloud.com

“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.” (Bill Waterson: Calvin &
Hobbes)

On Jun 03, 2016, at 02:42 PM, Leonard Smith wrote:

I've been trying to track down a problem with hiera_hash not merging.

puppet-3.8.6-1.el7
hiera-1.3.4-1.el7

## hiera.yaml
:hierarchy:
- test
- common

## test.yaml
---
rabbitmq_profile::vhosts:
'test' :
ensure: present

## common.yaml
---
rabbitmq_profile::vhosts:
'/' :
ensure: present

## rabbitmq_profile.pp

class rabbitmq_profile (

$vhosts = hiera_hash('rabbitmq_profile::vhosts',{})

) {

notify { "<>$vhosts": }
create_resources(rabbitmq_vhost, $vhosts )
}

## END

When I apply the manifest it creates the vhost specified in test.yaml but not
the one in comon.yaml. I expected it to merge the has from both yamls and
create the '/' and 'test' vhosts.

If I remove test from hiera.yaml it creates the '/' vhost fine. I've tried
setting the merge_behavior explicitly to native, deep and deeper, but I still
see the behavior where it picks up the hash form the first yaml file it
encounters and ignores the rest.

--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/9073d972-61d4-4454-bf0a-8dad4f889062%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/968448da-1bc7-4e09-90f9-3119e09ae21f%40me.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Trouble creating a release RPM from puppetlabs/puppet source repo

2016-06-03 Thread Matt Larson


I'm trying to create an RPM from source on a stock RHEL6-based (CentOS6) 
instance, but I'm seeing errors.  I also posted in 
https://ask.puppet.com/question/26388/trouble-creating-a-release-rpm-from-puppetlabspuppet-source-repo/
 


The output actually gets pretty far along, but stops at with this error: 
"install: cannot stat ext/redhat/puppet.conf: no such file or directory". 
If I fix that problem by manually editing the SPEC file, I just get more 
errors, so clearly there is no need to go down a rabbit hole since this 
must work for someone else, right?

I'm also posted in 
https://ask.puppet.com/question/26388/trouble-creating-a-release-rpm-from-puppetlabspuppet-source-repo/

Ideas?

Thanks in Advance,
Matt

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8d532582-be4b-4e58-813e-0e3519043a3f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Hiera Hash Merge Issues

I've been trying to track down a problem with hiera_hash not merging.

puppet-3.8.6-1.el7
hiera-1.3.4-1.el7

## hiera.yaml
:hierarchy:
  - test
  - common

## test.yaml
---
rabbitmq_profile::vhosts:
  'test' :
ensure: present

## common.yaml
---
rabbitmq_profile::vhosts:
  '/' :
ensure: present

## rabbitmq_profile.pp

class rabbitmq_profile (

$vhosts = hiera_hash('rabbitmq_profile::vhosts',{})

) {

  notify { "<>$vhosts": }
  create_resources(rabbitmq_vhost, $vhosts )
}

## END


When I apply the manifest it creates the vhost specified in test.yaml but 
not the one in comon.yaml. I expected it to merge the has from both yamls 
and create the '/' and 'test' vhosts.

 If I remove test from hiera.yaml it creates the '/' vhost fine. I've tried 
setting the merge_behavior explicitly to native, deep and deeper, but I 
still see the behavior where it picks up the hash form the first yaml file 
it encounters and ignores the rest.


-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/9073d972-61d4-4454-bf0a-8dad4f889062%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PuppetDB Query based on facts

I was messing around in psql to see if I could figure out the table 
structure and just query without the API wrapper, I couldn't before you 
replied.  Price is right losing horn.

On Friday, June 3, 2016 at 1:37:59 PM UTC-5, Mike Sharpton wrote:
>
> Doh!  Quotes matter, didn't think of it.  That appears to work, I grepped 
> and piped and have my list.  Thanks very much again, you have saved me work 
> twice now.  
>
> Mike
>
> On Friday, June 3, 2016 at 12:43:17 PM UTC-5, Wyatt Alt wrote:
>>
>> Mike,
>>
>> Where I was going with that is you might get results with
>>
>> curl -X GET http://localhost:8080/pdb/query/v4/nodes -d 'query=["and", 
>> ["=", ["fact", "operatingsystemmajrelease"], "7"], ["=", ["fact", "facta"], 
>> "true"]]'
>>
>> or
>>
>> curl -X GET http://localhost:8080/pdb/query/v4/nodes -d 'query=["and", 
>> ["=", ["fact", "operatingsystemmajrelease"], "7"], ["=", ["fact", "facta"], 
>> "True"]]'
>>
>> Let me know if one of those does it.
>>
>> Wyatt
>>
>>
>> On Fri, Jun 3, 2016 at 10:37 AM, Mike Sharpton  wrote:
>>
>>> Yep, the value of my fact is a string.  I will keep googling around to 
>>> see what I can find.  Thanks,
>>>
>>> Mike
>>>
>>>
>>> On Friday, June 3, 2016 at 11:31:28 AM UTC-5, Wyatt Alt wrote:

 Hey Mike, 

 I think operatingsystemmajrelease might be a string instead of an int, 
 based on https://tickets.puppetlabs.com/browse/FACT-962. You also 
 might 
 verify that facta is valued with a real boolean instead of a 
 stringified 
 bool (the reference to casing made me wonder.) 

 Wyatt 

>>> -- 
>>> 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 puppet-users...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/puppet-users/08f94fe4-c922-4ead-aced-400212c7a058%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/95fc0dbb-8c04-441f-97b3-1da4841b7f4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PuppetDB Query based on facts

Doh!  Quotes matter, didn't think of it.  That appears to work, I grepped 
and piped and have my list.  Thanks very much again, you have saved me work 
twice now.  

Mike

On Friday, June 3, 2016 at 12:43:17 PM UTC-5, Wyatt Alt wrote:
>
> Mike,
>
> Where I was going with that is you might get results with
>
> curl -X GET http://localhost:8080/pdb/query/v4/nodes -d 'query=["and", 
> ["=", ["fact", "operatingsystemmajrelease"], "7"], ["=", ["fact", "facta"], 
> "true"]]'
>
> or
>
> curl -X GET http://localhost:8080/pdb/query/v4/nodes -d 'query=["and", 
> ["=", ["fact", "operatingsystemmajrelease"], "7"], ["=", ["fact", "facta"], 
> "True"]]'
>
> Let me know if one of those does it.
>
> Wyatt
>
>
> On Fri, Jun 3, 2016 at 10:37 AM, Mike Sharpton  > wrote:
>
>> Yep, the value of my fact is a string.  I will keep googling around to 
>> see what I can find.  Thanks,
>>
>> Mike
>>
>>
>> On Friday, June 3, 2016 at 11:31:28 AM UTC-5, Wyatt Alt wrote:
>>>
>>> Hey Mike, 
>>>
>>> I think operatingsystemmajrelease might be a string instead of an int, 
>>> based on https://tickets.puppetlabs.com/browse/FACT-962. You also might 
>>> verify that facta is valued with a real boolean instead of a stringified 
>>> bool (the reference to casing made me wonder.) 
>>>
>>> Wyatt 
>>>
>> -- 
>> 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 puppet-users...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/08f94fe4-c922-4ead-aced-400212c7a058%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/3419859f-6b0b-4a70-adad-4e910fa7c74f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Puppet Agent 1.5.1 available

2016-06-03 Thread Stefan Heijmans

Hi Eric,

Think you ment these release notes:
https://docs.puppet.com/puppet/latest/reference/release_notes_agent.html

Stefan

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4c172ef3-9669-4a59-8694-dafee118dc02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PuppetDB Query based on facts

Yep, the value of my fact is a string.  I will keep googling around to see 
what I can find.  Thanks,

Mike

On Friday, June 3, 2016 at 11:31:28 AM UTC-5, Wyatt Alt wrote:
>
> Hey Mike, 
>
> I think operatingsystemmajrelease might be a string instead of an int, 
> based on https://tickets.puppetlabs.com/browse/FACT-962. You also might 
> verify that facta is valued with a real boolean instead of a stringified 
> bool (the reference to casing made me wonder.) 
>
> Wyatt 
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/08f94fe4-c922-4ead-aced-400212c7a058%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PuppetDB Query based on facts

2016-06-03 Thread Wyatt Alt

Mike,

Where I was going with that is you might get results with

curl -X GET http://localhost:8080/pdb/query/v4/nodes -d 'query=["and",
["=", ["fact", "operatingsystemmajrelease"], "7"], ["=", ["fact", "facta"],
"true"]]'

or

curl -X GET http://localhost:8080/pdb/query/v4/nodes -d 'query=["and",
["=", ["fact", "operatingsystemmajrelease"], "7"], ["=", ["fact", "facta"],
"True"]]'

Let me know if one of those does it.

Wyatt


On Fri, Jun 3, 2016 at 10:37 AM, Mike Sharpton  wrote:

> Yep, the value of my fact is a string.  I will keep googling around to see
> what I can find.  Thanks,
>
> Mike
>
>
> On Friday, June 3, 2016 at 11:31:28 AM UTC-5, Wyatt Alt wrote:
>>
>> Hey Mike,
>>
>> I think operatingsystemmajrelease might be a string instead of an int,
>> based on https://tickets.puppetlabs.com/browse/FACT-962. You also might
>> verify that facta is valued with a real boolean instead of a stringified
>> bool (the reference to casing made me wonder.)
>>
>> Wyatt
>>
> --
> 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 puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/08f94fe4-c922-4ead-aced-400212c7a058%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAJDiH3FAaY40bD_ZYgSP0QNY3znz83Wto7rdD2dZk7y2erYCCg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Puppet Agent 1.5.1 available

2016-06-03 Thread Eric Sorenson

Puppet Agent 1.5.1 is now available. This is a bugfix release that includes 
Puppet and Facter versions with a handful of fixes; no other components are 
update from the Puppet Agent 1.5.0 release a couple of weeks ago.

Notably, a couple of erroneous facts on Solaris are now correct 
("solaris_zones" and "productname"); Chuck Schweitzer found (and Thomas 
Hallgren fixed) a problem using Data in Modules with Hiera; and the 
Henrik/Thomas wrecking crew also fixed a problem with autorequires that broke 
puppetlabs-aws and puppet-archive, among other modules.

Check out the full release notes here: 
https://docs.puppet.com/puppetserver/latest/release_notes.html

To install or upgrade puppet-agent, follow the getting started directions: 
http://docs.puppetlabs.com/puppet/latest/reference/index.html


Eric Sorenson - eric.soren...@puppet.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4B23907C-50EA-40E6-A7D9-E1A8819465D8%40puppet.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PuppetDB Query based on facts

Wyatt,

Thanks for your reply.  I changed out my url and facta to my fact name, 
nothing is returned except this.

[ ]

To ensure it wasn't my fact that was messing this up, I tried another 
standard fact is_pe.  The value should be uppercase "False" but this 
returns a 500 when run that post/GET.

:8080/pdb/query/v4/nodes -d 'query=["and", ["=", ["fact", 
"operatingsystemmajrelease"], 7], ["=", ["fact", "is_pe"], False]]'

This returns nothing as well.  I have about 350 nodes of this type.

:8080/pdb/query/v4/nodes -d 'query=["and", ["=", ["fact", 
"operatingsystemmajrelease"], 7], ["=", ["fact", "is_pe"], false]]'

My fact value is lowercase as well, true is the value.  Any ideas?  

Thanks in advance,
Mike



On Friday, June 3, 2016 at 9:56:41 AM UTC-5, Wyatt Alt wrote:
>
> Hey Mike,
> I'm thinking you want something like this:
>
> curl -X GET http://localhost:8080/pdb/query/v4/nodes -d 'query=["and", 
> ["=", ["fact", "operatingsystemmajrelease"], 7], ["=", ["fact", "facta"], 
> true]]'
>
> Wyatt
>
>
>
> On Fri, Jun 3, 2016 at 6:40 AM, Mike Sharpton  > wrote:
>
>> Hey all,
>>
>> I am trying to do what should be a simple thing.  I need to query 
>> PuppetDB to gather a list of machines based on arbitrary facta being equal 
>> to true and the operatingsystemmajrelease fact being 7.  I have searched 
>> around and found a few examples, but can't get them to work properly.  I 
>> saw and example from Wyatt on here, but I must be doing something wrong as 
>> I can't even get that to run.  I have PuppetDB 3.2.0.
>>
>> I'm not sure if I should be running my query against this endpoint 
>> /pdb/query/v4/facts/, or drill into the facta uri and run a in/and against 
>> the operatingsystemmajrelease fact to get what I need.  All I need back is 
>> the certname of the machines in which facta is true and 
>> operatingsystemmajrelease is 7.  If someone has a quick one liner, it would 
>> be appreciated, otherwise I can bust out the data and filter it with 
>> Excel.  Thanks,
>>
>> Mike
>>
>> -- 
>> 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 puppet-users...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/5a1fec0e-1d02-442f-9465-9660a6087a8f%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5560a1c7-b2a9-482c-a1cd-e493b3dad2b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PuppetDB Query based on facts

2016-06-03 Thread Wyatt Alt

Hey Mike,
I'm thinking you want something like this:

curl -X GET http://localhost:8080/pdb/query/v4/nodes -d 'query=["and",
["=", ["fact", "operatingsystemmajrelease"], 7], ["=", ["fact", "facta"],
true]]'

Wyatt



On Fri, Jun 3, 2016 at 6:40 AM, Mike Sharpton  wrote:

> Hey all,
>
> I am trying to do what should be a simple thing.  I need to query PuppetDB
> to gather a list of machines based on arbitrary facta being equal to true
> and the operatingsystemmajrelease fact being 7.  I have searched around and
> found a few examples, but can't get them to work properly.  I saw and
> example from Wyatt on here, but I must be doing something wrong as I can't
> even get that to run.  I have PuppetDB 3.2.0.
>
> I'm not sure if I should be running my query against this endpoint
> /pdb/query/v4/facts/, or drill into the facta uri and run a in/and against
> the operatingsystemmajrelease fact to get what I need.  All I need back is
> the certname of the machines in which facta is true and
> operatingsystemmajrelease is 7.  If someone has a quick one liner, it would
> be appreciated, otherwise I can bust out the data and filter it with
> Excel.  Thanks,
>
> Mike
>
> --
> 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 puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/5a1fec0e-1d02-442f-9465-9660a6087a8f%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAJDiH3HK%3DihNjuz8PGWcKM_XsQsHcQ46DCqBw-o8etY8uG-JpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet-in-Docker

2016-06-03 Thread Rich Burroughs

I was starting to play around with rolling my own puppetserver container a
few weeks ago and I was wondering if there would ever be an official one.
So thanks for reading my mind :)


Rich
On Fri, Jun 3, 2016 at 6:23 AM Gareth Rushgrove 
wrote:

> Hi All
>
> A few folks might have seen this yesterday, but just in case.
>
>
> https://puppet.com/blog/puppet-docker-running-puppet-container-centric-infrastructure
>
> I've been working on a set of Docker images for running Puppet
> software, so Puppet Server, PuppetDB, etc. The blog post above covers
> why and when this might be useful, but a few examples:
>
> * You want to run Puppet on something like CoreOS, PhotonOS or Atomic
> where containers are the defacto way of installing software
> * You want a full local development environment (including on WIndows
> or OSX) with minimal overhead
>
> The Dockerfiles and various build tools are available on GitHub:
>
> https://github.com/puppetlabs/puppet-in-docker
>
> And the images are available today on Docker Hub:
>
> https://hub.docker.com/u/puppet/
>
> We've also created a number of examples that show a few tips and
> tricks, including standing up the server stack using Docker compose:
>
> https://github.com/puppetlabs/puppet-in-docker-examples
>
> These are an experimental way of packaging up and releasing Puppet
> software intended for those people already familiar with Docker. We'd
> love any feedback about what you like and don't like, what you'd like
> to see in the future or anything vaguely related.
>
> And a quick thanks to all the people in the Puppet community who have
> rolled their own versions of this at some point or another. By having
> an official Puppet repo we're hoping that for the common case we can
> get everyone collaborating on a shared set of Dockerfiles/images, and
> that with many eyes come all the good ideas, but we want to make them
> a good starting point for advanced users too.
>
> Cheers
>
> Gareth
>
>
>
> --
> Gareth Rushgrove
> @garethr
>
> devopsweekly.com
> morethanseven.net
> garethrushgrove.com
>
> --
> 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 puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAFi_6yJiXCCBoBeZCB90oi9JGSCbVbirYrG2ha460L3aHgTsHg%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAPGcbtDYfcA5_hwxL%2BnhuygKfpcNDp-jd_3WT7UiRxjbq%2BiQig%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] PuppetDB Query based on facts