Puppet users - Mar 2011 - ANNOUNCE: Puppet Dashboard 1.1.0rc3

This rc addresses an issue when using Dashboard 1.1.0rc1 with Puppet
2.6.7rc1 when the Puppet master would have both storedconfigs, and the
inventory service enabled.

Bug #6791 - Fact lookup for a single node from Dashboard fails when
            using storeconfigs

  This is because the active_record terminus that storeconfigs sets as
  the cache for facts does not properly return the facts'' timestamp.
  Dashboard then tries to parse this missing field and fails with can''t
  dup NilClass. Facts search is unaffected by this.

Also, as noted with the rc1 announcement, there were a couple of very
important notes we forgot to mention:

  1.  Reports will need to be converted to a new schematized format when
  upgrading (#5459).  Rather than just storing reports as serialized
  YAML in the database as is currently done in v1.0.4, they are now in a
  set of tables that allows them to be queried more easily and faster.
  This conversion can be a slow process if you have a long history of
  reports, so it''s not done as part of `rake db:migrate`.  Instead,
  there is a rake task (#5535) that will do the conversion for you,
  converting newer reports first and able to be resumed if it''s
  interrupted just by rerunning it.

  `rake reports:schematize`

  Also worth noting is the `rake reports:prune` task that can prune
  older reports that you don''t care about, which will make this
  conversion much faster.  Run the rake task without arguments to see
  documentation for how to specify how far back to prune.

  2.  The new inventory service portion of Dashboard only works if
  you''re running the newest version of Puppet (2.6.7 which is releasing
  today).

This release is available for download at:
  http://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.1.0rc3.tar.gz

See the Verifying Puppet Download section at:
  http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads

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

v1.1.0rc3
========2d4d3da Updated VERSION for 1.1.0rc3

v1.1.0rc2
========af1a006 (#6835) Handle malformed facts from Puppet 2.6.7 &
storedconfigs

-- 
Jacob Helwig

Hi Jacob,

2011/3/24 Jacob Helwig <jacob@puppetlabs.com>
> [...]
> This release is available for download at:
>
> http://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.1.0rc3.tar.gz
> [...]
>
are there already RPMs available? I would like to help testing but only if
RPMs are provided.

Kind regards, Thomas

-- 
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 Thomas, sorry for the slow reply on this and lack of packages for
testing.  We messed up and forgot to put packages out with Dashboard
for the RC or the release.  This should be fixed now for the release,
and we''ve updated our RC checklist to make testing packages for the
next time.

We definitely appreciate any help testing RC''s and releases, so I look
forward to your feedback.

Matt

On Mon, Mar 28, 2011 at 4:34 AM, Thomas Bendler
<thomas.bendler@gmail.com> wrote:
> Hi Jacob,
>
> 2011/3/24 Jacob Helwig <jacob@puppetlabs.com>
>>
>> [...]
>> This release is available for download at:
>>
>>
  http://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.1.0rc3.tar.gz
>> [...]
>
> are there already RPMs available? I would like to help testing but only if
> RPMs are provided.
>
> Kind regards, Thomas
>
> --
> 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.
>
-- 
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 Matt,

2011/4/8 Matt Robinson <matt@puppetlabs.com>
> [...]
> We definitely appreciate any help testing RC''s and releases, so I
look
> forward to your feedback.
> [...]
>
Ok, here it is (CentOS 5.6 system). I''ve changed:

su -s /bin/sh -c "${DASHBOARD_RUBY} ${DASHBOARD_HOME}/script/server -e
${DASHBOARD_ENVIRONMENT} -p ${DASHBOARD_PORT} -b ${DASHBOARD_IFACE}"
${DASHBOARD_USER} &

to:

su -s /bin/sh -c "${DASHBOARD_RUBY} ${DASHBOARD_HOME}/script/server -e
${DASHBOARD_ENVIRONMENT} -p ${DASHBOARD_PORT} -b
${DASHBOARD_IFACE}
>/dev/null 2>&1" ${DASHBOARD_USER} &
in /etc/init.d/puppet-dashboard. Otherwise my console is messed up with
error logs and I can''t log out without loosing puppet-dashboard.
/dev/null
could be replaced by a log file wich should be part of logrotate.

Regards, Thomas

-- 
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.

I''m not sure why this would be without more info to reproduce the
problem.  I couldn''t reproduce it anyway.  I''d recommend
opening a
ticket that includes at least a sample of the messed up error logs in
addition to the info you provided.

On Mon, Apr 11, 2011 at 7:06 AM, Thomas Bendler
<thomas.bendler@gmail.com> wrote:
> Hi Matt,
>
> 2011/4/8 Matt Robinson <matt@puppetlabs.com>
>>
>> [...]
>> We definitely appreciate any help testing RC''s and releases,
so I look
>> forward to your feedback.
>> [...]
>
> Ok, here it is (CentOS 5.6 system). I''ve changed:
>
> su -s /bin/sh -c "${DASHBOARD_RUBY} ${DASHBOARD_HOME}/script/server -e
> ${DASHBOARD_ENVIRONMENT} -p ${DASHBOARD_PORT} -b ${DASHBOARD_IFACE}"
> ${DASHBOARD_USER} &
>
> to:
>
> su -s /bin/sh -c "${DASHBOARD_RUBY} ${DASHBOARD_HOME}/script/server -e
> ${DASHBOARD_ENVIRONMENT} -p ${DASHBOARD_PORT} -b ${DASHBOARD_IFACE}
>>/dev/null 2>&1" ${DASHBOARD_USER} &
>
> in /etc/init.d/puppet-dashboard. Otherwise my console is messed up with
> error logs and I can''t log out without loosing puppet-dashboard.
/dev/null
> could be replaced by a log file wich should be part of logrotate.
>
> Regards, Thomas
>
-- 
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.