[Puppet - Feature #2198] Install multiple package within a single call to the package manager
Issue #2198 has been updated by gorget. I'd like this feature request to be assigned to me. Feature #2198: Install multiple package within a single call to the package manager http://projects.reductivelabs.com/issues/2198 Author: gorget Status: Accepted Priority: Normal Assigned to: Category: transactions Target version: Complexity: Unknown Affected version: 0.25.0 Keywords: During the configuration applying process the package manager is called for each package installation. It is possible to reduce the number of calls to the package manager by gathering package installation and delayed some package installation. Naturally, this modification should not break the dependency graph. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Feature #2198] Install multiple package within a single call to the package manager
Issue #2198 has been updated by jamtur01. Assigned to set to gorget Target version set to unplanned Feature #2198: Install multiple package within a single call to the package manager http://projects.reductivelabs.com/issues/2198 Author: gorget Status: Accepted Priority: Normal Assigned to: gorget Category: transactions Target version: unplanned Complexity: Unknown Affected version: 0.25.0 Keywords: During the configuration applying process the package manager is called for each package installation. It is possible to reduce the number of calls to the package manager by gathering package installation and delayed some package installation. Naturally, this modification should not break the dependency graph. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Feature #286] (Closed) Support wildmat/regex matches
Issue #286 has been updated by gorget. Status changed from Re-opened to Closed luke wrote: My position here is that I hope to have a node classifier as a standard part of the infrastructure by the end of the year, which makes this not really worth implementing from my perspective. If someone else disagrees and wants to submit the code, I'd accept it. Ok, that makes sense, I will try to find an easy work around using regsubst or external node. Feature #286: Support wildmat/regex matches http://projects.reductivelabs.com/issues/286 Author: admin Status: Closed Priority: Normal Assigned to: luke Category: language Target version: unplanned Complexity: Hard Patch: None Affected version: 0.25.0 Keywords: Having wildmat/regex pattern matching for node, case, if, etc would be very powerful. Instead of assuming all strings are one type or another, one possibility would be to assume strings without any meta-chars to be an exact match, those with meta-chars to be interpreted wildmat (globbing), and those prefixed with re: (or %r) to be interpreted as regex. This maintains compatibility without surprises for those not using/familiar with regex. wildmat/globbing looks cleaner for common cases (eg node: farm* for matching all farmXXX hosts), but regex is more precise (thus i enjoy having both). -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Bug #2196] (Closed) Redhat logrotate restarts daemons multiple times
Issue #2196 has been updated by jamtur01. Status changed from Accepted to Closed Target version changed from unplanned to 0.25.0 Pushed in commit:dc0a9978df57b0ca730f9d90a132772474d34a5a in branch master. Bug #2196: Redhat logrotate restarts daemons multiple times http://projects.reductivelabs.com/issues/2196 Author: ianburrell Status: Closed Priority: Normal Assigned to: lutter Category: Red Hat Target version: 0.25.0 Complexity: Unknown Affected version: 0.24.7 Keywords: The redhat logrotate script restarts the puppet and puppetmaster services once per log file. On a server with multiple log files, this result in the services being restarted multiple times. There is a sharedscripts directive which causes the postrotate script to be run once instead of for each file. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Bug #2199] (Unreviewed) Puppetqd daemon fails
Issue #2199 has been reported by jamtur01. Bug #2199: Puppetqd daemon fails http://projects.reductivelabs.com/issues/2199 Author: jamtur01 Status: Unreviewed Priority: Normal Assigned to: Category: Target version: Complexity: Unknown Affected version: 0.24.7 Keywords: -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Bug #2200] (Unreviewed) Puppetqd daemon fails
Issue #2200 has been reported by jamtur01. Bug #2200: Puppetqd daemon fails http://projects.reductivelabs.com/issues/2200 Author: jamtur01 Status: Unreviewed Priority: Normal Assigned to: luke Category: plumbing Target version: 0.25.0 Complexity: Unknown Affected version: 0.24.7 Keywords: pre $ puppetqd /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetqd.rb:8:in `extend': wrong argument type Class (expected Module) (TypeError) from /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetqd.rb:8 from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:182:in `instance_eval' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:182:in `initialize' from /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetqd.rb:7:in `new' from /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetqd.rb:7 from /usr/bin/puppetqd:52:in `require' from /usr/bin/puppetqd:52 /pre -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Bug #2201] (Accepted) Puppetqd/stomp feature fails
Issue #2201 has been reported by jamtur01. Bug #2201: Puppetqd/stomp feature fails http://projects.reductivelabs.com/issues/2201 Author: jamtur01 Status: Accepted Priority: Normal Assigned to: luke Category: plumbing Target version: 0.25.0 Complexity: Unknown Affected version: 0.24.7 Keywords: I've installed the stomp gem: pre # gem install stomp /pre Then when I run puppetqd: pre # puppetqd /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetqd.rb:63:in `run_setup': Could not load the 'stomp' library, which must be present for queueing to work. You must install the required library. (ArgumentError) from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:216:in `run' from /usr/bin/puppetqd:53 /pre When I run irb - same issue: pre # irb irb(main):001:0 require 'stomp' LoadError: no such file to load -- stomp from (irb):1:in `require' from (irb):1 irb(main):002:0 /pre -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Bug #2202] (Accepted) Puppetqd/stomp feature fails
Issue #2202 has been reported by jamtur01. Bug #2202: Puppetqd/stomp feature fails http://projects.reductivelabs.com/issues/2202 Author: jamtur01 Status: Accepted Priority: Normal Assigned to: luke Category: plumbing Target version: 0.25.0 Complexity: Unknown Affected version: 0.24.7 Keywords: I've installed the stomp gem: pre # gem install stomp /pre Then when I run puppetqd: pre # puppetqd /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetqd.rb:63:in `run_setup': Could not load the 'stomp' library, which must be present for queueing to work. You must install the required library. (ArgumentError) from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:216:in `run' from /usr/bin/puppetqd:53 /pre When I run irb - same issue: pre # irb irb(main):001:0 require 'stomp' LoadError: no such file to load -- stomp from (irb):1:in `require' from (irb):1 irb(main):002:0 /pre -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Bug #2203] (Accepted) Puppetqd/stomp feature fails
Issue #2203 has been reported by jamtur01. Bug #2203: Puppetqd/stomp feature fails http://projects.reductivelabs.com/issues/2203 Author: jamtur01 Status: Accepted Priority: Normal Assigned to: luke Category: plumbing Target version: 0.25.0 Complexity: Unknown Affected version: 0.24.7 Keywords: I've installed the stomp gem: pre # gem install stomp /pre Then when I run puppetqd: pre # puppetqd /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetqd.rb:63:in `run_setup': Could not load the 'stomp' library, which must be present for queueing to work. You must install the required library. (ArgumentError) from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:216:in `run' from /usr/bin/puppetqd:53 /pre When I run irb - same issue: pre # irb irb(main):001:0 require 'stomp' LoadError: no such file to load -- stomp from (irb):1:in `require' from (irb):1 irb(main):002:0 /pre -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Bug #2191] (Accepted) Ruby 1.9 portability
Issue #2191 has been updated by jamtur01. Category set to plumbing Status changed from Unreviewed to Accepted Target version set to unplanned Fix for Facter pushed in commit:fa78cbdf4c67d0c8d20695e75ede70a1df950773 in Facter branch master (also in 1.5.x) Bug #2191: Ruby 1.9 portability http://projects.reductivelabs.com/issues/2191 Author: phantez Status: Accepted Priority: Normal Assigned to: Category: plumbing Target version: unplanned Complexity: Unknown Affected version: 0.25.0 Keywords: I tried to use Puppet and Facter (master version) with Ruby 1.9.1 on CentOS 5.2 and I succeed to make Facter work but I still have some errors : pre # facter Could not retrieve ipaddress_eth0: undefined method `each' for #String:0xa08ed8c Could not retrieve macaddress_eth0: undefined method `each' for #String:0xa08e724 Could not retrieve netmask_eth0: undefined method `each' for #String: 0xa08e0d0 Could not retrieve ipaddress_eth1: undefined method `each' for #String:0xa08da7c Could not retrieve macaddress_eth1: undefined method `each' for #String:0xa08d428 Could not retrieve netmask_eth1: undefined method `each' for #String: 0xa08cdd4 Could not retrieve ipaddress_sit0: undefined method `each' for #String:0xa2ea9c8 Could not retrieve macaddress_sit0: undefined method `each' for #String:0xa2ea374 Could not retrieve netmask_sit0: undefined method `each' for #String: 0xa2e9d20 Could not retrieve network_eth0: undefined method `each' for #String: 0xa5a274c Could not retrieve network_eth1: undefined method `each' for #String: 0xa5a1fb8 Could not retrieve network_sit0: undefined method `each' for #String: 0xa5a1824 Could not retrieve macaddress: undefined method `each' for #String: 0xa54acb8 Could not retrieve virtual: undefined method `each' for #String: 0xa55a6a4 Could not retrieve virtual: undefined method `each' for #String: 0xa559e98 architecture = i386 /pre ... and then it goes ok. but puppetmasterd doesn't work and the errors are : pre # puppetmasterd Could not autoload file: constant Puppet::Type::File not defined Could not autoload file: constant Puppet::Type::File not defined ... Could not autoload file: constant Puppet::Type::File not defined Could not autoload file: constant Puppet::Type::File not defined Invalid method to apply /pre -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Bug #2200] (Accepted) Puppetqd daemon fails
Issue #2200 has been updated by jamtur01. Status changed from Unreviewed to Accepted Bug #2200: Puppetqd daemon fails http://projects.reductivelabs.com/issues/2200 Author: jamtur01 Status: Accepted Priority: Normal Assigned to: luke Category: plumbing Target version: 0.25.0 Complexity: Unknown Affected version: 0.24.7 Keywords: pre $ puppetqd /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetqd.rb:8:in `extend': wrong argument type Class (expected Module) (TypeError) from /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetqd.rb:8 from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:182:in `instance_eval' from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:182:in `initialize' from /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetqd.rb:7:in `new' from /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetqd.rb:7 from /usr/bin/puppetqd:52:in `require' from /usr/bin/puppetqd:52 /pre -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Feature #1556] A type and provider for editing /etc/hosts.allow
Issue #1556 has been updated by khightower.
I would like this new feature assigned to me.
Feature #1556: A type and provider for editing /etc/hosts.allow
http://projects.reductivelabs.com/issues/1556
Author: johnw
Status: Accepted
Priority: Normal
Assigned to: community
Category: newfeature
Target version: unplanned
Complexity: Easy
Affected version: 0.24.5
Keywords:
At the moment I'm doing something like this:
pre
exec { allow-ssh:
command = echo 'sshd : ALL' /etc/hosts.allow,
onlyif = grep -qv ^sshd /etc/hosts.allow;
}
/pre
Would much prefer this:
pre
tcpwrapper { sshd:
ensure = allow, # default is to allow
hosts = ALL;
}
/pre
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://reductivelabs.com/redmine/my/account
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Puppet Bugs group.
To post to this group, send email to puppet-bugs@googlegroups.com
To unsubscribe from this group, send email to
puppet-bugs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en
-~--~~~~--~~--~--~---
[Puppet - Feature #1556] A type and provider for editing /etc/hosts.allow
Issue #1556 has been updated by jamtur01.
Assigned to changed from community to khightower
Feature #1556: A type and provider for editing /etc/hosts.allow
http://projects.reductivelabs.com/issues/1556
Author: johnw
Status: Accepted
Priority: Normal
Assigned to: khightower
Category: newfeature
Target version: unplanned
Complexity: Easy
Affected version: 0.24.5
Keywords:
At the moment I'm doing something like this:
pre
exec { allow-ssh:
command = echo 'sshd : ALL' /etc/hosts.allow,
onlyif = grep -qv ^sshd /etc/hosts.allow;
}
/pre
Would much prefer this:
pre
tcpwrapper { sshd:
ensure = allow, # default is to allow
hosts = ALL;
}
/pre
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://reductivelabs.com/redmine/my/account
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Puppet Bugs group.
To post to this group, send email to puppet-bugs@googlegroups.com
To unsubscribe from this group, send email to
puppet-bugs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en
-~--~~~~--~~--~--~---
[Puppet - Bug #2185] (Needs more information) --mkusers on Mac OS X 10.5 Server
Issue #2185 has been updated by jamtur01. Category set to OSX Status changed from Unreviewed to Needs more information Assigned to set to nigelk2 Target version set to unplanned Nigel - any ideas? Bug #2185: --mkusers on Mac OS X 10.5 Server http://projects.reductivelabs.com/issues/2185 Author: AllanMarcus Status: Needs more information Priority: Normal Assigned to: nigelk2 Category: OSX Target version: unplanned Complexity: Unknown Affected version: 0.24.8 Keywords: mac puppetmasterd mkusers I installed puppet via MacPorts on a 10.5 server.As root I ran the following command and received the following error. bash-3.2# puppetmasterd --mkusers Got 1 failure(s) while initializing: Failed to retrieve current state of resource: Could not determine OS X version -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Bug #2095] (Needs more information) Changing the permissions of /etc/puppet/puppet.conf via puppet crashes puppetmaster
Issue #2095 has been updated by jamtur01.
Status changed from Unreviewed to Needs more information
Target version set to unplanned
Trevor - what platform is this?
Bug #2095: Changing the permissions of /etc/puppet/puppet.conf via puppet
crashes puppetmaster
http://projects.reductivelabs.com/issues/2095
Author: TrevorHemsley
Status: Needs more information
Priority: Normal
Assigned to:
Category: file
Target version: unplanned
Complexity: Unknown
Affected version: 0.24.7
Keywords:
class puppetperms
{
file {/etc/puppet/puppet.conf:
owner = root,
group = root,
mode = 600
}
}
then invoke puppetd --test --tags puppetperms on the puppetmaster server
machine. The perms get changed, puppetmaster gets notified then crashes.
In syslog I see this
puppetd[6381]: (//Node[infra]/puppetperms/File[/etc/puppet/puppet.conf]/mode)
mode changed '644' to '600'
puppetd[6381]: Finished catalog run in 7.08 seconds
puppetmasterd[26866]: Reparsing /etc/puppet/puppet.conf
But puppetmaster is now dead.
Restart puppetmaster and all is OK again. Can happily run puppetd --test --tags
puppetperms while the perms are correct. Reset them via
chmod 700 /etc/puppet/puppet.conf
and puppetmaster immediately crashes without even running puppetd --test --tags
puppetperms.
BTW, puppetd does not run as a daemon on any of these machines, it's only run
manually.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://reductivelabs.com/redmine/my/account
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Puppet Bugs group.
To post to this group, send email to puppet-bugs@googlegroups.com
To unsubscribe from this group, send email to
puppet-bugs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en
-~--~~~~--~~--~--~---
[Puppet - Bug #2193] (Needs design decision) Exec's command parameter should accept lists in addition to strings
Issue #2193 has been updated by jamtur01. Status changed from Unreviewed to Needs design decision Assigned to set to luke Target version set to unplanned Bug #2193: Exec's command parameter should accept lists in addition to strings http://projects.reductivelabs.com/issues/2193 Author: grim_radical Status: Needs design decision Priority: Normal Assigned to: luke Category: exec Target version: unplanned Complexity: Unknown Affected version: 0.25.0 Keywords: Currently, exec executes its command by passing a string to Kernel#exec, which subjects the command to shell-expansion. There are many use cases where the user knows the exact command they wish to execute, and does not want the shell involved at all in the execution (say, for example, you're trying to pass an argument to a command that has weird characters in it that the shell would normally expand out). Exec's command param should accept a list as input, where the list follows the format accepted by Kernel#exec (If multiple arguments are given, the second and subsequent arguments are passed as parameters to command with no shell expansion.). I've attached a patch against 0.25 HEAD (minimally tested)...hopefully that can be a starting point for development. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Bug #2188] (Accepted) puppetmaster fails to start
Issue #2188 has been updated by luke. Status changed from Needs more information to Accepted Assigned to changed from luke to community I don't know that I've ever seen that error before. Bug #2188: puppetmaster fails to start http://projects.reductivelabs.com/issues/2188 Author: khightower Status: Accepted Priority: Normal Assigned to: community Category: plumbing Target version: 0.25.0 Complexity: Unknown Affected version: 0.25.0 Keywords: puppetmasterd While testing from HEAD I ran into the following error trying to start puppetmasterd in daemon mode. pre [r...@hawkins ~]# puppetmasterd --trace -D /usr/lib/ruby/site_ruby/1.8/puppet/simple_graph.rb:105:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:283:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:541:in `new' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:541:in `to_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:603:in `use' /usr/lib/ruby/1.8/sync.rb:229:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:597:in `use' /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetmasterd.rb:113:in `run_setup' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:216:in `run' /usr/sbin/puppetmasterd:66 /usr/lib/ruby/site_ruby/1.8/puppet/simple_graph.rb:105:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:283:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:541:in `new' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:541:in `to_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:603:in `use' /usr/lib/ruby/1.8/sync.rb:229:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:597:in `use' /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetmasterd.rb:124:in `run_setup' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:216:in `run' /usr/sbin/puppetmasterd:66 /usr/lib/ruby/site_ruby/1.8/puppet/simple_graph.rb:105:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:283:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:541:in `new' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:541:in `to_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:603:in `use' /usr/lib/ruby/1.8/sync.rb:229:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:597:in `use' /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate_authority.rb:140:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate_authority.rb:23:in `new' /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate_authority.rb:23:in `init_singleton_instance' /usr/lib/ruby/site_ruby/1.8/puppet/util/cacher.rb:92:in `send' /usr/lib/ruby/site_ruby/1.8/puppet/util/cacher.rb:92:in `cached_value' /usr/lib/ruby/site_ruby/1.8/puppet/util/cacher.rb:48:in `singleton_instance' /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate_authority.rb:37:in `instance' /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetmasterd.rb:125:in `run_setup' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:216:in `run' /usr/sbin/puppetmasterd:66 /usr/lib/ruby/site_ruby/1.8/puppet/simple_graph.rb:105:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:283:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:541:in `new' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:541:in `to_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:603:in `use' /usr/lib/ruby/1.8/sync.rb:229:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:597:in `use' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/ssl_file.rb:50:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:309:in `new' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:309:in `make_terminus' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:130:in `terminus' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:297:in `prepare' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:186:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/indirector.rb:51:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/ssl/host.rb:130:in `key' /usr/lib/ruby/site_ruby/1.8/puppet/ssl/host.rb:170:in `certificate' /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate_authority.rb:233:in `setup' /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate_authority.rb:146:in `initialize' /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate_authority.rb:23:in `new' /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate_authority.rb:23:in `init_singleton_instance' /usr/lib/ruby/site_ruby/1.8/puppet/util/cacher.rb:92:in `send' /usr/lib/ruby/site_ruby/1.8/puppet/util/cacher.rb:92:in `cached_value' /usr/lib/ruby/site_ruby/1.8/puppet/util/cacher.rb:48:in `singleton_instance' /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate_authority.rb:37:in `instance' /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetmasterd.rb:125:in `run_setup' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:216:in
[Puppet - Feature #2186] (Accepted) Some introspection capabilities about Files
Issue #2186 has been updated by luke. Status changed from Needs design decision to Accepted Assigned to changed from luke to community While I think this is a good idea, I think it's a good bit more work than is obvious. The simple cases are relatively simple - load the catalog and look for a file of that name. But the hard cases aren't that simple, because they require recursion. I'd accept this patch, but I think it's a good bit of work. And really, it's probably either a different executable focused on introspecting the catalog, or an addition to puppetd. Feature #2186: Some introspection capabilities about Files http://projects.reductivelabs.com/issues/2186 Author: phantez Status: Accepted Priority: Normal Assigned to: community Category: file Target version: unplanned Complexity: Unknown Affected version: 0.25.0 Keywords: Allow the user to ask some introspection query about files, the following examples use arbitrary options : * What is the reference file for a specific file ? pre # puppet /etc/puppet/manifest/site.pp --which-source-file /etc/sysconfig/security.conf Src file /etc/puppet/services/files/security.conf /pre * What is the difference between the actual file and the reference file ? pre # puppet /etc/puppet/manifest/site.pp --diff-with-reference-file /etc/sysconfig/security.conf 1c1,2 file1 --- file2 /pre * Which manifest define a specific file ? pre # puppet /etc/puppet/manifest/site.pp --which-manifest-file /etc/sysconfig/security.conf Content is defined in class security in '/etc/puppet/services/manifests/conf.pp' /pre I don't know which command should handle this request and how to manage the fact that the answers depend on the node and the facts, but I think that this features can be very useful to maintain manifests when there is several administrators. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Bug #2163] (Accepted) puppetrun does not know when client runs fail
Issue #2163 has been updated by luke. Subject changed from Puppetrun and puppetd disagree to puppetrun does not know when client runs fail Status changed from Needs more information to Accepted Assigned to changed from luke to community That's probably right. 'puppetrun' doesn't have good means of getting data back from the client. Of course, give that, puppetrun is correct - the run was triggered, it just doesn't know what happened next. Bug #2163: puppetrun does not know when client runs fail http://projects.reductivelabs.com/issues/2163 Author: pete Status: Accepted Priority: Normal Assigned to: community Category: executables Target version: unplanned Complexity: Unknown Affected version: 0.24.7 Keywords: I intentionally broke my puppet_node_classifier to see exit codes. See also: http://projects.reductivelabs.com/issues/2162 puppetd prints out that there is a problem: # /usr/sbin/puppetd --server=01.demo.test --test err: Could not retrieve catalog: Could not find node '01.demo.test'; cannot compile warning: Not using cache on failed catalog puppetrun, however, merrily thinks that everything is okay: # puppetrun --host=01.demo.test --foreground Failed to load ruby LDAP library. LDAP functionality will not be available Triggering 01.demo.test 01.demo.test finished with exit code 0 Finished The exit code I've submitted in the previous bug, but I think puppetrun should give me an indication of whether there were any problems with the run. Context, in case it's helpful: I'm controlling puppet via a web interface, and want to take an action across a cluster of machines, like upgrade these servers to a new version of an application. puppet_node_classifier pulls from a database, and then the nodes update themselves according to the rules laid out. I want to be able to indicate in the web interface whether the upgrade was successful or not. Currently, it looks to me that puppetrun is only reporting whether or not the trigger of a manual run was successful, and not whether the manual run itself was successful. Pete -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Bug #2193] (Accepted) Exec's command parameter should accept lists in addition to strings
Issue #2193 has been updated by luke. Status changed from Needs design decision to Accepted Target version changed from unplanned to 0.26.0 I'm fine with this (and it's customer work, so I'll get it done in the next release). Bug #2193: Exec's command parameter should accept lists in addition to strings http://projects.reductivelabs.com/issues/2193 Author: grim_radical Status: Accepted Priority: Normal Assigned to: luke Category: exec Target version: 0.26.0 Complexity: Unknown Affected version: 0.25.0 Keywords: Currently, exec executes its command by passing a string to Kernel#exec, which subjects the command to shell-expansion. There are many use cases where the user knows the exact command they wish to execute, and does not want the shell involved at all in the execution (say, for example, you're trying to pass an argument to a command that has weird characters in it that the shell would normally expand out). Exec's command param should accept a list as input, where the list follows the format accepted by Kernel#exec (If multiple arguments are given, the second and subsequent arguments are passed as parameters to command with no shell expansion.). I've attached a patch against 0.25 HEAD (minimally tested)...hopefully that can be a starting point for development. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~--~~~~--~~--~--~---
[Puppet - Bug #2188] puppetmaster fails to start
Issue #2188 has been updated by khightower.
Just tried the following on a clean VM:
pre
git clone git://reductivelabs.com/puppet
cd puppet/
ruby install.rb
useradd puppet
mkdir -p
/etc/puppet/ssl/{ca/{private,requests,signed},certificate_requests,certs,private_keys,public_keys}
mkdir -p /var/puppet/run/
chown puppet:puppet -R /etc/puppet/
chown puppet:puppet -R /var/puppet/run/
[r...@jake manifest]# puppetmasterd --trace -v
/usr/lib/ruby/site_ruby/1.8/puppet/simple_graph.rb:98:in `vertex_adjacencies'
/usr/lib/ruby/site_ruby/1.8/puppet/simple_graph.rb:49:in `has_edge?'
/usr/lib/ruby/site_ruby/1.8/puppet/simple_graph.rb:275:in `edge?'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:335:in
`relationship_graph'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:334:in `each'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:334:in
`relationship_graph'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:333:in `each'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:333:in
`relationship_graph'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:491:in `relationship_graph'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:487:in `prepare'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:274:in `evaluate'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:137:in `apply'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:615:in `use'
/usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:597:in `use'
/usr/lib/ruby/site_ruby/1.8/puppet/application/puppetmasterd.rb:113:in
`run_setup'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:216:in `run'
/usr/sbin/puppetmasterd:66
/usr/lib/ruby/site_ruby/1.8/puppet/simple_graph.rb:98:in `vertex_adjacencies'
/usr/lib/ruby/site_ruby/1.8/puppet/simple_graph.rb:49:in `has_edge?'
/usr/lib/ruby/site_ruby/1.8/puppet/simple_graph.rb:275:in `edge?'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:335:in
`relationship_graph'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:334:in `each'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:334:in
`relationship_graph'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:333:in `each'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:333:in
`relationship_graph'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:491:in `relationship_graph'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:487:in `prepare'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:274:in `evaluate'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:137:in `apply'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:615:in `use'
/usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:597:in `use'
/usr/lib/ruby/site_ruby/1.8/puppet/application/puppetmasterd.rb:124:in
`run_setup'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:216:in `run'
/usr/sbin/puppetmasterd:66
/pre
Puppet still does not start, but I did not see the error from the --trace
alone. Taken a look at /var/log/messages:
pre
Apr 21 19:42:36 jake puppetmasterd[3038]: Got an uncaught exception of type
NameError: uninitialized constant Puppet::SimpleGraph::VertexWrapper::Set
Apr 21 19:42:36 jake puppetmasterd[3038]: Got an uncaught exception of type
NameError: uninitialized constant Puppet::SimpleGraph::VertexWrapper::Set
Apr 21 19:42:36 jake puppetmasterd[3051]: Reopening log files
Apr 21 19:42:36 jake puppetmasterd[3051]: Starting Puppet server version
0.25.0beta1
/pre
Bug #2188: puppetmaster fails to start
http://projects.reductivelabs.com/issues/2188
Author: khightower
Status: Accepted
Priority: Normal
Assigned to: community
Category: plumbing
Target version: 0.25.0
Complexity: Unknown
Affected version: 0.25.0
Keywords: puppetmasterd
While testing from HEAD I ran into the following error trying to start
puppetmasterd in daemon mode.
pre
[r...@hawkins ~]# puppetmasterd --trace -D
/usr/lib/ruby/site_ruby/1.8/puppet/simple_graph.rb:105:in `initialize'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:283:in `initialize'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:541:in `new'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:541:in `to_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:603:in `use'
/usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:597:in `use'
/usr/lib/ruby/site_ruby/1.8/puppet/application/puppetmasterd.rb:113:in
`run_setup'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:216:in `run'
/usr/sbin/puppetmasterd:66
/usr/lib/ruby/site_ruby/1.8/puppet/simple_graph.rb:105:in `initialize'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:283:in `initialize'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:541:in `new'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:541:in `to_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:603:in `use'
/usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
