[Puppet Users] yum group install issue

[Jagga Soorma]

Hello,

This is a n00b question :)  I am trying to use the puppet-yum module from 
the forge (https://forge.puppet.com/puppet/yum) and have added the 
following to my yaml file:

--
classes:
  - yum

yum::group:
  'GNOME Desktop':
ensure: present
timeoute: 600
--

However, now when I do a puppet agent run I get the following error:

--
# puppet agent -t --noop
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Syntax error at 'Boolean'; expected ')' at 
/etc/puppet/environments/production/modules/yum/manifests/init.pp:99 on 
node node1
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
--

What am I missing here?  

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/2b5b82d6-af57-4607-9af4-7d613e405f10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: custom facts

[Michael Di Domenico]

On Thu, Apr 26, 2018 at 8:58 AM, jcbollinger  wrote:
> On Wednesday, April 25, 2018 at 12:05:18 PM UTC-5, Michael Di Domenico
> wrote:
>>
>> yes, that is true.  i want both facter and puppet to be able to find
>> my custom facts without having to specify an environment variable.
>
> But you're chasing the wrong objective.  You should not be using facter
> (directly) to evaluate custom facts provided by Puppet, at least with
> puppet5.  Instead, use puppet's 'facts' face:
>
> $ puppet facts
>
> That should, again, Just Work, regardless of whether you normally use
> 'puppet apply' or obtain catalogs from a master.

yes, that's likely true.  i'm still learning and i didn't build the
original environment, so change is hard and has to be slow, small
steps

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

Re: [Puppet Users] PuppetDB: manually import reports

[jcbollinger]

On Wednesday, April 25, 2018 at 6:22:39 AM UTC-5, Thomas Müller wrote:
>
>
>  
>>
>>>
>>> Another usecase could be to have a async puppetdb connection from the 
>>> second datacenter. If the connection between the datacenters is not  stable 
>>> enough to use a single puppetdb I would need to add a puppetdb per DC.Then 
>>> I also would want to sync data to the central puppetdb instance.
>>>
>>>
>> Is that an *actual* use case or a hypothetical one?
>>
>> I'm just thinking what my options are if it the datacenter link is not 
> stable enough. I'm not investing time to create a solution.
>
> I've thought a bit longer about the "importing reports". it's not just 
> importing reports, it's also importing facts and importing catalogs to the 
> central db. Overall I think this really would require much time to 
> implement the tooling. Maybe then it will be easier to query 2 puppetdb's 
> instead of syncing everything to one. 
>
> But maybe all works out fine and no hacking will be necessary. :)
>
>
There are Postgres-level tools for database federation and 
synchronization.  As I already suggested, something along those lines is 
probably worth your consideration as a mechanism for the actual data 
movement.  The other question to consider is how to structure the data so 
that it even makes sense to combine them at all, and again, at a bare 
minimum, your various participating masters should rely on a common CA.  To 
a good approximation, the CA identity is the site identity, and it does not 
make much sense to combine data from different sites in the same database.


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/feed1ef2-7f3e-40a0-8cb4-ef7532ee4813%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: custom facts

[jcbollinger]

On Wednesday, April 25, 2018 at 12:05:18 PM UTC-5, Michael Di Domenico 
wrote:
 

> yes, that is true.  i want both facter and puppet to be able to find 
> my custom facts without having to specify an environment variable. 
>

But you're chasing the wrong objective.  You should not be using facter 
(directly) to evaluate custom facts provided by Puppet, at least with 
puppet5.  Instead, use puppet's 'facts' face:

$ puppet facts

That should, again, Just Work, regardless of whether you normally use 
'puppet apply' or obtain catalogs from a master.


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/a7965ec0-796c-4d81-b7cf-03a4067879e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: custom facts

[Thomas Müller]

Am Mittwoch, 25. April 2018 16:01:00 UTC+2 schrieb Michael Di Domenico:
>
> i'm upgrading from puppet 3 (via epel) to puppet 5 (via puppetlabs), 
> i'm confused on how/if there's a way to get custom ruby facts to load 
> into facter without having to specify FACTERLIB.  i'll admit i might 
> have missed something in the  documentation 
>
> in the past i'd copy my ruby facts into 
> /usr/share/ruby/vendor_ruby_facter (which probably wasnt right), and 
> everytime I ran facter it would autoload my facts, no need for 
> switches to env variables 
>
> there is a /opt/puppetlabs/puppet/lib/ruby/vendor_ruby, but when i 
> copy my facts into there they don't load 
>
> what's the right way to do this? 
>

what are your "custom facts" ? Custom facts in modules get automatically 
synced to the puppet agent or for puppet apply.

If you manage your facts yourself and not by modules you might configure 
the custom-dir within the facter.conf 
https://puppet.com/docs/facter/3.11/configuring_facter.html 

- Thomas

 

-- 
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/d903ff0d-da42-4ad3-ac4d-7d222e95bc6c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Getting error on all puppet agents-please help me

[Thomas Müller]

Am Mittwoch, 25. April 2018 16:01:25 UTC+2 schrieb raja gopal:
>
> This is log details where i got from one of the puppet agent, but i didn't 
> get any log from /var/log/puppet.log from puppet master.
>
>
>
>
> Apr 24 23:46:39 lx-cmlive9 puppet-agent[3312]: Finished catalog run in 
> 993.17 seconds
> Apr 25 00:04:03 lx-cmlive9 puppet-agent[3312]: Finished catalog run in 
> 988.27 seconds
> Apr 25 00:18:14 lx-cmlive9 puppet-agent[3312]: Finished catalog run in 
> 787.23 seconds
> Apr 25 00:30:01 lx-cmlive9 puppet-agent[3312]: Caught TERM; calling stop
> Apr 25 00:30:01 lx-cmlive9 puppet-agent[1802]: Reopening log files
> Apr 25 00:30:01 lx-cmlive9 puppet-agent[1802]: Starting Puppet client 
> version 2.7.26
>

really Puppet 2.7.26? 

last update of puppet 2.7 was in 2014.
 

> Apr 25 00:30:01 lx-cmlive9 puppet-agent[1802]: Run of Puppet configuration 
> client already in progress; skipping
>

I would:

* check if there is some hung agent in the background and kill it
* verify if the agent_catalog_run_lockfile exists, if it is remove it 
(puppet agent --configprint agent_catalog_run_lockfile (really don't know 
if puppet 2.7 supports this)).
* restart the service

- Thomas


 

>
>
> Kindly help me to resolve it..
>
> Thanks a lot.
>

-- 
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/a4a8f1ec-e8a1-4f8b-94a2-b3932da9fefa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.