Re: [Puppet Users] Puppet MultiMaster open source

[Christopher Wood]

https://docs.puppet.com/puppetserver/2.2/external_ca_configuration.html#disabling-the-internal-puppet-ca-service

I use that line and have puppetized builds for puppetmasters anyway. Albeit 
that setting the Subject Alternative Name for the outside of the load balancer 
takes slightly more effort than signing a cert for a standard puppetmaster.

https://docs.puppet.com/guides/scaling_multiple_masters.html#before-running-puppet-agent-or-puppet-master

On Wed, Apr 20, 2016 at 07:50:04PM +0200, Geoff Galitz wrote:
>Thanks for the replies... any pointers on setting up puppet servers as
>compile masters?
>-G
>On Wed, Apr 20, 2016 at 5:12 PM, Kevin Corcoran
><[1]kevin.corco...@puppet.com> wrote:
> 
>  On Wed, Apr 20, 2016 at 5:58 AM, Geoff Galitz
>  <[2]ggal...@shutterstock.com> wrote:
> 
>Is it possible to get compile master, master of master and code
>manager (file sync) working in the open source versions?
> 
>  Code manager and file sync are only available as part of Puppet
>  Enterprise.  I believe the standard alternative is to run r10k directly
>  on each master.
> 
>  --
>  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 [3]puppet-users+unsubscr...@googlegroups.com.
>  To view this discussion on the web visit
>  
> [4]https://groups.google.com/d/msgid/puppet-users/CAF-bMBeJ8%3DJ3tP7uBP4C3sugoEr6hdhugHmkzHUN_g5oFTkvxQ%40mail.gmail.com.
>  For more options, visit [5]https://groups.google.com/d/optout.
> 
>--
>Geoff Galitz, Systems Engineer
>Shutterstock GmbH
>Greifswalder Strasse 212
>Aufgang F, 2 Hof
>10405 Berlin
> 
>--
>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 [6]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [7]https://groups.google.com/d/msgid/puppet-users/CABiayTDyM%3DMzsbc1HAmKqzy12-eqmuxfH%2B-VjK_JxBNCLi%3DrDA%40mail.gmail.com.
>For more options, visit [8]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:kevin.corco...@puppet.com
>2. mailto:ggal...@shutterstock.com
>3. mailto:puppet-users+unsubscr...@googlegroups.com
>4. 
> https://groups.google.com/d/msgid/puppet-users/CAF-bMBeJ8%3DJ3tP7uBP4C3sugoEr6hdhugHmkzHUN_g5oFTkvxQ%40mail.gmail.com?utm_medium=email_source=footer
>5. https://groups.google.com/d/optout
>6. mailto:puppet-users+unsubscr...@googlegroups.com
>7. 
> https://groups.google.com/d/msgid/puppet-users/CABiayTDyM%3DMzsbc1HAmKqzy12-eqmuxfH%2B-VjK_JxBNCLi%3DrDA%40mail.gmail.com?utm_medium=email_source=footer
>8. 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/20160420221439.GA4270%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet MultiMaster open source

[Geoff Galitz]

Thanks for the replies... any pointers on setting up puppet servers as
compile masters?

-G



On Wed, Apr 20, 2016 at 5:12 PM, Kevin Corcoran 
wrote:

> On Wed, Apr 20, 2016 at 5:58 AM, Geoff Galitz 
> wrote:
>
>> Is it possible to get compile master, master of master and code manager
>> (file sync) working in the open source versions?
>>
>
> Code manager and file sync are only available as part of Puppet
> Enterprise.  I believe the standard alternative is to run r10k directly on
> each master.
>
> --
> 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/CAF-bMBeJ8%3DJ3tP7uBP4C3sugoEr6hdhugHmkzHUN_g5oFTkvxQ%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 


Geoff Galitz, Systems Engineer
Shutterstock GmbH
Greifswalder Strasse 212
Aufgang F, 2 Hof
10405 Berlin

-- 
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/CABiayTDyM%3DMzsbc1HAmKqzy12-eqmuxfH%2B-VjK_JxBNCLi%3DrDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppetlabs-release not signed

[Rick Sherman]

Hi chrido,

I'm trying to reproduce the issue you saw.

Could you please provide the Puppet related output of 
apt-key finger

Thank you,
Rick Sherman
Release Engineering, Puppet

