similar to: how do you test and release puppet changes?

Hello, we run Puppet Dashboard 1.2.23 in our sandbox and get an error deleting a node. - first time we press the delete button nothing happens - second time we press the delete button we get the following error; ActiveRecord::StatementInvalid in NodesController#destroy Mysql::Error: Lock wait timeout exceeded; try restarting transaction: DELETE FROM `node_group_memberships` WHERE `id` = 53

Hi, I am new to the job and forum. I installed puppet and puppetmaster and set up my first dependencies acording to a manual that we have here in our company. Everything works fine and I can set up new nodes with several modules to choose from. Unfortunatley the Dashboard <http://forge.puppetlabs.com/puppetlabs/dashboard>gives me errors instead of starting correctley. Here the

Hi, I have 51 clients in puppet-dashboard – and when I tell it to delete a node – it simply hangs forever. If I try to just open / on the puppet-dashboard website – I get a proxy timeout (I have apache in front). I end up having to kill webrick and start it again – with the node NOT being deleted :( I have commented on an issue here - which seems to be about the same:

Greetings, I have a tested, working setup of Puppet and Webrick. I can add nodes, classes, etc. Then I switched to Puppet/Passenger and get the error below. Puppet, Apache and Passenger are all up. I have installed using *YUM *repos and *GEMs*. So, I have the most updated packages they have. Puppet version: 2.7.19 Ruby version: 1.8.7 (2011-06-30 patchlevel 352 i386) Apache: 2.2.15 The error

puppet agent --verbose shows a verbose output of the changes done by puppet, such as: notice: /Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner: owner changed ''root'' to ''logstash'' notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed ''stopped'' to ''running''

** I installed PE Master on one VM and Agents on two VMs pointing to master . Agent1 VM 64 bit works fine , but agent2 VM 32 bit fails with below error. Only difference is architecture. One more note both the agent nodes were accepted from Dashboard,so master has both the certificates. Any help will be greatly appreciated. puppet-enterprise-3.1.0-el-6-i386]# puppet agent --test Info:

Hello, I have followed the documentation at http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html to try to setup dashboard but after I manually add a node it shows up as unreported. The agent has successfully completed a very basic catalog run just adding a file to the file-system. Dashboard v1.2 Puppet puppet-server.noarch 2.7.19-1.el6 SERVER: -bash-4.1$ cat

My install was working for a couple of months until I rebooted my puppet server. The clients do not report an error when I run puppet agent -t. I''ve attempted to remove certificates and renew. The clients get new certificates, but the console still does not update. Even the puppet server itself is not updating as a client. After reboot the only thing I have noticed that changed

I finally got around to installing PuppetDB and connecting it to my Master. I even set up Nginx to act as a reverse proxy, and I can make API calls like a pro. The dashboard is nice, but I''m anxious to get at least the same functionality that Puppet Dashboard gave me. Namely, a quick look at recent catalog changes or run failures (is this even possible, since PuppetDB

Hi, i''m a newbie about Puppet( 1 month ~) i got error on generate temp file, i''ll explain my situation: -i have a puppetmaster(version: 3.3.0),executed on root and a puppet agent(version 2.7) provisioning by vagrant,executed on root -my site.pp, where webserv is a parametrized class, and typews is a parameter to choice nginx or lamp module, -i have my Enc node with path

I''m running puppet on CentOS 6.3 x86_64: - facter.i386 1:1.6.12-2.el6 @puppet - puppet.noarch 2.7.19-1.el6 @puppet - ruby-shadow.x86_64 1.4.1-13.el6 @puppet Puppetmaster: - facter.x86_64 1:1.6.12-2.el6 @puppet - hiera.noarch 1.0.0-2.el6 @puppet - puppet.noarch 2.7.19-1.el6 @puppet -

Hi All, I have somehow managed to configure the puppet dashboard, but it is not displaying the nodes and the classes in the dashboard. It is completely empty. Any one has any idea of configuring puppet dashboard so that it displays all the nodes, classes, and reports/ I am newbie so please explain in a little brief. Regards Niraj K. -- You received this message because you are subscribed

>Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find terminus puppetsvr for indirection catalog I had a working puppet install (new) with 2 agents working well. I added puppet dashboard and the inventory part which is also working well. However, clients are talking to the server (putting info into dashboard inventory), but not pulling down the

Hi, I got the following error:- Error: Could not retrieve catalog from remote server: wrong header line format In puppet.conf file on puppetmaster, I added following lines - facts_terminus = inventory_active_record dbadapter = mysql dbname = dashboard dbuser = test dbpassword = test123 dbserver = puppet-master.com dbsocket =

trying to deploy puppetdb , puppet server is RHEL 6.1 , [root@puppet ~]# rpm -qa|grep puppet puppetdb-0.9.1-2.el6.noarch puppet-dashboard-1.2.9-1.el6.noarch puppet-server-2.7.17-1.el6.noarch puppetdb-terminus-0.9.1-2.el6.noarch puppet-2.7.17-1.el6.noarch on the clients, got an error for puppetdb , client1 :~ # puppet agent --test err: Could not retrieve catalog from remote server: Error 400

I want to setup a node using a three step process 1) download node requirements (git) 2) download modules to fit requirements (puppet) 3) Bring up the node in the required state (puppet) The second step is the one I am having trouble with. I want a file (master.pp) to list out all the modules and what versions are needed before applying the site.pp file. From what I have been able to find

Hello, Just kicking the tyres with PuppetDB (1.1.0) on a test setup with 100-odd nodes running only once an hour by default. Looking at the dashboard the catalog duplication is showing 0.0% which seems a little odd to me. Any way to track down why this is and how to correct it as presumably this is not desired behaviour. Cheers Paul -- You received this message because you are subscribed

Hello, I did make a stupid fault: not commiting changes to version control :-( After the installation of puppet-dashboard, I added a recipe to add report = true to puppet config files on clients. Now all Puppet clients don''t update because of an error... What can be the various reasons for an ''400'' error?? I guess it has something to do with rights. Jun 28 09:52:36 pm

I have a very basic puppet install right now, running puppet master, with the dashboard and foreman on the same host, I have some legacy static nodes (nodes.pp) and now I am using puppet to provision nodes in EC2. I am running cloud provisioner .60rc1 and my question is what happens after a puppet node bootstrap? I''m running into some issues and maybe its just idiot user driving this

I''m trying to setup dashboard as a node classifier w/puppet 2.6.14. Not sure why this is not working... In puppet.conf on the master I have: node_terminus = exec external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http:// localhost /usr/share/puppet-dashboard/bin/external_node The agent''s return: err: Could not retrieve catalog from remote server: Error 400 on SERVER: