similar to: Puppet dashboard - having cached catalog runs show up as warnings

Puppet Dashboard 1.2.23-rc3 is a maintenance release candidate of the 1.2 series of Puppet Dashboard with bug fixes and minor features. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.23-rc3.tar.gz Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For

Hi all, i planned for a startup to install one of this gui tools. But if i look in the documentation, or google it, i find no results which helps. If i would like to install the rpm package i get the following dependencies problems rpm -i puppet-dashboard-1.2.3-1.el6.noarch.rpm warning: puppet-dashboard-1.2.3-1.el6.noarch.rpm: Header V4 RSA/SHA1 signature: NOKEY, key ID 4bd6ec30 error: Failed

Hi, I just installed & configured puppet-dashboard as per the official documentation <http://docs.puppetlabs.com/dashboard/manual/1.2/>, but now my nodes cannot retrieve their catalog: [root@puppetnode-01 ~]# puppetd --debug --verbose --no-daemonize ... err: Could not retrieve catalog from remote server: Server hostname > ''puppetmaster-01.mydomain.com''

Puppet Dashboard 1.2.23 is a maintenance release of the 1.2 series of Puppet Dashboard with bug fixes and minor features. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.23.tar.gz Available in native package format in the Puppet Labs yum and apt repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Please report

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

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 puppet users, We''ve got a puppet (0.24.8) implementation with two environments, called production and testing. We''ve also got a Puppet Dashboard (1.0) instance up and running, which is receiving and displaying reports from hosts in both of the environments. We would like to start using the dashboard as an external node classification tool, so I''ve taken the example

Puppet Dashboard 1.2.15 is a bugfix release of the 1.2 series of Puppet Dashboard. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.15.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com Please report feedback via the Puppet Labs Redmine site, using an affected

Puppet Dashboard 1.2.13-rc1 is a maintenance and bugfix release candidate of Puppet Dashboard. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.13-rc1.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com See the Verifying Puppet Download section at:

This release of Puppet Dashboard addresses CVE-2013-0277 and CVE-2013-0269. These are vulnerabilities that affect Ruby on Rails, specifically around YAML serialization and JSON handling. They expose vulnerable systems to SQL Injection, Denial of Service Attacks, and arbitrary YAML deserialization. Additionally, CVE-2013-0276 and CVE-2013-0263 affect vendored components of Puppet Dashboard, but by

This is a maintenance release of Puppet Dashboard. This release resolves issues #7405, #9101, #8878, and #8803. More details below. This release is available for download at: http://downloads.puppetlabs.com/dashboard/ We have included Debian and RPM packages as well as a tarball. See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet

the puppetmaster conf file is: [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl reports = store, http, foreman reporturl = http://localhost:3000/reports/upload [agent] classfile = $vardir/classes.txt localconfig = $vardir/localconfig the puppet client conf file is: [main] logdir = /var/log/puppet rundir = /var/run/puppet

This is a maintenance release of Puppet Dashboard. It includes contributions from Adrien Thebo, Chad Metcalf, Chris W, Daniel Pittman, Daniel Sauble, Devon Harless, Michael Stahnke, Moses Mendoza, Randall Hansen, Josh Lifton, and Nick Fagerlund. This release is available for download at: http://downloads.puppetlabs.com/dashboard/ We have included Debian and RPM packages as well as a tarball

Welcome to the first Puppet Dashboard maintenance release of the new year. This release includes a security update to address CVE-2012-0891, a XSS vulnerability discovered by David Dasz <david@dasz.at>. We have classified the risk from this exposure as moderate. All Puppet Dashboard users are encouraged to upgrade when possible. Puppet Enterprise users should visit

This is a maintenance release of Puppet Dashboard. This release resolves issues #10198, #10270, and #10543. More details below. This release is available for download at: http://downloads.puppetlabs.com/dashboard/ We have included Debian and RPM packages as well as a tarball. See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet

Hello, I''m trying to get puppet-dashboard installed on a CentOS 6.3 machine running puppet v3.0.1. I''m following the puppet-dashboard documentation here: http://docs.puppetlabs.com/dashboard/manual/1.2/configuring.html In the documentation page linked above, it says: Puppet uses SSL certificates to control who can make requests to the puppet > master, so Dashboard has

Hi All, For some reason my puppet dashborad is not starting and new node requests are not displaying in dashboard. I am getting following error while restarting Puppet dashboard. root@PuppetMaster:/etc/puppetlabs/puppet/modules# /etc/init.d/pe-puppet-dashboard-workers start * Starting PE Puppet Dashboard Workers

Hi, I''m trying to switch my working puppet-dashboard installation over from the test server that it comes with to an Apache/Passenger setup. Puppet seems to be humming along just fine under this setup, but dashboard is unhappy. The web interface comes up with no style. I''ve taken a look with Safari''s developer windows at what it thinks is going on and I''m

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

Puppet Dashboard 1.2.13 is a maintenance and bugfix release of Puppet Dashboard. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.13.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com See the Verifying Puppet Download section at: