similar to: Puppet Dashboard stuff

After upgraded to puppet-dashboard 1.04, when I click links to check information of nodes or groups , such as http://localhost:3001/nodes/22, it return a "We''re sorry, but something went wrong." to me. Checking the log, i got something as follows: ActionView::TemplateError (undefined method `<=>'' for #<NodeGroup id: 5, name:"Web_Marketing">) on

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

I have puppet running on WEBrick. Dashboard works. I can see the hosts currently in puppet. In Dashboard I can add hosts and create groups, but cannot add classes. The auto-search returns nothing when I click on a group or server and start typing in the Classes textbox. Is this a common occurrence with Dashboard? I have looked on the web and found no answer. Appreciate any pointers. Thanks.

I''m using puppet-dashboard 1.1.0-1 on Ubuntu. I remove old reports using this command: nice -n +1 rake RAILS_ENV=production reports:prune upto=1 unit=mon This seems to work fine, and the amount of reports returnd by this mysql query seems to drop by the proper amount: select count(*) from reports; Right now it returns a value of 12591. So far so good. The problem is the

I''m currently running a dashboard as a separate process and have a proxy in apache with authentication to access as http://puppet.ourhost.com/dashboard/ I have to start the dashboard with "-P /dashboard" option to make it work. I''m wondering how to achieve this with passenger. The config I found in ext/passanger seems to run the dashboard under the root of the virtual

Hello Puppet Users ! We encounter a problem with the dashboard on this URI : /reports/changed The /reports works fine with ~130000 reports (up to 3 months and auto-cleaning with rake reports:prune job) I make a reports:prune:orphaned, juste in case, but without any success. The most recent change on the server was the puppetmaster upgrade from 3.0.2 to 3.1.0. Here is the dashboard error log

Hey All, I see that a number of Admins have experienced this same issue, but no one has posted a workable solution. I have about 200 agents, but on any given day I''ll see 5-10 failed tasks in Dashboard as follows: *Importing report report-21248-180.yaml* at 10-18-2013 11:10 EDTValidation failed: Host already has a report for time and kind Backtrace

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

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:

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

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

Dear All, I already deploy puppet-dashboard with passanger. i''m want to try puppet-dasboard work in like myserver.com/puppet-report using apache proxy reverse, but still getting work, its just show the index then when i try to click some link like nodes, its will be goto myserver.com/nodes, not to myserver.com/puppet-report/nodes its just work if i try to reverse to myserver.com.

Hi, Iam a newbie to puppet, iam trying to set my local puppet master and dashboard running on same server. Iam also using https to connect to dashboard. I can launch the dashboard on https://IP fine but i see only one report on the webpage, When i tried to import all the previous reports iam getting this error # cd /usr/share/puppet-dashboard/ ]# sudo -u puppet-dashboard rake

I''m having all sorts of trouble getting our new puppet-dashboard install to connect/get the facts/inventory from the puppet master. These are separate boxes, and I''m getting (testing): root@puppetdash puppet-dashboard]# curl -k -H "Accept: yaml" https://puppet:8140/production/facts/hero0304.rc.fas.harvard.edu Forbidden request:

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

I''ve almost gotten PE running -- Based on tips from a recent Webinar, I''ve started on a minimal RHEL 6 system, and have installed the PE 2.03 packages. Once I set up /etc/ hosts (DNS will come later), I started the PE services. Given past problems (possibly just me), I was pleasantly surprised that the puppet-enterprise-updater script was so accommodating as I remembered which

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

Hi, Since this morning all nodes are showing as unresponsive. I have faced a similar error before and the problem was fixed restarting the dashboard-workers as there were many pending task in the puppet dashboard. I am using Puppet Enterprise 2.7.1 version. I have already checked/done: * Restarted the puppetmaster server * Check that puppet-dashboard-workers are working * Time is synced

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