On Wed, Sep 7, 2011 at 6:15 PM, Michael Stahnke stah...@puppetlabs.com wrote:
3. Dashboard has had no commits since 1.2.0, so no RC this month.
Dashboard does have commits since 1.2.0
$ git log --oneline --no-merges 1.2.0..
6b10a5e maint: Move duplicated code to a helper method
02ca4ff maint:
On Tue, Aug 30, 2011 at 8:15 AM, David Thompson
dthomp...@waisman.wisc.edu wrote:
basically anyone attempting to do anything reasonable with ruby on RHEL 5.x
(or any of the free repackaged distributions of RHEL 5.x) knows that 1.8.5
version is just short of useless and has implemented other
A race condition issue has been found with DelayedJob report
processing. The fix has been committed to the rc branch, so another
RC will be necessary.
Ticket #8686
commit:e86526f224058d8d049b2f8b93d5fdca57332ad8
On Fri, Jul 22, 2011 at 4:18 PM, Michael Stahnke stah...@puppetlabs.com wrote:
sure) before cutting
a new rc is 8691.
Dan
On Thu, Jul 28, 2011 at 4:38 PM, Matt Robinson m...@puppetlabs.com wrote:
A race condition issue has been found with DelayedJob report
processing. The fix has been committed to the rc branch, so another
RC will be necessary.
Ticket #8686
require 'rubygems'
require 'yourgemname'
That should be enough. You're going to have to start giving more info
you want more help. At the very least the gem name. Sometimes you
think you're requiring the gem correctly based on the gem name, but
the thing you need to require might not match the
Jake
The behavior in 2.7 when running the master with
--allow_duplicate_certs set is the same as in 2.6.x in that you can
manually (using something like curl or the new 'puppet certificate'
face) generate multiple certs with same CN name, but the agent errors
the same way regardless of the puppet
This release addresses issues with the Puppet 2.6.x series.
Bug #4884:
Shell exec provider that executes code as a raw shell script
Bug #5670:
Failed resources don't improperly trigger a refresh
Feature #2331:
New macports provider
You can find the full release notes for Puppet at:
This release addresses some issues issues with Dashboard v1.1.0
#6532 - There is a rake task for generating random sample reports for
testing. rake reports:samples:generate
CHANGELOG
v1.1.1rc1
==
f1b2af4 (#7060) Use absolute paths for cert/private key
1a3e607 maint: Document the `rake
...@gmail.com wrote:
Hi Matt,
2011/4/8 Matt Robinson m...@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
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
There were a few very important changes we forgot to highlight in the
Dashboard v1.1.0rc1 release notes.
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,
Facter 1.5.9 is a maintenance release containing fixes and updates.
This release is available for download at:
http://puppetlabs.com/downloads/facter/facter-1.5.9rc1.tar.gz
See the Verifying Puppet Download section at:
On Wed, Mar 16, 2011 at 5:38 PM, Matt Robinson m...@puppetlabs.com wrote:
Facter 1.5.9 is a maintenance release containing fixes and updates.
That subject and message were supposed to say that this is a release
candidate, 1.5.9rc1, not the final release of 1.5.9
--
You received this message
,
there are already tables for facts, used for storeconfigs, along with an
active_record terminus for facts.
On Fri, Feb 25, 2011 at 1:55 PM, Matt Robinson m...@puppetlabs.com wrote:
I propose that we don't share tables, and the inventory service (and
any other future service that needs a database backend
On Wed, Feb 23, 2011 at 2:04 PM, Nick Lewis n...@puppetlabs.com wrote:
Our current plan for the inventory service is to provide active_record
termini for the facts and inventory indirections. This is to support
fast look-up of facts, and search of nodes based on their facts. However,
there are
The documentation on the wiki for the development lifecycle process
has been updated in an effort to make it easier for people to get code
into Puppet. The goals were to make it correct and easy to follow, so
take a look and let us know if there's anything that could use
improvement.
Hi Oliver,
Dan Bode emailed me to let me know that he has already looked into
this a bit and that he will be on site to work with you this next
week. I'll look further into these tests if he doesn't have the time
to see this through.
Matt
On Fri, Sep 3, 2010 at 4:20 PM, Matt Robinson m
Hi Oliver,
Sorry for taking so long to respond on this. We definitely appreciate
the help writing some tests for that patch as it looks like something
that would definitely help people once it gets merged in.
Writing tests for puppet providers can be tricky, as you're finding.
I'll take a look
Steven,
Thanks for sharing your findings. I've created ticket #4553 to either
add some README documentation about this or somehow setup a default
for log size.
Matt
http://projects.puppetlabs.com/issues/4553
On Mon, Aug 16, 2010 at 3:32 PM, Steven L. Seed slseed1...@gmail.com wrote:
I found
We weren't aware as none of us are using Internet Explorer. We'll
have to have someone get a copy to test with at some point.
Can you file a ticket?
http://projects.puppetlabs.com
Thanks,
Matt
On Thu, Aug 12, 2010 at 6:40 AM, ScubaDude brett.ma...@googlemail.com wrote:
puppet-dashboard on
There's a Google Summer of Code student working on a libvirt module
for us right now. It's currently alpha stage and only supports Xen
and KVM right now, not OpenVZ, but might be worth following the
progress or contributing to the code or providing feedback.
not be using the
stable version of facter? Looks like 1.5.7 was last updated in
9/2009? :/
On Aug 2, 6:04 pm, Matt Robinson m...@puppetlabs.com wrote:
I was seeing similar problems and it had to do with a bug in facter
since it wasn't confining a windows fact to windows. Try this patch
I was seeing similar problems and it had to do with a bug in facter
since it wasn't confining a windows fact to windows. Try this patch
on your facter:
http://github.com/nicklewis/facter/commit/b2c21145885c15abc43b3641fcf903e13a859565
On Mon, Aug 2, 2010 at 5:26 PM, bobics bob...@gmail.com
23 matches
Mail list logo