On Wednesday, April 20, 2016 at 9:55:04 AM UTC-5, chrido wrote:
>
> Similiar problems with apt:
> W: GPG error: http://apt.puppetlabs.com wily Release: The following 
> signatures were invalid: BADSIG 1054B7A24BD6EC30 Puppet Labs Release Key 
> (Puppet Labs Release Key) 
> There is a new pubkey in http://apt.puppetlabs.com/, are you changing the 
> key?
>
> On Wednesday, April 20, 2016 at 3:25:41 PM UTC+2, kbrede wrote:
>>
>> I'm getting the same for:
>>
>> Package puppetlabs-release-5-12.noarch.rpm is not signed
>> Package puppetlabs-release-6-12.noarch.rpm is not signed
>> Package puppetlabs-release-7-12.noarch.rpm is not signed
>>
>>
>>
>> Kenton Brede
>>
>>
>>
>>
>>
>> On Wed, Apr 20, 2016 at 4:11 AM, Jonathan Gazeley <
>> jonathan...@bristol.ac.uk> wrote:
>>
>>> This morning I noticed on yum.puppetlabs.com that 
>>> puppetlabs-release-6-12.noarch.rpm and puppetlabs-release-7-12.noarch.rpm 
>>> are not signed (possibly others too, I didn't check). My yum cron job is 
>>> bitching about it because I don't allow unsigned packages.
>>>
>>> Is this a mistake?
>>>
>>> Thanks,
>>> Jonathan
>>>
>>> -- 
>>> Jonathan Gazeley
>>> Senior Systems Administrator
>>> IT Services
>>> University of Bristol
>>>
>>> -- 
>>> 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/571747B7.1020908%40bristol.ac.uk
>>> .
>>> 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/3a53984e-c695-42e2-b617-ea4e954d6db8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet MultiMaster open source

[Kevin Corcoran]

On Wed, Apr 20, 2016 at 5:58 AM, Geoff Galitz 
wrote:

> Is it possible to get compile master, master of master and code manager
> (file sync) working in the open source versions?
>

Code manager and file sync are only available as part of Puppet
Enterprise.  I believe the standard alternative is to run r10k directly on
each master.

-- 
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/CAF-bMBeJ8%3DJ3tP7uBP4C3sugoEr6hdhugHmkzHUN_g5oFTkvxQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppetlabs-release not signed

[Melissa Stone]

Thanks for reporting this, everyone. I've fixed the packages on
yum.puppetlabs.com, and I'll start investigating apt.puppetlabs.com now.

On Wed, Apr 20, 2016 at 7:55 AM chrido  wrote:

> Similiar problems with apt:
> W: GPG error: http://apt.puppetlabs.com wily Release: The following
> signatures were invalid: BADSIG 1054B7A24BD6EC30 Puppet Labs Release Key
> (Puppet Labs Release Key) 
> There is a new pubkey in http://apt.puppetlabs.com/, are you changing the
> key?
>
> On Wednesday, April 20, 2016 at 3:25:41 PM UTC+2, kbrede wrote:
>
>> I'm getting the same for:
>>
>> Package puppetlabs-release-5-12.noarch.rpm is not signed
>> Package puppetlabs-release-6-12.noarch.rpm is not signed
>> Package puppetlabs-release-7-12.noarch.rpm is not signed
>>
>>
>>
>> Kenton Brede
>>
>>
>>
>>
>>
>> On Wed, Apr 20, 2016 at 4:11 AM, Jonathan Gazeley <
>> jonathan...@bristol.ac.uk> wrote:
>>
> This morning I noticed on yum.puppetlabs.com that
>>> puppetlabs-release-6-12.noarch.rpm and puppetlabs-release-7-12.noarch.rpm
>>> are not signed (possibly others too, I didn't check). My yum cron job is
>>> bitching about it because I don't allow unsigned packages.
>>>
>>> Is this a mistake?
>>>
>>> Thanks,
>>> Jonathan
>>
>>
>>>
>>> --
>>> Jonathan Gazeley
>>> Senior Systems Administrator
>>> IT Services
>>> University of Bristol
>>>
>>> --
>>> 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/571747B7.1020908%40bristol.ac.uk
>>> .
>>> 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/c4837b1a-c2bd-4e73-9552-3306b28c4594%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Melissa Stone
Release Engineer, Puppet Labs
--

PuppetConf 2016 , October 17-21, San Diego,
California
*Early Birds save $350*

-
Register by June 30th

-- 
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/CAHEe_kqeXhUV3aHxCe-1qosK%2BqjL_%2BoNqfXUFWGvcxv5567rUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppetlabs-release not signed

[chrido]

Similiar problems with apt:
W: GPG error: http://apt.puppetlabs.com wily Release: The following 
signatures were invalid: BADSIG 1054B7A24BD6EC30 Puppet Labs Release Key 
(Puppet Labs Release Key) 
There is a new pubkey in http://apt.puppetlabs.com/, are you changing the 
key?

On Wednesday, April 20, 2016 at 3:25:41 PM UTC+2, kbrede wrote:
>
> I'm getting the same for:
>
> Package puppetlabs-release-5-12.noarch.rpm is not signed
> Package puppetlabs-release-6-12.noarch.rpm is not signed
> Package puppetlabs-release-7-12.noarch.rpm is not signed
>
>
>
> Kenton Brede
>
>
>
>
>
> On Wed, Apr 20, 2016 at 4:11 AM, Jonathan Gazeley <
> jonathan...@bristol.ac.uk > wrote:
>
>> This morning I noticed on yum.puppetlabs.com that 
>> puppetlabs-release-6-12.noarch.rpm and puppetlabs-release-7-12.noarch.rpm 
>> are not signed (possibly others too, I didn't check). My yum cron job is 
>> bitching about it because I don't allow unsigned packages.
>>
>> Is this a mistake?
>>
>> Thanks,
>> Jonathan
>>
>> -- 
>> Jonathan Gazeley
>> Senior Systems Administrator
>> IT Services
>> University of Bristol
>>
>> -- 
>> 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/571747B7.1020908%40bristol.ac.uk
>> .
>> 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/c4837b1a-c2bd-4e73-9552-3306b28c4594%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Strategies for "boring" packages

[Dirk Heinrichs]

Am 19.04.2016 um 02:47 schrieb J.T. Conklin:

> What strategies do you use for "boring" modules so you're not
> overwhelmed by hundreds of small boilerplate modules?

I use a simple module with one class for mass-installing packages and
another one for mass-uninstalling, like:

class linux_base::install ($packages = undef) {
  $packages.each |String $pkg| {
package { $pkg: ensure => latest, }
  }
}

where $packages is an array of package names (strings), which can easily
be provided for each (group of) host(s) via Hiera.

The ::uninstall class has "purge" instead of "latest". Of course, input
array for both classes must be mutually exclusive, if both are used at
the same time.

HTH...

Dirk
-- 

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.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/57178BA2.6020801%40recommind.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Strategies for "boring" packages

[jcbollinger]

On Monday, April 18, 2016 at 8:07:34 PM UTC-5, J.T. Conklin wrote: 

> So I throw the question to the puppet community... What strategies do 
> you use for "boring" modules so you're not overwhelmed by hundreds of 
> small boilerplate modules? 
>
>

Although it's orthogonal to the question, whether you create separate 
modules for group things together into large collection modules, you could 
look to the Example42 Tiny Puppet module  to 
minimize your boilerplate.  That is its express purpose.  I don't have 
enough information to determine how well it actually would meet your needs, 
but it's certainly worth a look.  If indeed it succeeds in cutting your 
"boring" modules to a few lines of code then that might change the equation 
for you.


John

-- 
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/34aa5ab4-cfad-424f-ba67-60218104fdf0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Patterns for multi-arch libraries...

[jcbollinger]

On Tuesday, April 19, 2016 at 11:07:07 AM UTC-5, J.T. Conklin wrote:
>
> Rob Nelson  writes: 
> > Silly question, but what package manager doesn't let you upgrade those 
> > two packages independently but also doesn't update the dependent 
> > packages at the same time? 
>
> We have this problem on CentOS machines using the yum provider. The logs 
> reported something to the effect of openssl.x86_64 couldn't be updated 
> to version N+1 as that conflicted with openssl.i686 version N.  I wish 
> I had saved the logs at the time so I could share the exact text with 
> you all.
>


Yes, yum can be configured so that it forces co-installed 32-bit and 64-bit 
versions of the same package to have the same epoch:version-release, and 
that option ('protected_multilib') is enabled by default.  You could 
consider disabling it in your yum.conf, which, of course, Puppet could help 
you do.  That does not override general conflict detection, however, which 
could still be in play, nor normal dependency resolution.  And, really, 
having mismatched library versions seems a little dubious to me, but 
perhaps allowing it as a transitory state would make for smoother 
integration with Puppet.

It is conceivable that you would benefit from setting yum's 'multilib_policy' 
option to 'all' to automatically install all available architectures of 
each package, instead of, by default, only the one that best matches the 
machine architecture.  The former was the default configuration in EL5, 
whereas the latter became the default in EL6.  I don't think that will 
directly address your current problem, but it, too, might make for smoother 
integration.

As an ongoing concern, if you have multiple architectures of the same 
package installed on a given system, then yum commands that give the 
package name but no arch will affect all packages of that name.  Thus, 
updating just 'openssl' will update all installed arches of that package, 
whereas updating (or installing) 'openssl.x86_64' is specific to that arch 
of the package.  And that's where you're running into trouble.  Puppet's 
package providers manage a single package at a time (as it appears to 
them).  In your case, then, even though you're managing both openssl.x86_64 
and openssl.i686, Puppet attempts to perform a separate install / update 
for each.  The separate installs work, but separate updates do not.  You 
need to update both arches in the same yum run (supposing that 
protected_multilib is enabled), and the only way to do that in Puppet is to 
leave the arch off the package name.


John

-- 
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/39e43216-c6da-481e-af56-58b31f1cd7b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppetlabs-release not signed

[Kenton Brede]

I'm getting the same for:

Package puppetlabs-release-5-12.noarch.rpm is not signed
Package puppetlabs-release-6-12.noarch.rpm is not signed
Package puppetlabs-release-7-12.noarch.rpm is not signed



Kenton Brede





On Wed, Apr 20, 2016 at 4:11 AM, Jonathan Gazeley <
jonathan.gaze...@bristol.ac.uk> wrote:

> This morning I noticed on yum.puppetlabs.com that
> puppetlabs-release-6-12.noarch.rpm and puppetlabs-release-7-12.noarch.rpm
> are not signed (possibly others too, I didn't check). My yum cron job is
> bitching about it because I don't allow unsigned packages.
>
> Is this a mistake?
>
> Thanks,
> Jonathan
>
> --
> Jonathan Gazeley
> Senior Systems Administrator
> IT Services
> University of Bristol
>
> --
> 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/571747B7.1020908%40bristol.ac.uk
> .
> 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/CA%2BnSE39-n7krpKMxQ8Bxi6pF_EhPz%3DwG2X3ba%2BLe7dZDbhgYXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Hiera Error 400 on SERVER: Could not find data item classes in any Hiera data file and no default supplied

[Ugo Bellavance]

On Wednesday, April 20, 2016 at 9:03:35 AM UTC-4, jcbollinger wrote:
>
>
>
> On Tuesday, April 19, 2016 at 12:36:47 PM UTC-5, Ugo Bellavance wrote:
>
> This:
>  
>
>> When debugging on the master:
>>
>> # puppet master --debug --compile agent1.example.com | grep hiera | grep 
>> -v Cannot | grep -v Looking
>> [...]
>> Debug: hiera(): Hiera YAML backend starting
>> Debug: hiera(): Found classes in host/agent1.example.com
>> [...]
>>
>
>
> Shows that your Hiera config and data are fine.
>
> You haven't presented any logs of the actual puppetmaster service failure, 
> and these might be more illuminating, but at this point I'm inclined to 
> guess that your problem is one of two things:
>
>1. perhaps the master is running with a stale Hiera config, and needs 
>to be restarted to see the up-to-date one, or
>2. access controls on one or more of the Hiera data files prevent the 
>puppetmaster process from reading them.
>
> I'd rate the latter as somewhat more likely.
>

Here are the logs on the puppet master (please note that I don't use the 
fileserver anymore and as you can see, I restarted the master just before 
testing):

Apr 20 09:08:51 master puppet-master[26083]: Starting Puppet master version 
3.6.2
Apr 20 09:09:27 master puppet-master[26083]: Removing mount "files": 
/var/lib/puppet/files does not exist or is not a directory
Apr 20 09:09:27 master puppet-master[26083]: Error parsing fileserver 
configuration: wrong number of arguments (3 for 0..1); using old 
configuration
Apr 20 09:09:31 master puppet-master[26083]: The use of 'import' is 
deprecated at /etc/puppet/manifests/site.pp:4. See 
http://links.puppetlabs.com/puppet-import-deprecation
Apr 20 09:09:31 master puppet-master[26083]:   (at grammar.ra:610:in `block 
in _reduce_190')
Apr 20 09:09:32 master puppet-master[26083]: Could not find data item 
classes in any Hiera data file and no default supplied at 
/etc/puppet/manifests/site.pp:12 on node 
agent1.atqlan.agri-tracabilite.qc.ca
Apr 20 09:09:32 master puppet-master[26083]: Could not find data item 
classes in any Hiera data file and no default supplied at 
/etc/puppet/manifests/site.pp:12 on node agent1
.atqlan.agri-tracabilite.qc.ca
Apr 20 09:09:32 master puppet-master[26083]: Could not find data item 
classes in any Hiera data file and no default supplied at 
/etc/puppet/manifests/site.pp:12 on node agent1
.atqlan.agri-tracabilite.qc.ca
 

-- 
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/06b16b12-6ead-4a7e-80de-169560fc3b18%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Hiera Error 400 on SERVER: Could not find data item classes in any Hiera data file and no default supplied

[jcbollinger]

On Tuesday, April 19, 2016 at 12:36:47 PM UTC-5, Ugo Bellavance wrote:

This:
 

> When debugging on the master:
>
> # puppet master --debug --compile agent1.example.com | grep hiera | grep 
> -v Cannot | grep -v Looking
> [...]
> Debug: hiera(): Hiera YAML backend starting
> Debug: hiera(): Found classes in host/agent1.example.com
> [...]
>


Shows that your Hiera config and data are fine.

You haven't presented any logs of the actual puppetmaster service failure, 
and these might be more illuminating, but at this point I'm inclined to 
guess that your problem is one of two things:

   1. perhaps the master is running with a stale Hiera config, and needs to 
   be restarted to see the up-to-date one, or
   2. access controls on one or more of the Hiera data files prevent the 
   puppetmaster process from reading them.

I'd rate the latter as somewhat more likely.


John

-- 
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/dfb61c5b-56cc-47ad-8ca7-9d163f3622f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet MultiMaster open source

[Geoff Galitz]

Hi...

Is it possible to get compile master, master of master and code manager
(file sync) working in the open source versions?  Specifically:

puppetserver-2.3.1-1.el7.noarch
puppetlabs-release-pc1-1.0.0-1.el7.noarch

Or are there pointers to get similar functionality via the open source
packages?

-G





-- 


Geoff Galitz, Systems Engineer
Shutterstock GmbH
Greifswalder Strasse 212
Aufgang F, 2 Hof
10405 Berlin

-- 
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/CABiayTAACGByEk9kEzCddLdWHNkBzdhcLr%2Btg32ATCD4%3D9OruQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera Error 400 on SERVER: Could not find data item classes in any Hiera data file and no default supplied

[Ugo Bellavance]

On Wednesday, April 20, 2016 at 7:45:13 AM UTC-4, Peter Faller wrote:
>
> Ugo, I think you need:
>
> classes:
>   - ntp
>
> ... instead of:
>
> classes: ntp
>
> ... to make 'classes' an array instead of a simple value.
>

Tried it but I get the same result.  I think that both work, the array 
being needed when one than one class is needed here.

I guess that the next step will be to try with the latest Puppet 3...

Thanks,

-- 
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/4c8d8fb9-38c1-46fe-aefb-8a7492b6dcea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera Error 400 on SERVER: Could not find data item classes in any Hiera data file and no default supplied

[Peter Faller]

Ugo, I think you need:

classes:
  - ntp

... instead of:

classes: ntp

... to make 'classes' an array instead of a simple value.

-- 
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/bbf2e4fe-e9da-40ef-832e-aabde1bbed14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppetlabs-release not signed

[Artur Gadelshin]

Hello. It brokes beaker tests either.

2016-04-20 12:11 GMT+03:00 Jonathan Gazeley 
:

> This morning I noticed on yum.puppetlabs.com that
> puppetlabs-release-6-12.noarch.rpm and puppetlabs-release-7-12.noarch.rpm
> are not signed (possibly others too, I didn't check). My yum cron job is
> bitching about it because I don't allow unsigned packages.
>
> Is this a mistake?
>
> Thanks,
> Jonathan
>
> --
> Jonathan Gazeley
> Senior Systems Administrator
> IT Services
> University of Bristol
>
> --
> 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/571747B7.1020908%40bristol.ac.uk
> .
> 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/CAAPADrx%2BfpA2M8ZmcoAcfPiX06v3YZTmTS_nym6fDsHC7sgeeQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppetlabs-release not signed

[Jonathan Gazeley]

This morning I noticed on yum.puppetlabs.com that 
puppetlabs-release-6-12.noarch.rpm and 
puppetlabs-release-7-12.noarch.rpm are not signed (possibly others too, 
I didn't check). My yum cron job is bitching about it because I don't 
allow unsigned packages.


Is this a mistake?

Thanks,
Jonathan

--
Jonathan Gazeley
Senior Systems Administrator
IT Services
University of Bristol

--
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/571747B7.1020908%40bristol.ac.uk.
For more options, visit https://groups.google.com/d/optout.