Announce: Puppet Dashboard 1.2.10 Available

William Hopper

unread,

Jul 12, 2012, 7:07:33 PM7/12/12

to puppet...@googlegroups.com, puppe...@googlegroups.com

1.2.10 is a maintenance release of Puppet Dashboard.
It includes contributions from Will Hopper and Moses Mendoza.
Thanks to Aaron Patterson for the security content in commit
e17269f.

This release is available for download at:
https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.10.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:
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet

Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.2.10:
http://projects.puppetlabs.com/projects/dashboard

Documentation is available at:
http://docs.puppetlabs.com/dashboard/index.html

1.2.10 Security Fixes/Highlights
===
*Patch puppet-dashboard for CVE-2012-2660

This commit adds a patch to actionpack to address
CVE-2012-2660, unsafe query generation vulnerability. This
patch is taken from Aaron Patterson on the rails security list:
https://groups.google.com/forum/?fromgroups#!topic/rubyonrails-security/8SA-M3as7A8

*(#11849) Add rake task to install cron job to clean up database reports

This commit adds a rake task to install a monthly cron
job to clean up old database reports, as suggested in official
Puppet Labs documentation. This allows users to easily install
the optional cron job while not risking undesired data loss for
those who do not wish to have the job installed by default.

1.2.10 Changelog
===
Will Hopper (1)
5de691f (#11849) Add rake task to install cron job to clean up database reports
Moses Mendoza (3)
07c75a3 cleanup on puppet-dashboard spec file
b70344d create certs directory with installation
d9b7eeb Install a default settings.yml file with database.yml
e17269f Patch puppet-dashboard for CVE-2012-2660

signature.asc

Jo Rhett

unread,

Jul 12, 2012, 8:05:29 PM7/12/12

to puppet...@googlegroups.com, puppe...@googlegroups.com

On Jul 12, 2012, at 4:07 PM, William Hopper wrote:

*(#11849) Add rake task to install cron job to clean up database reports

  This commit adds a rake task to install a monthly cron
  job to clean up old database reports, as suggested in official
  Puppet Labs documentation. This allows users to easily install
  the optional cron job while not risking undesired data loss for
  those who do not wish to have the job installed by default.

Where is the documentation for this feature? How do I invoke it?

The maintaining page still just says to create a cron job.

--

Jo Rhett

Net Consonance : net philanthropy to improve open source and internet projects.

Stefan Heijmans

unread,

Jul 13, 2012, 2:50:07 AM7/13/12

to puppet...@googlegroups.com, puppe...@googlegroups.com

Op vrijdag 13 juli 2012 02:05:29 UTC+2 schreef Jo het volgende:

Where is the documentation for this feature? How do I invoke it?

The maintaining page still just says to create a cron job.

the maintaining page also mentions;

If you run ‘rake reports:prune’ without any arguments, it will display further usage instructions.

Just installed in in our sandbox and it shows;

rake reports:prune
EXAMPLE:
# Prune records upto 1 month old:
rake reports:prune upto=1 unit=mon

UNITS:
Valid units of time are: mon,yr,day,min,wk,hr

Stefan Heijmans

unread,

Jul 13, 2012, 3:05:55 AM7/13/12

to puppet...@googlegroups.com, puppe...@googlegroups.com

Op vrijdag 13 juli 2012 08:50:07 UTC+2 schreef Stefan Heijmans het volgende:

the maintaining page also mentions;

If you run ‘rake reports:prune’ without any arguments, it will display further usage instructions.

my bad, that's not the one.

# rake cron:cleanup
ln -sf /usr/share/puppet-dashboard/examples/puppet-dashboard.cleanup_reports.cron /etc/cron.monthly/puppet-dashboard.cleanup_reports.cron

It creates a link from the source to the /etc/cron.monthly.

One issue, if you have puppet-dashboard installed in a different location the source is not there.

# more /etc/cron.monthly/puppet-dashboard.cleanup_reports.cron
/etc/cron.monthly/puppet-dashboard.cleanup_reports.cron: No such file or directory
# ll /usr/share/puppet-dashboard/examples/puppet-dashboard.cleanup_reports.cron
ls: /usr/share/puppet-dashboard/examples/puppet-dashboard.cleanup_reports.cron: No such file or directory
# ll /opt/puppet-dashboard/examples/puppet-dashboard.cleanup_reports.cron
-rwxr-xr-x 1 puppet-dashboard puppet-dashboard 597 Jul 12 20:50 /opt/puppet-dashboard/examples/puppet-dashboard.cleanup_reports.cron
#

Antidot SAS

unread,

Jul 13, 2012, 5:16:51 AM7/13/12

to puppet...@googlegroups.com

HI I trying to upgrade for debian squeeze:

(Reading database ... 66401 files and directories currently installed.)

Preparing to replace librack-ruby 1.1.0-4 (using .../librack-ruby_1.1.0-4_all.deb) ...

Unpacking replacement librack-ruby ...

Setting up puppet-dashboard (1.2.10-1puppetlabs1) ...

Starting Puppet Dashboard:Not starting Puppet Dashboard, disabled via /etc/default/puppet-dashboard ... (warning).

.

Starting Puppet Dashboard Workers:NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01.

Gem.source_index called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21.

NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01.

Gem::SourceIndex#initialize called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100.