similar to: Please start testing for release

Displaying 20 results from an estimated 10000 matches similar to: "Please start testing for release"

2007 Oct 25
15
State of Development
Hi all, I''m sure you''re all wondering what the heck is going on with development and why there are so many open tickets. Hopefully this email will answer those questions for you. REST Development ====================== First, I''ve found the REST work to be significantly more complicated than I''d feared. The plumbing is nearly all done and the majority
2007 Dec 17
21
New error in Centos 5.1
Just started a "pilot" puppet server for real after messing around in VMs for the past week or so... I used the 0.24.0 since it was available, and on the test run, got this: err: Could not prefetch package provider ''yum'': Execution of ''/usr/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py'' returned 512: /usr/bin/python:
2007 Mar 19
23
puppet hangs while trying to restart a daemon
Hello all, puppet hangs while trying to restart a daemon when the associated config file changes, here the log: Mar 19 11:30:04 ingentTest puppetd[27390]: Starting Puppet client version 0.22.0 puppetd[27390]: Starting configuration run puppetd[27390]: (/ingenttest/qualsevolnode/guaita[guaita]/File[/etc/guaita.conf]/content) synced puppetd[27390]:
2007 Apr 23
8
exec resources
I am consistently getting the following error from puppetd when an exec resource is triggered by a refresh event: Apr 23 10:36:11 mailhub puppetd[37884]: Reopening log files Apr 23 10:36:11 mailhub puppetd[37884]: Starting Puppet client version 0.22.3 Apr 23 10:36:11 mailhub puppetd[37884]: Starting configuration run Apr 23 10:36:12 mailhub puppetd[37884]:
2007 Apr 26
5
$processor fact not working on OS X
Hello dear list. First of all thanks to all the developers for the great work on puppet. After using it for a while, there is not better tool to manage a network! I have a problem with the $processor fact, which seems to be either not there or ignored at all. I try to implement package deployment for the Macs (Intel vs. PowerPC) as described here:
2007 Feb 21
9
Facter environment variables being ignored in puppet?
Facter has the feature that it will turn any environment variable named FACTER_* into a fact. I can do this on the commandline no problem, but when I attempt this in puppet it seems to ignore that parts. Is anyone else seeing this? (Is this expected behavior?) I don''t see a ticket or a mail thread on it - though my searching powers have been weak the last couple of weeks... Thanks,
2007 Jan 04
10
New Feature: Graphing
Hi all, One of the major new features in the upcoming release is that Puppet now uses a graph library internally to handle resource relationships. The big benefit to all of you is that you can use this library to turn these graphs into images. The trick, right now, is adding --graph when you run puppetd. This creates .dot files, which can then be interpreted by the
2007 Oct 18
1
ruby error on macosx
I don''t manage any macosx machines but I do run puppet standalone to check syntax etc. I''ve been getting the following error: Could not autoload "/usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/resourceoverride.rb": superclass mismatch for class ResourceOverride specifically small test pp files still work, though I''ve found when I use parseonly it
2007 Nov 21
6
mod_proxy_balancer under heavy load.
So I''m still working on a ''perfect'' setup so I can document it on the wiki, and will submit some puppet patches against 0.23.2 next week, but here''s what I''ve done that has made a big difference to stability here. in puppetmasterd at line 261, I''ve modified the Mongrel instantiation from: server = Mongrel::HttpServer.new(addr,
2007 Apr 30
17
Managing packages which require a reboot
Hi, I''m working on a method to manage packages which require a reboot after being installed. I''m curious how other people are handling this problem. Consider the resource: pkg_deploy { "MacOSXUpdCombo10.4.9Intel.dmg": alias => macosx1049 } I''d like to only install the package under if the following conditions are met: - No user is logged into the
2008 Jan 06
3
Mac OS X pkgs up.
So I''ve done some Mac OS X pkgs for the latest Facter and Puppet, as well as a combined mpkg for them both. Jeff McCune and I are doing a fair bit of testing on them this week in preparation for MacWorld, so I wasn''t going to upload them to the official site for another few days, but they''re looking pretty good. http://explanatorygap.net/puppet/Facter_1.3.8.pkg.zip
2007 May 01
8
Custom functions and facts
Hello! I''ve been trying to use facts from Facter in a custom function. I''ve been following Matthew''s entry in the wiki (http://www.reductivelabs.com/trac/puppet/wiki/WritingYourOwnFunctions). What i''m seeing is that Facter[''fqdn''].value is always returning the fqdn of the puppetmaster host. I was expecting the fqdn of the client host.
2006 Jul 26
19
documentation suggestions: including FQDN seems to
Hi, I''m new to Puppet, but it looks very good, so far. We are going to use it for a multi-tier (DEV, QA, staging, production) environment which is consists of web, app, and database servers. I have a couple of suggestions for the Puppet documentation that may save others some time. First, it seems node names MUST be FQDNs (hostname and hostname. will not work). Since we are not using
2007 Jan 10
7
Problem adding facts ...
I have created my first ''fact'', first attempt at Ruby too, and configured the fileserver to server it but when a Fedora (5 or 6) client sync''s puppetd appears to hang. CentOS clients sync and use the new fact fine. Find attached the fact file and the output from ''puppetd --debug --factsync'' on a FC5 client is below. This is a 0.20.1 client and
2007 Jun 14
19
Please test export/collect from svn
For those of you out there using export/collect (which we really need to come up with a better name for...), can you test the current SVN code? I''m mostly wondering if the performance is any better. To use it, you''ll have to remove your current database, since the database schema is significantly changed. I''m getting what looks like an additional 25% reduction
2008 Feb 01
3
"Could not retrieve dependency" error
Hi, I''m getting a "Could not retrieve dependency" error and I can''t figure why. Someone got a cluestick for me? I''m using the following simplified configuration to ensure sshd is running and gets reloaded when the config file changes: ---- site.pp ---- import "classes/sshd.pp" node obsd42 { include ssh-server } node debian40 { include
2007 Feb 22
33
Scaling Puppet 0.22.1 to hunderdes of nodes.
Hi, My environment is composed of ~250 workstations hitting a single puppetmaster server, which has been working fairly well up until now. The most recent change has been a migration of a lot of remote file copy objects which were previously handled with cfengine. client side puppetd calls to the puppetmaster.getconfig method are taking unreasonably long, on the order of 2-3 minutes. It
2007 Dec 18
2
Backward compatibility issues in 0.24.0
Hi all, Hobbeswalsh on IRC has discovered a backward compatibility issue in 0.24.0, preventing 0.23.x clients working well with 0.24.0 servers. Specifically, you can''t specify relationships to builtin resources when the client is 0.23.x, although specifying relationships to defined resources still works. The problem is that prior to 0.24.0 there was no central class
2007 Nov 28
13
What to call a class: Manifest? Configuration? ResourceContainer?
Hi all, I''ve got a new class in the current code, which I''ve been calling Configuration but Matt reasonably thinks is horrible. He is recommending the name Manifest, and I figured I''d see what others thought. The point of the class is to function as a resource container -- it keeps a reference to all of the resources we''re managing, and knows how to
2008 Nov 10
4
Weird custom type behaviour
Hey, I have a very trivial parsedfile based type - http://pastie.org/311146 - that works fine when deployed and run under puppetd -t. However, when being run by the daemonized puppet, it results in this error: Mon Nov 10 03:50:48 +0000 2008 //Node[ams-proxy-2]/quagga/Quagga::Daemon[zebra]/Quagga_service[zebra] (err): Failed to retrieve current state of resource: No ability to determine if