{5} Assigned, Active Tickets by Owner (Full Description) (23 matches)
List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.
Fujin
| Ticket | Summary | Component | Milestone | Type | Severity | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #219 | user type could be used to lock account | user | unplanned | enhancement | minor | 08/08/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
User type could easely add locking capability by using: ensure => locked This will password lock the account and synonym for present+lock. This kind of users could only login with sshkey or other non-password means and be sure that it is enforced that way. This is enforced by passwd -l login ( on debian at least) pw user mod -h - -n login ( on freebsd ) regards, Ghislain. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ajax
| Ticket | Summary | Component | Milestone | Type | Severity | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #461 | Directories involved in file copies should not check timestamps | fileserving | unplanned | defect | normal | 01/26/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
When a recursive file copy is being done, there's no point in checking the directory timestamp, and it can result in extra service restarts. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
andrew
| Ticket | Summary | Component | Milestone | Type | Severity | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #1215 | Some syntax errors are not visible when running puppetd from the CLI | interface | 0.24.5 | defect | normal | 05/06/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
A syntax error in the puppetmaster config, doesn't cause an error to be displayed when running puppetd --test on the CLI of a node that would be affected. I'm using 24.4 on both client and master. When this is my node config: node nyvl-flstg2 inherits virtual-php-web-node {
$custom_environment = "staging"
include www2
}
this is the output of puppetd --test on that node: [root@nyvl-flstg2 ~]# puppetd --test notice: Ignoring cache info: Caching catalog at /var/lib/puppet/localconfig.yaml notice: Starting catalog run notice: Finished catalog run in 9.98 seconds [root@nyvl-flstg2 ~]# Which is all to be expected, everything is working correctly. However, if this is my node config: node nyvl-flstg2 inherits virtual-php-web-node {
$custom_environment = "staging"
include www2 ?
}
I get this in /var/log/messages on the puppetmaster: May 6 17:14:20 nyvl-flintranet puppetmasterd[29418]: Could not parse for environment development: Syntax error at '}' at /etc/puppet/manifests/nodes/nyvl-flstg2.pp:4 Which makes sense, because of the '?' in the line that is "include www2 ?" However, if I run puppetd on the client, I have no knowledge that there is a syntax error: [root@nyvl-flstg2 ~]# puppetd --test notice: Ignoring cache info: Caching catalog at /var/lib/puppet/localconfig.yaml notice: Starting catalog run notice: Finished catalog run in 9.15 seconds [root@nyvl-flstg2 ~]# In this case, I actually don't know what config the client is using, since it can't be using the current one (there's a significant syntax error) and it is "ignoring cache". I'd expect an error to be displayed saying that there is a syntax issue. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
luke
| Ticket | Summary | Component | Milestone | Type | Severity | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #612 | Export/Collect should be documented | documentation | elmo | enhancement | normal | 04/25/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
There's very little documentation for Export/Collect; all we have is at Virtual Resources, and it's not enough. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #1183 | some settings are not environment aware, e.g; manifest | settings | 0.24.5 | defect | normal | 04/09/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
When using puppetd ---environment=development --configprint <config name> the --environment variable is getting ignored. As you can see below Complete puppet.conf: [main]
vardir = /var/lib/puppet
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl
environment = production
manifest = $manifestdir/site.pp
[puppetmasterd]
environments=production,development
[puppetd]
classfile = $vardir/classes.txt
localconfig = $vardir/localconfig
environments=production,development
[production]
manifest = /srv/puppet/production/manifests/site.pp
[development]
manifest = /srv/puppet/development/manifests/site.pp
From default settings # puppetd --configprint manifest /etc/puppet/manifests/site.pp Using enviroments: # puppetd --environment=development --configprint manifest /etc/puppet/manifests/site.pp # puppetd --environment=production --configprint manifest /etc/puppet/manifests/site.pp |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #1175 | Custom function doesn't work when using multiple environments | language | 0.24.5 | defect | critical | 04/02/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Environments settings in puppet.conf: client: [main]
environment = production
server: [main]
environments = production,development
[production]
manifest = /usr/local/etc/puppet/manifests/production/site.pp
modulepath = /usr/local/etc/puppet/modules/production
I have module for postfix configuration with custom function My postfix module located in /usr/local/etc/puppet/modules/production/postfix and my custom function in /usr/local/etc/puppet/modules/production/postfix/plugins/puppet/parser/functions. I get the following error running puppet client: err: Could not retrieve catalog: Unknown function .... at /usr/local/etc/puppet/modules/production/postfix/manifests/init.pp:60 on node ..... If I disable using this function in postfix/manifests/init.pp module works. If I use setup without environments with configuration: [main]
manifest = /usr/local/etc/puppet/manifests/site.pp
modulepath = /usr/local/etc/puppet/modules
and place module into /usr/local/etc/puppet/modules/postfix and function into /usr/local/etc/puppet/modules/postfix/plugins/puppet/parser/functions everything works as expected. os version: FreeBSD-6.2 puppet version: 0.24.4 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #381 | Allow multiple overrides in one statement | language | elmo | enhancement | normal | 12/15/06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
It should be possible to write Type[name1,name2] { attr => value }
and have it mean hte exact same thing as Type[name1] { attr => value }
Type[name2] { attr => value }
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #448 | Relationships should have their own syntax | language | enhancement | normal | 01/22/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Relationships should be a separate configuration layer, and as such should have their own special syntax, rather than using parameters. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #593 | Puppet's cron type struggles with vixie-cron | cron | elmo | defect | normal | 04/17/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
After making a few changes to my cron job in my manifest, my crontab begins to look like: # DO NOT EDIT THIS FILE - edit the master and reinstall. # (- installed on Thu Apr 12 12:16:01 2007) # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $) # HEADER This file was autogenerated at Thu Apr 12 12:16:01 -0700 2007 by puppet. # HEADER While it can still be managed manually, it is definitely notrecommended. # HEADER Note particularly that the comments starting with 'Puppet Name' should # HEADER not be deleted, as doing so could cause duplicate cron jobs. # DO NOT EDIT THIS FILE - edit the master and reinstall. # (- installed on Wed Apr 11 16:42:40 2007) # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $) # DO NOT EDIT THIS FILE - edit the master and reinstall. # (- installed on Tue Apr 10 13:49:45 2007) # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $) # DO NOT EDIT THIS FILE - edit the master and reinstall. # (- installed on Thu Apr 5 17:36:42 2007) # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $) # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/tmp/crontab.XXXXWxMPKB installed on Thu Apr 5 17:08:07 2007) # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $) # Puppet Name: websync */10 * * * * <snip> If puppet would put its notice just before the first job it manages, I think it would avoid this problem. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #682 | Should be able to override noop when set in a type | RAL | elmo | enhancement | normal | 06/21/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I'm thinking about a configuration class that, amongst other things execs out to a 'dangerous' configuration script. I'd like to make this a noop by default, so the operator has to try a bit harder to invoke it. So I thought about doing something like: class blah {
exec { danger:
noop => true,
tag => hitme,
command => "might_break_it",
path => "/bin:/usr/bin:/usr/local/bin",
logoutput => true
}
}
And fire up puppetd with puppetd -o --tags hitme Unfortunately it doesn't fire the script... Whilst I see from an earlier post in puppet-users there you can supply --no-noop to puppetd, it makes no difference. I presume this getoptism only works if the noop you're using has been put in puppet.conf, not in the type. This enhancement request is to create a way to override the "noop => true". |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #752 | Extra or missing slashes break client pre-downloads | unknown | elmo | defect | normal | 08/04/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Here are the errors: diggyk: err: /plugin_collector/File[/var/lib/puppet/lib/k5login.rb]: Failed to generate additional resources during transaction: Fileserver module 'pluginsk5login' not mounted [6:24pm] diggyk: err: /plugin_collector/File[/var/lib/puppet/lib/k5login.rb]/source: Could not describe /pluginsk5login.rb: Fileserver module 'pluginsk5login' not mounted And here's a stack trace: http://pastie.caboo.se/84822 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #857 | Behaviour of Puppet when multiple classes of the same name are defined | language | elmo | defect | normal | 10/05/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
When multiple classes of the same name are defined: class mysql { notice('This is a load of the MySQL class') } class mysql { notice('This is a load of the second MySQL class') } class mysql { notice('This is a load of the third MySQL class') } According to Luke the contents of each new class of the same name are just added to the initial class and processed. Testing indicates that this isn't the behaviour and in fact only the first class is processed, i.e. using the above example the only notice returned is: "notice: mysql: This is a load of the MySQL class" I recommend that either this configuration throws an error - making classes unique - or the combination behaviour is fixed to include all content of each class. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #869 | False dependency: Error thrown after reparsing /etc/puppet.conf | settings | unplanned | defect | normal | 10/15/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This could well be a horrendous one to debug. If, as I expect you will need manifest or manifest-snippets to debug I should be able to get some cut down version over to you. I am applying a Puppet manifest to a 'bare metal' build. One class, utilities::puppetclientconf, admittedly not in a respectable dependency chain, changes /etc/puppet/puppet.conf. Puppet then wants to reparse and continue applying classes. It them barfs with Could not retrieve dependency 'File/etc/puppet' at /etc/puppet/modules/utilities/manifests/init.pp:291. This dependency *does* exist somewhere else in the class. Logs and a couple of manifest snippets attached. Oct 15 16:31:52 engpsr0155 puppetd[23546]: (//engpsr0155/base/utilities::puppetclientconf/File[/etc/puppet/puppet.conf]) Filebucketed to main with sum 7571487c3a26a4a087b29fcd787cfe57
Oct 15 16:31:52 engpsr0155 puppetd[23546]: (//engpsr0155/base/utilities::puppetclientconf/File[/etc/puppet/puppet.conf]/source) replacing from source puppet:///utilities/testpuppet.conf with contents {md5}daa7e7ee745a0f657720f85fa9c32de5
Oct 15 16:31:53 engpsr0155 puppetd[23546]: (//engpsr0155/base/services::setup/services::redhat/Service[gpm]/ensure) ensure changed 'running' to 'stopped'
Oct 15 16:31:57 engpsr0155 Installed: tk.x86_64 8.4.13-3.fc6
Oct 15 16:31:57 engpsr0155 Installed: tclx.x86_64 8.4.0-5.fc6
Oct 15 16:31:58 engpsr0155 Installed: emacspeak.noarch 23.0-2.1
Oct 15 16:31:58 engpsr0155 puppetd[23546]: (//engpsr0155/base/packages::setup/rhel5-packagegroups::dmzbase/rhel5-packagegroups::editors/Package[emacspeak]/ensure) created
Oct 15 16:31:58 engpsr0155 puppetd[23546]: (//engpsr0155/base/filemode::setup/filemode::redhat_filemode/filemode::filemode[/usr/bin/newgrp]/File[/usr/bin/newgrp]/mode) mode changed '4755' to '711'
Oct 15 16:31:58 engpsr0155 puppetd[23546]: (//engpsr0155/base/definittab::setup/definittab::definittab[std]/Inittab[~~]/ensure) created
Oct 15 16:31:58 engpsr0155 puppetd[23546]: (Filebucket[/var/lib/puppet/clientbucket]) Adding /etc/inittab(3b107ced0981045ff867f1b10eabb891)
Oct 15 16:32:02 engpsr0155 Installed: ntp.x86_64 4.2.2p1-5.el5
Oct 15 16:32:02 engpsr0155 puppetd[23546]: Reparsing /etc/puppet/puppet.conf
Oct 15 16:32:02 engpsr0155 puppetd[23546]: (//engpsr0155/base/ntp::setup/Package[ntp]/ensure) change from absent to present failed: Could not retrieve dependency 'File[/etc/puppet]' at /etc/puppet/modules/utilities/manifests/init.pp:291
Oct 15 16:32:06 engpsr0155 Installed: gnuplot.x86_64 4.0.0-12
Oct 15 16:32:06 engpsr0155 Installed: gnuplot-emacs.x86_64 4.0.0-12
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #901 | package type not automatically dependant on yumrepo type | RAL | elmo | enhancement | normal | 11/13/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
When using a yumrepo type to define yum repositories and using a yum provider for packages, there should be an automatic dependency setup between the two such that the yumrepo is processed first. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #1168 | Master-side client certificates convert hostnames to lowercase | unknown | 0.24.5 | defect | normal | 03/31/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I'm trying to use master-side certificate generation with hosts at Amazon's EC2 service. Internal hostnames there use mixed-case names: domU-12-31-12-34-56-78.compute-1.internal Note the "U" is upper-case. I build a set of certificates for this client: puppetca --generate domU-12-31-12-34-56-78.compute-1.internal Resulting files are: ./private_keys/domu-12-31-12-34-56-78.compute-1.internal.pem ./certs/domu-12-31-12-34-56-78.compute-1.internal.pem ./ca/signed/domu-12-31-12-34-56-78.compute-1.internal.pem Note all lower-case "u"s in "domu". When I put these onto the puppet client, they are mis-matched between hostname and filenames. The client (when started) ends up creating new keys with mixed-case names next to the versions that were copied from the Puppet master server: -rw------- 1 root root domU-12-31-12-34-56-78.compute-1.internal.pem -r-------- 1 root root domu-12-31-12-34-56-78.compute-1.internal.pem It's very possible this is invalid. I don't know the specs surrounding certificate generation. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #1201 | Variables defined via external node script are not same as ones defined in manifests | unknown | 0.24.5 | defect | normal | 04/23/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
In converting to an external node classifier script all my if statements in templates started failing. While a variable created either via the script or a manifest would print the same they do not test the same. The problem is that variables defined in a manifest are of class 'String', but variables defined via an external script are of class 'TrueClass'. This breaks all comparisons, since TrueClass needs to be converted to a string before you can run string comparisons on it. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #171 | File source operations cannot currently be rolled back | fileserving | enhancement | normal | 06/13/06 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Rollback doesn't work for file source operations. This is not a huge problem because rollback isn't currently used in the system, but they should work nonetheless. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #728 | ParsedFile providers do not work outside of a transaction | RAL | elmo | defect | normal | 07/20/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
When using types with a Parsed File? provider, the class-level prefetch is never called, which means that their current state is never retrieved. This makes them not work with tools like 'ralsh'. The fix should be relatively straightforward -- just find a way to trigger a prefetch if the data is missing -- but it likely requires a relatively high-level redesign to make this work. I made an attempt at triggering off of an empty @property_hash, and then creating a new hash during flush() (so that the provider class still had the data to write it to disk), but this caused other problems. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #511 | checksum => timestamp hiccups on timezone change | file | defect | trivial | 02/18/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This happened a lot after changing the timezone from UTC to UTC+1: notice: //.../File/usr/.../checksum: checksum changed '{time}Sun Feb 18 19:09:01 +0000 2007' to '{time}Sun Feb 18 20:09:01 +0100 2007' Since TZ changes should not happen often, this is really a minor annoyance. I suppose, the error happens in lib/puppet/type/pfile/checksum.rb when doing mtime.to_s These conversions should probably all happen in UTC. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #883 | Puppet configuration run time calculation not 'internal' | unknown | unplanned | defect | trivial | 10/29/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I'm not sure how to summarize clearly, so I will expound here. From puppetd --test: notice: Finished configuration run in 18252.08 seconds It took less than a minute to run, probably. We just updated our config with an NTP module now that the NTP server is online. Right after I logged in: $ date Mon Oct 29 17:03:58 UTC 2007 $ puppetd --test ... notice: //basenode/ntp/Service[ntpd]/ensure: ensure changed 'stopped' to 'running' ... notice: Finished configuration run in 18252.08 seconds $ date Mon Oct 29 22:08:36 UTC 2007 It looks like puppet checks the timestamp of the system before it runs, and then again afterward to calculate the run time, rather than timing everything internally? |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
lutter
| Ticket | Summary | Component | Milestone | Type | Severity | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #674 | Remove/simplify cache for fileserver clients in file | file | None | refactor | minor | 06/18/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
pfile.rb caches fileserver clients in uri2obj. That cache should either be keyed off server + port or be removed entirely. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
michael
| Ticket | Summary | Component | Milestone | Type | Severity | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #772 | Puppetmaster dies on SIGHUP | executables | unplanned | defect | normal | 08/16/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Sending a SIGHUP to the puppetmasterd caused it to keel over: /var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet.rb:245:in `settraps': uninitialized constant Puppet::Network::Client::Master (NameError) Trace: /var/lib/gems/1.8/bin/puppetmasterd --verbose --debug --mkusers --certname puppet.example.com --trace
info: Starting server for Puppet version 0.23.2
debug: user provider pw: Not suitable: missing pw
debug: user provider netinfo: Not suitable: missing nireport
debug: user provider directoryservice: Not suitable: operatingsystem not in darwin
debug: group provider pw: Not suitable: missing /usr/sbin/pw
debug: group provider netinfo: Not suitable: missing nireport
debug: group provider directoryservice: Not suitable: operatingsystem not in darwin
debug: /puppetconfig/main/File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca]: Autorequiring Group[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca]: Autorequiring User[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca]: Autorequiring File[/etc/puppet/ssl]
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private_keys/puppet.example.com.pem]: Autorequiring File[/etc/puppet/ssl/private_keys]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_crl.pem]: Autorequiring Group[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_crl.pem]: Autorequiring User[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_crl.pem]: Autorequiring File[/etc/puppet/ssl/ca]
debug: /puppetconfig/main/File[/var/puppet/state/state.yaml]: Autorequiring File[/var/puppet/state]
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /puppetconfig/main/File[/var/puppet/state]: Autorequiring File[/var/puppet]
debug: /puppetconfig/main/File[/var/puppet/facts]: Autorequiring File[/var/puppet]
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/public_keys/puppet.example.com.pem]: Autorequiring File[/etc/puppet/ssl/public_keys]
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/puppet/ssl]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/private/ca.pass]: Autorequiring Group[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/private/ca.pass]: Autorequiring User[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/private/ca.pass]: Autorequiring File[/etc/puppet/ssl/ca/private]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/serial]: Autorequiring Group[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/serial]: Autorequiring User[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/serial]: Autorequiring File[/etc/puppet/ssl/ca]
debug: /puppetconfig/main/File[/var/puppet/lib]: Autorequiring File[/var/puppet]
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /puppetconfig/main/File[/var/puppet/run]: Autorequiring File[/var/puppet]
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_pub.pem]: Autorequiring Group[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_pub.pem]: Autorequiring User[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_pub.pem]: Autorequiring File[/etc/puppet/ssl/ca]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/signed]: Autorequiring Group[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/signed]: Autorequiring User[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/signed]: Autorequiring File[/etc/puppet/ssl/ca]
debug: /puppetconfig/main/File[/var/puppet/plugins]: Autorequiring File[/var/puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_key.pem]: Autorequiring Group[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_key.pem]: Autorequiring User[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_key.pem]: Autorequiring File[/etc/puppet/ssl/ca]
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/csr_puppet.example.com.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/certs/puppet.example.com.pem]: Autorequiring File[/etc/puppet/ssl/certs]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/private]: Autorequiring Group[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/private]: Autorequiring User[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/private]: Autorequiring File[/etc/puppet/ssl/ca]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/requests]: Autorequiring Group[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/requests]: Autorequiring User[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/requests]: Autorequiring File[/etc/puppet/ssl/ca]
debug: /puppetconfig/ca/File[/etc/puppet/autosign.conf]: Autorequiring File[/etc/puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/inventory.txt]: Autorequiring Group[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/inventory.txt]: Autorequiring User[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/inventory.txt]: Autorequiring File[/etc/puppet/ssl/ca]
debug: /puppetconfig/main/User[puppet]: Autorequiring Group[puppet]
debug: /puppetconfig/main/File[/var/puppet/log]: Autorequiring Group[puppet]
debug: /puppetconfig/main/File[/var/puppet/log]: Autorequiring User[puppet]
debug: /puppetconfig/main/File[/var/puppet/log]: Autorequiring File[/var/puppet]
debug: /puppetconfig/main/File[/etc/puppet/namespaceauth.conf]: Autorequiring File[/etc/puppet]
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/puppet/ssl/certs]
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private/password]: Autorequiring File[/etc/puppet/ssl/private]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_crt.pem]: Autorequiring Group[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_crt.pem]: Autorequiring User[puppet]
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_crt.pem]: Autorequiring File[/etc/puppet/ssl/ca]
debug: /puppetconfig/main/File[/etc/puppet/namespaceauth.conf]: File does not exist
debug: /puppetconfig/ca/File[/etc/puppet/autosign.conf]: File does not exist
debug: /puppetconfig/main/File[/var/puppet/plugins]: File does not exist
debug: /puppetconfig/main/File[/var/puppet/facts]: File does not exist
debug: /puppetconfig/main/File[/var/puppet/state/state.yaml]: File does not exist
debug: /puppetconfig/main/File[/etc/puppet/ssl]: File does not exist
debug: /puppetconfig/main/File[/etc/puppet/ssl]: Changing ensure
debug: /puppetconfig/main/File[/etc/puppet/ssl]: 1 change(s)
debug: /puppetconfig/main/File[/etc/puppet/ssl]/ensure: setting directory (currently absent)
debug: /puppetconfig/main/File[/etc/puppet/ssl]/ensure: created
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/csr_puppet.example.com.pem]: File does not exist
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/public_keys]: File does not exist
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/public_keys]: Changing ensure
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/public_keys]: 1 change(s)
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/public_keys]/ensure: setting directory (currently absent)
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/public_keys]/ensure: created
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/public_keys/puppet.example.com.pem]: File does not exist
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private]: File does not exist
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private]: Changing ensure
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private]: 1 change(s)
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private]/ensure: setting directory (currently absent)
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private]/ensure: created
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private/password]: File does not exist
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private_keys]: File does not exist
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private_keys]: Changing ensure
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private_keys]: 1 change(s)
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private_keys]/ensure: setting directory (currently absent)
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private_keys]/ensure: created
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/private_keys/puppet.example.com.pem]: File does not exist
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/certs]: File does not exist
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/certs]: Changing ensure
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/certs]: 1 change(s)
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/certs]/ensure: setting directory (currently absent)
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/certs]/ensure: created
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/certs/ca.pem]: File does not exist
debug: /puppetconfig/ssl/File[/etc/puppet/ssl/certs/puppet.example.com.pem]: File does not exist
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca]: File does not exist
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca]: Changing ensure
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca]: 1 change(s)
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca]/ensure: setting directory (currently absent)
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca]/ensure: created
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_crt.pem]: File does not exist
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/inventory.txt]: File does not exist
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/private]: File does not exist
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/private]: Changing ensure
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/private]: 1 change(s)
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/private]/ensure: setting directory (currently absent)
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/private]/ensure: created
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/private/ca.pass]: File does not exist
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/requests]: File does not exist
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/requests]: Changing ensure
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/requests]: 1 change(s)
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/requests]/ensure: setting directory (currently absent)
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/requests]/ensure: created
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_key.pem]: File does not exist
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_pub.pem]: File does not exist
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/signed]: File does not exist
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/signed]: Changing ensure
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/signed]: 1 change(s)
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/signed]/ensure: setting directory (currently absent)
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/signed]/ensure: created
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/serial]: File does not exist
debug: /puppetconfig/ca/File[/etc/puppet/ssl/ca/ca_crl.pem]: File does not exist
debug: Finishing transaction 23774977915440 with 9 changes
debug: /puppetconfig/reporting/User[puppet]: Autorequiring Group[puppet]
debug: /puppetconfig/reporting/File[/var/puppet/reports]: Autorequiring Group[puppet]
debug: /puppetconfig/reporting/File[/var/puppet/reports]: Autorequiring User[puppet]
debug: Finishing transaction 23774977244460 with 0 changes
debug: /puppetconfig/metrics/User[puppet]: Autorequiring Group[puppet]
debug: /puppetconfig/metrics/File[/var/puppet/rrd]: Autorequiring Group[puppet]
debug: /puppetconfig/metrics/File[/var/puppet/rrd]: Autorequiring User[puppet]
debug: Finishing transaction 23774977139660 with 0 changes
debug: Creating interpreter
debug: importing '/etc/puppet/manifests/common.pp'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/parser/ast/function.rb:32:in `initialize'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/parser/parser_support.rb:60:in `new'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/parser/parser_support.rb:60:in `ast'
grammar.ra:371:in `_reduce_100'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/util/autoload.rb:75:in `_racc_yyparse_c'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/util/autoload.rb:75:in `catch'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/util/autoload.rb:75:in `_racc_yyparse_c'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/parser/lexer.rb:283:in `scan'
/usr/lib/ruby/1.8/racc/parser.rb:152:in `_racc_yyparse_c'
/usr/lib/ruby/1.8/racc/parser.rb:152:in `__send__'
/usr/lib/ruby/1.8/racc/parser.rb:152:in `yyparse'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/parser/parser_support.rb:397:in `parse'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/parser/parser_support.rb:199:in `import'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/parser/parser_support.rb:183:in `collect'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/parser/parser_support.rb:183:in `import'
grammar.ra:498:in `_reduce_134'
grammar.ra:497:in `each'
grammar.ra:497:in `_reduce_134'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/util/autoload.rb:75:in `_racc_yyparse_c'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/util/autoload.rb:75:in `catch'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/util/autoload.rb:75:in `_racc_yyparse_c'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/parser/lexer.rb:283:in `scan'
/usr/lib/ruby/1.8/racc/parser.rb:152:in `_racc_yyparse_c'
/usr/lib/ruby/1.8/racc/parser.rb:152:in `__send__'
/usr/lib/ruby/1.8/racc/parser.rb:152:in `yyparse'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/parser/parser_support.rb:397:in `parse'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/parser/interpreter.rb:651:in `parsefiles'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/util.rb:212:in `benchmark'
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
/usr/lib/ruby/1.8/benchmark.rb:307:in `realtime'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/util.rb:211:in `benchmark'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/parser/interpreter.rb:650:in `parsefiles'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/parser/interpreter.rb:327:in `initialize'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/network/handler/master.rb:124:in `new'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/network/handler/master.rb:124:in `initialize'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/network/server/webrick.rb:134:in `new'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/network/server/webrick.rb:134:in `setup_handlers'
/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `collect'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/network/server/webrick.rb:129:in `each'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/network/server/webrick.rb:129:in `collect'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/network/server/webrick.rb:129:in `setup_handlers'
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/network/server/webrick.rb:79:in `initialize'
/var/lib/gems/1.8/gems/puppet-0.23.2/bin/puppetmasterd:259:in `new'
/var/lib/gems/1.8/gems/puppet-0.23.2/bin/puppetmasterd:259
/var/lib/gems/1.8/bin/puppetmasterd:18:in `load'
/var/lib/gems/1.8/bin/puppetmasterd:18
err: Could not parse; using old configuration: Unknown function slash_escape at /etc/puppet/manifests/common.pp:63
debug: Finishing transaction 23774978581060 with 0 changes
info: Creating a new certificate request for puppet.example.com
info: Creating a new SSL key at /etc/puppet/ssl/private_keys/puppet.example.com.pem
info: Autosign is enabled but /etc/puppet/autosign.conf is missing
info: Signing certificate for CA server
info: Signing certificate for puppet.example.com
debug: /puppetconfig/puppetmasterd/File[/var/puppet/bucket]: Autorequiring Group[puppet]
debug: /puppetconfig/puppetmasterd/File[/var/puppet/bucket]: Autorequiring User[puppet]
debug: /puppetconfig/puppetmasterd/User[puppet]: Autorequiring Group[puppet]
debug: /puppetconfig/puppetmasterd/File[/etc/puppet/manifests/site.pp]: Autorequiring File[/etc/puppet/manifests]
debug: /puppetconfig/puppetmasterd/File[/var/puppet/log/puppetmaster.log]: Autorequiring Group[puppet]
debug: /puppetconfig/puppetmasterd/File[/var/puppet/log/puppetmaster.log]: Autorequiring User[puppet]
debug: /puppetconfig/puppetmasterd/File[/var/puppet/log/masterhttp.log]: Autorequiring Group[puppet]
debug: /puppetconfig/puppetmasterd/File[/var/puppet/log/masterhttp.log]: Autorequiring User[puppet]
debug: /puppetconfig/puppetmasterd/File[/etc/puppet/modules:/usr/share/puppet/modules]: File does not exist
debug: /puppetconfig/puppetmasterd/File[/etc/puppet/puppet.conf]: File does not exist
debug: /puppetconfig/puppetmasterd/File[/var/puppet/log/puppetmaster.log]: File does not exist
debug: Finishing transaction 23774978309320 with 0 changes
info: Listening on port 8140
notice: Starting Puppet server version 0.23.2
/var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet.rb:245:in `settraps': uninitialized constant Puppet::Network::Client::Master (NameError)
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `find'
from /var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet.rb:245:in `each'
from /var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet.rb:245:in `find'
from /var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet.rb:245:in `settraps'
from /var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/external/event-loop/event-loop.rb:127:in `call'
from /var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/external/event-loop/event-loop.rb:127:in `select'
from /var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/external/event-loop/event-loop.rb:127:in `select'
from /var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/external/event-loop/event-loop.rb:116:in `iterate'
from /var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet/external/event-loop/event-loop.rb:107:in `run'
from /var/lib/gems/1.8/gems/puppet-0.23.2/lib/puppet.rb:361:in `start'
from /var/lib/gems/1.8/gems/puppet-0.23.2/bin/puppetmasterd:306
from /var/lib/gems/1.8/bin/puppetmasterd:18:in `load'
from /var/lib/gems/1.8/bin/puppetmasterd:18
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
plathrop
| Ticket | Summary | Component | Milestone | Type | Severity | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #947 | pluginsync failure: can't convert nil into String in lib/puppet/network/handler/fileserver.rb:797 | server | misspiggy | defect | major | 12/03/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
When trying to pluginsync with default parameters, current HEAD ([8eecbe54c96cec0de492e7ae77211637b65057e8]) puppetmaster fails with this trace: debug: mount[plugins]: Listing /plugins for ic.black.co.at ./lib/puppet/network/handler/fileserver.rb:797:in `join' ./lib/puppet/network/handler/fileserver.rb:797:in `file_path' ./lib/puppet/network/handler/fileserver.rb:807:in `reclist' ./lib/puppet/network/handler/fileserver.rb:730:in `list' ./lib/puppet/network/handler/fileserver.rb:152:in `list' /usr/share/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:147:in `to_proc' ./lib/puppet/network/xmlrpc/processor.rb:52:in `call' ./lib/puppet/network/xmlrpc/processor.rb:52:in `protect_service' ./lib/puppet/network/xmlrpc/processor.rb:85:in `setup_processor' /usr/lib/ruby/1.8/xmlrpc/server.rb:336:in `call' /usr/lib/ruby/1.8/xmlrpc/server.rb:336:in `dispatch' /usr/lib/ruby/1.8/xmlrpc/server.rb:323:in `each' /usr/lib/ruby/1.8/xmlrpc/server.rb:323:in `dispatch' /usr/lib/ruby/1.8/xmlrpc/server.rb:366:in `call_method' /usr/lib/ruby/1.8/xmlrpc/server.rb:378:in `handle' ./lib/puppet/network/xmlrpc/processor.rb:44:in `process' ./lib/puppet/network/xmlrpc/webrick_servlet.rb:68:in `service' /usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service' /usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run' /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:95:in `start' /usr/lib/ruby/1.8/webrick/server.rb:92:in `each' /usr/lib/ruby/1.8/webrick/server.rb:92:in `start' /usr/lib/ruby/1.8/webrick/server.rb:23:in `start' /usr/lib/ruby/1.8/webrick/server.rb:82:in `start' ./lib/puppet.rb:336:in `start' ./lib/puppet.rb:187:in `newthread' ./lib/puppet.rb:186:in `initialize' ./lib/puppet.rb:186:in `new' ./lib/puppet.rb:186:in `newthread' ./lib/puppet.rb:334:in `start' ./lib/puppet.rb:333:in `each' ./lib/puppet.rb:333:in `start' ./bin/puppetmasterd:281 err: Could not call: can't convert nil into String I have prodded around the PluginMount class and I think the basic problem is that the data structure returned by Mount.list is *beep*. This amongst other things causes relpath = abspath.sub(%r{^#{basepath}}, '') in lib/puppet/network/handler/fileserver.rb:PluginMount:reclist() to not work in all cases, especially when the basepath changes from one module to the next. I have created a little patch that cleans up the Plugin Mount? class by overriding list instead of reclist and calling the original reclist for each module in turn. This surely needs more love to remove duplicates, but it does work on my puppetmaster now. Please find the patch in the rest/fix-plugins-mount branch of my repo at git://git.black.co.at/puppet-bugfixes |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
