FAQ
I installed the RPM available from yum.puppetlabs.com on CentOS 6.x and I receive the following error when upgrading from 1.2.10 to 1.2.11.

$ rake db:migrate RAILS_ENV=production
certificate_path: 'certs/puppet.cert.pem'
private_key_path: 'certs/puppet.private_key.pem'
public_key_path: 'certs/puppet.public_key.pem'

(in /usr/share/puppet-dashboard)
Unable to read the packaging repo info from ext/build_defaults.yaml
$ ls ext
passenger puppet
$ find ext
ext
ext/passenger
ext/passenger/dashboard-vhost.conf
ext/puppet
ext/puppet/puppet_dashboard.rb

Dashboard appears to be working fine, but the error provides some cause for concern.
On Sep 13, 2012, at 3:14 PM, Matthaus Owens wrote:
Puppet Dashboard 1.2.11 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.11.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.11:
http://projects.puppetlabs.com/projects/dashboard

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

Puppet Dashboard 1.2.11 Highlights
============================
(#15196) Make items per page configurable
This commit adds the ability to specify the number of specific items
per page displayed by dashboard in the settings.yml file, including
nodes, classes, groups and reports per page.

Autorefresh link gen fixed to work under passenger
Autorefresh link generation did not take root_path for the
application into consideration. Using File.join() to try and avoid
multiple /'s getting into generated url which would cause routing
problems.

Shift to using packaging repo for packaging tasks
This release introduces Dashboard's use of the packaging repo at
https://github.com/puppetlabs/packaging for packaging automation. From
source, doing a rake package:bootstrap clones packaging tasks into
ext/packaging and adds rake tasks for packaging of tar, srpm, rpm, and
deb using tools such as rpmbuild and debuild, as well as
puppetlabs-namespaced tasks that use chroot environment tools and are
keyed to specifically interacting with the puppetlabs environment. The
packaging repo works in tandem with the new package-builder modules
designed to set up hosts for packaging,
https://github.com/puppetlabs/puppetlabs-rpmbuilder, and
https://github.com/puppetlabs/puppetlabs-debbuilder. This is very much
a work in progress, but a model for how packaging automation could
improve across many Puppet Labs projects.

Puppet Dashboard 1.2.11 Changelog
============================
Boyan Tabakov (2):
d6619a1 Updated debian postinst script to link properly the
settings.yml file to puppet-dashboard config directory.
a8a97dc Fixed linking of database.yml in debian postinst to use
absolute path.

Erik Dalén (1):
ffe7bdd (#15196) Make items per page configurable

Jani Mikkonen (1):
df5a20a Autorefresh link gen fixed to work under passenger

Joshua Harlan Lifton (2):
c64c013 (#10477) Clean up log files by moving message to debug
a8e2586 Fix spec tests broken by commit c64c013

Matthaus Litteken (2):
8806f60 (#15291) Add Vendor tag to Puppet-Dashboard spec file
c0592af Update CHANGELOG, VERSION for 1.2.11

Moses Mendoza (10):
3abf9df Move packaging up to ext to avoid conflict with pkging repo
71d302a re-template debian changelog
4201990 Fixup redhat spec erb for packaging repo
42030b8 Remove obsolete package.rake file
da22ddd Add packaging data files
8f03e6c Add VERSION file to source
e6f6acf Fixup Rakefile for setting up packaging repo
101af75 Update supported debian versions and cows
20a109a Update mocks to accurately reflect dashboard builds
dd88f0b Update CHANGELOG, VERSION for 1.2.11-rc1

Will Hopper (2):
63a0634 Add release number variable to packaging rake task
5eccef2 (#15523) Update Debian packaging rake task to create the
debian and original tarballs

--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com.
To unsubscribe from this group, send email to puppet-dev+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
--
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.



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

Search Discussions

  • Moses Mendoza at Sep 18, 2012 at 8:55 pm
    Hi Jo,

    Good catch. While working with packaging, we modified the
    puppet-dashboard top-level rakefile to try loading a couple yaml files
    in ext, and a rescue prints the message you see if they're not there.
    Alas, those yaml files don't make it into the rpm, which is why you're
    seeing the message. It doesn't affect dashboard's other rake tasks,
    e.g. db:migrate in any way, but that error message is certainly an
    unsavory user experience. The next release of puppet dashboard will
    address this. Thanks for reporting this.

    Moses
    On Tue, Sep 18, 2012 at 9:56 AM, Jo Rhett wrote:
    I installed the RPM available from yum.puppetlabs.com on CentOS 6.x and I
    receive the following error when upgrading from 1.2.10 to 1.2.11.

    $ rake db:migrate RAILS_ENV=production
    certificate_path: 'certs/puppet.cert.pem'
    private_key_path: 'certs/puppet.private_key.pem'
    public_key_path: 'certs/puppet.public_key.pem'

    (in /usr/share/puppet-dashboard)
    Unable to read the packaging repo info from ext/build_defaults.yaml
    $ ls ext
    passenger puppet
    $ find ext
    ext
    ext/passenger
    ext/passenger/dashboard-vhost.conf
    ext/puppet
    ext/puppet/puppet_dashboard.rb

    Dashboard appears to be working fine, but the error provides some cause for
    concern.

    On Sep 13, 2012, at 3:14 PM, Matthaus Owens wrote:

    Puppet Dashboard 1.2.11 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.11.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.11:
    http://projects.puppetlabs.com/projects/dashboard

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

    Puppet Dashboard 1.2.11 Highlights
    ============================
    (#15196) Make items per page configurable
    This commit adds the ability to specify the number of specific items
    per page displayed by dashboard in the settings.yml file, including
    nodes, classes, groups and reports per page.

    Autorefresh link gen fixed to work under passenger
    Autorefresh link generation did not take root_path for the
    application into consideration. Using File.join() to try and avoid
    multiple /'s getting into generated url which would cause routing
    problems.

    Shift to using packaging repo for packaging tasks
    This release introduces Dashboard's use of the packaging repo at
    https://github.com/puppetlabs/packaging for packaging automation. From
    source, doing a rake package:bootstrap clones packaging tasks into
    ext/packaging and adds rake tasks for packaging of tar, srpm, rpm, and
    deb using tools such as rpmbuild and debuild, as well as
    puppetlabs-namespaced tasks that use chroot environment tools and are
    keyed to specifically interacting with the puppetlabs environment. The
    packaging repo works in tandem with the new package-builder modules
    designed to set up hosts for packaging,
    https://github.com/puppetlabs/puppetlabs-rpmbuilder, and
    https://github.com/puppetlabs/puppetlabs-debbuilder. This is very much
    a work in progress, but a model for how packaging automation could
    improve across many Puppet Labs projects.

    Puppet Dashboard 1.2.11 Changelog
    ============================
    Boyan Tabakov (2):
    d6619a1 Updated debian postinst script to link properly the
    settings.yml file to puppet-dashboard config directory.
    a8a97dc Fixed linking of database.yml in debian postinst to use
    absolute path.

    Erik Dalén (1):
    ffe7bdd (#15196) Make items per page configurable

    Jani Mikkonen (1):
    df5a20a Autorefresh link gen fixed to work under passenger

    Joshua Harlan Lifton (2):
    c64c013 (#10477) Clean up log files by moving message to debug
    a8e2586 Fix spec tests broken by commit c64c013

    Matthaus Litteken (2):
    8806f60 (#15291) Add Vendor tag to Puppet-Dashboard spec file
    c0592af Update CHANGELOG, VERSION for 1.2.11

    Moses Mendoza (10):
    3abf9df Move packaging up to ext to avoid conflict with pkging repo
    71d302a re-template debian changelog
    4201990 Fixup redhat spec erb for packaging repo
    42030b8 Remove obsolete package.rake file
    da22ddd Add packaging data files
    8f03e6c Add VERSION file to source
    e6f6acf Fixup Rakefile for setting up packaging repo
    101af75 Update supported debian versions and cows
    20a109a Update mocks to accurately reflect dashboard builds
    dd88f0b Update CHANGELOG, VERSION for 1.2.11-rc1

    Will Hopper (2):
    63a0634 Add release number variable to packaging rake task
    5eccef2 (#15523) Update Debian packaging rake task to create the
    debian and original tarballs

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


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



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

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppuppet-users @
categoriespuppet
postedSep 18, '12 at 7:52p
activeSep 18, '12 at 8:55p
posts2
users2
websitepuppetlabs.com

2 users in discussion

Moses Mendoza: 1 post Jo Rhett: 1 post

People

Translate

site design / logo © 2022 Grokbase