1

Puppet error when testing manifest

view story
linux-howto

http://serverfault.com – Prefix: I searched this out, but the fact that there are any number of things that can cause this problem, I have been unable to find a solution to this particular case. I have a puppet master (3.0.2-1; RHEL6) and the /etc/puppet/manifests/site.pp file contains the following: import 'nodes/nodes.pp' $puppetserver = 'puppet.example.dom' Naturally, the server domain is not what is in use, but has been changed to protect the innocent. The nodes/nodes.pp file contains: node 'agent1.example.dom' { include users, } The users class is under /etc/puppet/modules/users. The manifests/init.pp (HowTos)

xskl's picture
Submitted by xskl on 01/11/2013

Stories similar to Puppet error when testing manifest

puppet - missin openjdk-6-jdk 1 year 10 weeks ago

I am trying to run a script with puppet.

Quick brief - for testing purpose, I installed puppet agent on 5 nodes (Debian Squeeze + puppet 2.7.20-1puppetlabs1), and puppet master on 1 server (same version).

On puppetmaster side in every manifest I check if $::osfamily == 'Debian'.

So I am new to puppet and have been reading through a user guide to get better acquainted with he program. As a result I have been able to get some programs to install (i.e.

On our puppet box ( under the puppet/modules folder ) , I have added a module for installing a package. I then added the classes needed for the resources into the init.pp ( and other derived class files ) into the manifests folder.

I am new to Puppet and I'm trying to get Puppet to configure my EC2 instances after they're started from a Cloud Formation Template in AWS. The problem is that all the nodes that get started from the Cloud Formation Template all have the same name (the name from the AMI that the new nodes derive from).

I would love to find a way to have puppet rename the nodes when the nodes start up.

I am getting an error of err: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter port at /etc/puppet/manifests/nodes/node.pp:652 on node test-puppet

My puppet class: (The Line 652 at node.pp)

node 'test-puppet' { class { 'syslog_ng': host => "newhost", ip => "192.168.1.10", port => "1999", logfile => "/var/log/test

I am learning puppet and using this tool install puppet clients on nodes.

puppet node install --login=root --keyfile=~/.ssh/id_rsa --install-script puppet-enterprise --installer-payload ~/puppet/puppet-enterprise-2.7.0-ubuntu-12.04-amd64.tar.gz --installer-answers ~/puppet/installer.answers --puppetagent-certname puppet.node01.example.com 192.168.1.100

Everything seems to work ok.

I am trying to setup puppet's dashboard to be monitor the status of my servers. With the below shown configurations, my clients (or nodes) only show up as Unreported and says Has not reported in "Last report".

However the node can communicate with the server and pull changes as it's supposed to, but nothing appears in the dash.

Vagrant / puppet workflow 49 weeks 6 days ago

I'm new to puppet and vagrant, but I'm developing my own Puppet manifests intended to set up a vagrant box. That is, the puppet manifest is in my Vagrant directory on the host machine, and vagrant is invoking puppet -- there is no puppet server.

The thing is, my workflow is:

while(not working as desired) { vagrant destroy amend manifest vagrant up }

...