Puppet users - Nov 2012 - Announce: Puppet Dashboard 1.2.13 Available

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:
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.13:
http://projects.puppetlabs.com/projects/dashboard

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

==============================## Puppet Dashboard 1.2.13 Bug Fixes ##
==============================(#17161) Fix stylesheet URLs for IE colorbox
images
    The colorbox CSS looks for the IE images in
/images/internet_explorer. The correct location is
/stylesheets/images/internet_explorer.

Update debian and redhat init script to use INT instead of term to stop

    Previously the debian init script didn''t pass --signal to the
    start-stop-daemon, which defaults to TERM. Dashboard runs out of webrick by
    default, which catches and ignores TERM, but will respond to INT and stop
    sanely. Currently, running ''service puppet-dashboard stop''
returns

    [2012-03-27 10:24:17] ERROR SignalException: SIGTERM
        /usr/lib/ruby/1.8/webrick/server.rb:91:in `select''

    and then waits for the retry timeout, at which point
start-stop-daemon SIGKILLs
    the ruby process. If --signal is set to INT in the init script, running
    ''service puppet-dashboard stop'' returns

    [2012-03-27 10:28:35] INFO  going to shutdown ...
    [2012-03-27 10:28:35] INFO  WEBrick::HTTPServer#start done.
    Exiting

    which is the expected behavior.

    The redhat init script suffered from a similar problem, adding -INT to the
    killproc call speeds up the `service puppet-dashboard stop` call as killproc
    doesn''t need to wait and see if the process has ended, as INT is
responded to
    immediately by webrick.

(#9296) Fix loading rack for rubygems >= 1.8

    Rubygems version 1.8 broke some of the ways vendored gems used to
work in Rails
    2. This commit updates the config/environment.rb to add all of the
gem libs to
    the rails autoload_paths. It also updates the actionpack action_controller
    library to not call out to gem explicitly. We know that the correct rack
    version is being supplied in the vendored gems, so the following
require ''rack''
    line will succeed.

    This also munges the load path in config/boot.rb because boot.rb
doesn''t load
    environment.rb right away, and so can''t find rack, due to the same
gem problem.
    So this uses the same loop as in environment.rb, but instead of the rails
    autoload_paths, it adds the libs to $:, or $LOAD_PATH.

==============================## Puppet Dashboard 1.2.13 Changelog ##
==============================
Branan Purvine-Riley (1):
      c2e4a4a (#17161) Fix stylesheet URLs for IE colorbox images

Matthaus Owens (3):
      a3f2588 (#9296) Fix loading rack for rubygems >= 1.8
      5378b46 Update debian and redhat init script to use INT instead
of term to stop
      7a38e19 Updating CHANGELOG, VERSION for 1.2.13. Updating .gitignore

Moses Mendoza (1):
      ee6d3c3 Update VERSION, CHANGELOG for 1.2.13-rc1

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Hi,

Just updated from 1.2.11 to 1.2.13 with the tarball (
http://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.13.tar.gz)

Starting puppet-dashboard-workers it gives the following message;

# service puppet-dashboard-workers start
Starting puppet-dashboard-workers: 
/opt/puppet-dashboard/vendor/plugins/delayed_job/lib/delayed/command.rb:65:in 
`mkdir'': No such file or directory - /opt/puppet-dashboard/tmp/pids 
(Errno::ENOENT)
        from 
/opt/puppet-dashboard/vendor/plugins/delayed_job/lib/delayed/command.rb:65:in 
`daemonize''
        from /opt/puppet-dashboard/script/delayed_job:5
                                                           [FAILED]
#

# ll -d /opt/puppet-dashboard/tmp
ls: /opt/puppet-dashboard/tmp: No such file or directory
#

Creating this directory fixes it.


Checking the tarball shows that in 1.2.13 the tmp directory is not provided 
any more, in 1.2.11 it was still there.
# tar -tzvf puppet-dashboard-1.2.11.tar.gz|grep tmp
-rw-r--r-- matthaus/allstaff    923 2011-08-24 22:37:13 
puppet-dashboard-1.2.11/vendor/rails/railties/lib/tasks/tmp.rake
drwxr-xr-x matthaus/allstaff      0 2012-09-13 23:28:22 
puppet-dashboard-1.2.11/tmp/
# tar -tzvf puppet-dashboard-1.2.13.tar.gz|grep tmp
-rw-r--r-- matthaus/allstaff    923 2012-11-06 00:15:09 
puppet-dashboard-1.2.13/vendor/rails/railties/lib/tasks/tmp.rake
#

Stefan

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/8yrKNShvqbIJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Stefan,
Thanks for catching that. A recent change to our packaging workflow
unintentionally stopped empty directories from getting included in the
tarballs. We''ve since reverted that change, and a new release of
Dashboard will be forthcoming with an updated tarball, complete with
tmp dir..

On Wed, Nov 7, 2012 at 8:05 AM, Stefan Heijmans <heijmans@rechtspraak.nl>
wrote:
> Hi,
>
> Just updated from 1.2.11 to 1.2.13 with the tarball
> (http://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.13.tar.gz)
>
> Starting puppet-dashboard-workers it gives the following message;
>
> # service puppet-dashboard-workers start
> Starting puppet-dashboard-workers:
>
/opt/puppet-dashboard/vendor/plugins/delayed_job/lib/delayed/command.rb:65:in
> `mkdir'': No such file or directory -
/opt/puppet-dashboard/tmp/pids
> (Errno::ENOENT)
>         from
>
/opt/puppet-dashboard/vendor/plugins/delayed_job/lib/delayed/command.rb:65:in
> `daemonize''
>         from /opt/puppet-dashboard/script/delayed_job:5
>                                                            [FAILED]
> #
>
> # ll -d /opt/puppet-dashboard/tmp
> ls: /opt/puppet-dashboard/tmp: No such file or directory
> #
>
> Creating this directory fixes it.
>
>
> Checking the tarball shows that in 1.2.13 the tmp directory is not provided
> any more, in 1.2.11 it was still there.
> # tar -tzvf puppet-dashboard-1.2.11.tar.gz|grep tmp
> -rw-r--r-- matthaus/allstaff    923 2011-08-24 22:37:13
> puppet-dashboard-1.2.11/vendor/rails/railties/lib/tasks/tmp.rake
> drwxr-xr-x matthaus/allstaff      0 2012-09-13 23:28:22
> puppet-dashboard-1.2.11/tmp/
> # tar -tzvf puppet-dashboard-1.2.13.tar.gz|grep tmp
> -rw-r--r-- matthaus/allstaff    923 2012-11-06 00:15:09
> puppet-dashboard-1.2.13/vendor/rails/railties/lib/tasks/tmp.rake
> #
>
> Stefan
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/8yrKNShvqbIJ.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.


-- 
Matthaus Owens
Release Manager, Puppet Labs

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Matthaus,
I also noticed the following messages with the 1.2.13 db:migrate rake task, 
haven''t seem them before;
# rake db:migrate RAILS_ENV=production
config.gem: Unpacked gem rspec-1.3.2 in vendor/gems has no specification 
file. Run ''rake gems:refresh_specs'' to fix this.
config.gem: Unpacked gem sass-3.1.2 in vendor/gems has no specification 
file. Run ''rake gems:refresh_specs'' to fix this.
config.gem: Unpacked gem thoughtbot-shoulda-2.10.2 in vendor/gems has no 
specification file. Run ''rake gems:refresh_specs'' to fix this.
config.gem: Unpacked gem haml-3.1.2 in vendor/gems has no specification 
file. Run ''rake gems:refresh_specs'' to fix this.
config.gem: Unpacked gem rack-1.1.2 in vendor/gems has no specification 
file. Run ''rake gems:refresh_specs'' to fix this.
config.gem: Unpacked gem rspec-rails-1.3.4 in vendor/gems has no 
specification file. Run ''rake gems:refresh_specs'' to fix this.
config.gem: Unpacked gem daemons-1.0.10 in vendor/gems has no specification 
file. Run ''rake gems:refresh_specs'' to fix this.
config.gem: Unpacked gem will_paginate-2.3.15 in vendor/gems has no 
specification file. Run ''rake gems:refresh_specs'' to fix this.
config.gem: Unpacked gem json_pure-1.5.1 in vendor/gems has no 
specification file. Run ''rake gems:refresh_specs'' to fix this.
config.gem: Unpacked gem factory_girl-1.3.3 in vendor/gems has no 
specification file. Run ''rake gems:refresh_specs'' to fix this.
config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no specification 
file. Run ''rake gems:refresh_specs'' to fix this.
config.gem: Unpacked gem mocha-0.9.7 in vendor/gems has no specification 
file. Run ''rake gems:refresh_specs'' to fix this.
 

Stefan

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/Yp3DpRU4t6EJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.