I have built a new Puppet master to test Puppet 4. I have installed the
server itself and used r10k to put my code on the server but when doing a
puppet client run on the master I get this error:
root@puppet:~# puppet agent -t
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading fa
Wow, thanks for the quick reply. I looked through the shell scripts, but by
the very fact that they are shell scripts, it's clear that they are only
for running on the server (the VM). Does your code do anything on the *host
computer*? The Puppet folks seem to think that I have to install the .m
Hmm, perhaps more of the lights are coming on for me, after conferring
briefly with the creator of PuPHPet. Here is a question I have not asked
before, because I thought I knew: Which machine is the Puppet "agent" to be
installed and run on?
1. The server that is being provisioned? (in my ca
Hi,
I have been running for a few weeks puppet 3.7.5 + puppetserver 1.0.2
with the future parser enabled and stringify_facts disabled. I had to
do some minor fixing to get everything to work (mostly due to facts
type change), but it went overall quite well.
Now I have decided to take the next ste
Hi Allan
>
> I see that it's possible to use the MySql module to create users and
> manage grants. And, it's also possible to have Puppet authenticate against
> Active Directory.
>
What do you mean by "authenticate puppet against active directory"?
>
> I'm not seeing a simple way to bridge
On Wednesday, 20 May 2015 11:52:06 UTC+1, Matthias Saou wrote:
>
> I will post followups if
> anyone is interested.
>
>
Count me interested - I'm in the same pre-leap state (3.7 with all the
future features enabled) and looking at 4, so I'm keen to hear all the
details.
--
You received this
Am Mittwoch, 20. Mai 2015 07:15:07 UTC+2 schrieb Vincent Weathers:
>
> This may have been asked before, but I'm having problems clearing out
> nodes from puppetdb.
>
> Some background info:
>
> OS:
>
> [root@puppet-sys puppet]# cat /etc/redhat-release
> Scientific Linux release 6.6 (Carbon)
>
>
Am Mittwoch, 20. Mai 2015 10:31:14 UTC+2 schrieb Danny Roberts:
>
> I have built a new Puppet master to test Puppet 4. I have installed the
> server itself and used r10k to put my code on the server but when doing a
> puppet client run on the master I get this error:
>
> root@puppet:~# puppet a
On Wed, 20 May 2015 03:57:50 -0700 (PDT)
Nick Howes wrote:
> On Wednesday, 20 May 2015 11:52:06 UTC+1, Matthias Saou wrote:
> >
> > I will post followups if
> > anyone is interested.
> >
> >
> Count me interested - I'm in the same pre-leap state (3.7 with all
> the future features enabled) and
On Wednesday, 20 May 2015 13:22:37 UTC+1, Matthias Saou wrote:
>
>
> Next, the very cryprtic "undefined method `key_attributes' for
> nil:NilClass" message is apparently caused by the change of having
> empty arrays now evaluate to true. This is the fix I came up with :
>
>
> https://github.co
> Does your code do anything on the *host computer*?
No, everything that happens, happens inside the VM. You only need Vagrant
and your virtualizer of choice (Virtualbox, Vmware, Parallels).
On Wednesday, May 20, 2015 at 3:58:13 AM UTC-5, Karen Ellrick wrote:
>
> Wow, thanks for the quick repl
Dear all,
I've installed wdijkerman/zabbix module in puppet server.
Now I've been modifying its conf in hiera :
zabbix::zabbix_url: 'zabbix.linux.crg.es'
zabbix::zabbix_version: '2.2'
zabbix::manage_repo: 'false'
But seems that the module is ignoring those parameters.
I've to modify them in zab
Hello,
I try to customize my http vhost template and defined and array of ip
addresses in the manifests:
class apache::webservice(
$htdocs = $apache::param::htdocs,
$apacheuser = $apache::param::apacheuser,
$apachegroup = $apache::param::apachegroup,
$logdir = $apache::param::logdir,
) i
On Wed, 20 May 2015 15:06:57 +0200
Arnau Bria wrote:
Hello,
me again with answer to both problems :-)
> Now I've been modifying its conf in hiera :
>
> zabbix::zabbix_url: 'zabbix.linux.crg.es'
> zabbix::zabbix_version: '2.2'
> zabbix::manage_repo: 'false'
>
> But seems that the module is igno
Yep, use descr => 'blah' instead of name => 'blah'
On Friday, 4 December 2009 18:50:31 UTC, Bryan Schneiders wrote:
>
> I'm using puppet-0.24.8-4.el5 on CentOS 5.4.
>
> My problem is yumrepo isn't writing the "name=" field to the
> repository files which causes yum to complain with the error:
Hi people,
I'm instalation puppet in server01 and the foreman-proxy and the server02
instalation the foreman server.
My problem is not pupulate the hosts in foreman server and i not see debug
connections between server.
My instalation for module the puppet "theforeman-foreman_proxy"
Help me ple
Hi,
I have setup Vagrant to provision with puppet_server. I have an independent
VM in VirtualBox that acts as the puppet server and my puppet code is on
that machine.
When I vagrant up a client VM, it runs puppet fine and executes my puppet
code and provisions as expected my client VM.
But if
>
>
> IMHO it can't find any "classes" keys and as "undef" handling changed in
> 4.0 it now throws an error.
>
> If it should return values: what if you run the hiera command from
> command line ? something like:
>
>
> hiera --debug --array classes undef topscopevar1=value topscopevar2=val
I wanted to use the puppetdb api to be able to sniff out some various
anomalies that the console doesn't easily show me. I wanted to do this via
powershell because I know it better than bash or Python or whatever
language smarter folks than me would use. I had to wade through some
poorly docu
On Wed, May 20, 2015 at 4:35 AM, Karen Ellrick
wrote:
> Hmm, perhaps more of the lights are coming on for me, after conferring
> briefly with the creator of PuPHPet. Here is a question I have not asked
> before, because I thought I knew: Which machine is the Puppet "agent" to be
> installed and r
Hi, Puppet 4.1 and Facter 2.4.4 have been released and rolled up into a new
Puppet Agent All-in-One package (puppet-agent-1.1.0).
Puppet 4.1.0 is a feature release in the Puppet 4 series. This release's main
focus was improvements to the Puppet language, but it also includes some
improvements t
I finally figured out what this was. In my puppetmaster's
/etc/puppet.conf
file, I needed to declare
certname = puppet-sys
in the [main], [master], and [agent] sections.
We do not use FQDN's in our puppet environment due to weird DNS stuff. So,
we use the shortnames only. PuppetDB was not ab
Reading the puppet 4.1.0 releasenotes there is some bugfix for hiera_include
included: https://tickets.puppetlabs.com/plugins/servlet/mobile#issue/PUP-4334
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop
23 matches
Mail list logo
