[Puppet - Bug #17994] (Unreviewed) Symbolic file modes when creating directories: Wrong permissions

Issue #17994 has been reported by Daniel Grafe. Bug #17994: Symbolic file modes when creating directories: Wrong permissions https://projects.puppetlabs.com/issues/17994 Author: Daniel Grafe Status: Unreviewed Priority: Normal Assignee: Category:

[Puppet - Bug #17371] Setting owner, group, mode for files specified in puppet.conf no longer seems to work

Issue #17371 has been updated by Dominic Cleal. Branch changed from https://github.com/puppetlabs/puppet/pull/1278 to https://github.com/puppetlabs/puppet/pull/1316 I've rebased it onto master and submitted a new PR. Bug #17371: Setting owner, group,

[Puppet - Bug #17995] Package is being reinstalled every time when using debian backports

Issue #17995 has been updated by Matthaus Owens. Project changed from Puppet Community Package Repository to Puppet Moving to the main Puppet project as this isn't a packaging issue. Bug #17995: Package is being reinstalled every time when using debian

[Puppet - Bug #16651] Installing the cloud provisioner module breaks the node subcommand

Issue #16651 has been updated by Josh Cooper. The fix in progress for #7136 adds the current environment's modulepath to the $LOAD_PATH prior to requiring the face. This enables the face application to require utility code (require 'puppet/cloudpack'). However, we are now running into

[Puppet - Feature #18013] (Unreviewed) Support for Microsoft .msu packages

Issue #18013 has been reported by Luis Mayorga. Feature #18013: Support for Microsoft .msu packages https://projects.puppetlabs.com/issues/18013 Author: Luis Mayorga Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected

[Puppet - Feature #16804] scheduled_task : add support for every X minutes or hours mode

Issue #16804 has been updated by Matthaus Owens. Project changed from Puppet Enterprise (Public) to Puppet Moving to the Puppet project, as this is not a PE feature, but rather a Puppet feature. Feature #16804: scheduled_task : add support for every X

[Facter - Bug #17925] Could not retrieve ec2_userdata: 404 Not Found

Issue #17925 has been updated by Jeff McCune. Project changed from Puppet to Facter Bug #17925: Could not retrieve ec2_userdata: 404 Not Found https://projects.puppetlabs.com/issues/17925#change-78320 Author: Banio Carpenter Status: Accepted Priority:

[Puppet - Bug #17879] extract cert name properly from subject DN

Issue #17879 has been updated by Yuri Arabadji. Related. pre Ignoring --listen on onetime run /usr/local/rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/net/http.rb:799: warning: exception in verify_callback is ignored Warning: Unable to fetch my node definition, but the agent run will continue:

[Puppet - Bug #15496] Puppet incorrectly determining offset for certain timezones

Issue #15496 has been updated by Sean Millichamp. The timezone we are using is America/Caracas: http://www.timeanddate.com/worldclock/city.html?n=58 As you can see from that link, the current UTC offset is -04:30 but the timestamps in the Puppet report, generated during a

[Puppet - Bug #15496] Puppet incorrectly determining offset for certain timezones

Issue #15496 has been updated by Sean Millichamp. Assignee changed from Sean Millichamp to eric sorenson Bug #15496: Puppet incorrectly determining offset for certain timezones https://projects.puppetlabs.com/issues/15496#change-78329 Author: Ken

[Facter - Feature #7559] Fact for identifying Amazon VPC instances.

Issue #7559 has been updated by Josh Cooper. Ryan Coleman wrote: Would it help to make this fact a module that is distributed through the Puppet Forge instead of making a part of core Facter? Those running in EC2 can install the module and pluginsync the fact to their agents. It would for

[Facter - Feature #7559] Fact for identifying Amazon VPC instances.

Issue #7559 has been updated by Justin Lambert. Ryan Coleman wrote: Would it help to make this fact a module that is distributed through the Puppet Forge instead of making a part of core Facter? Those running in EC2 can install the module and pluginsync the fact to their agents. It would

[Puppet - Feature #16804] (Accepted) scheduled_task : add support for every X minutes or hours mode

Issue #16804 has been updated by Josh Cooper. Status changed from Unreviewed to Accepted Keywords set to windows Unfortunately, we can't support every X minutes because Windows scheduled tasks (version 1) don't support it. The newer v2 APIs for creating scheduled tasks do support it, but

[Puppet - Feature #18013] (Accepted) Support for Microsoft .msu packages

Issue #18013 has been updated by Josh Cooper. Status changed from Unreviewed to Accepted Keywords set to windows Hi Luis, can you update the ticket with the commands you use to install and uninstall an msu package? Feature #18013: Support for Microsoft

[Facter - Bug #17925] Could not retrieve ec2_userdata: 404 Not Found

Issue #17925 has been updated by Jeff McCune. I believe this problem is caused by Facter not accounting for the situation where the EC2 metadata server returns a 404 if there is no user-data set for the instance. I'm going to write a small patch to take this scenario into account which

[Puppet - Bug #17880] When master is not a CA

Issue #17880 has been updated by Yuri Arabadji. disregard err: Could not retrieve catalog; skipping run error, that was from old puppet 2.6.x. Now, with puppet 3.0.1, with `hostcrl` setting pointing to non-existent file, it spits out pre Warning: Unable to fetch my node definition, but the

[Puppet - Bug #15496] Puppet incorrectly determining offset for certain timezones

Issue #15496 has been updated by eric sorenson. We implement yaml with zaml, and which incorrectly handles fractional negative tz offsets: pre lib/puppet/util/zaml.rb 375 class Time 376 def to_zaml(z) 377 # 2008-12-06 10:06:51.373758 -07:00 378 ms = (%0.6f % (usec * 1e-6))[2..-1]

[Puppet - Feature #18013] Support for Microsoft .msu packages

Issue #18013 has been updated by Luis Mayorga. I wish i know :). I guess is documented here http://support.microsoft.com/kb/934307. My question is if i can use the windows provider on Puppet for Windows. Feature #18013: Support for Microsoft .msu

[Puppet - Bug #17989] (Closed) Cannot install Puppet on Red Hat Enterprise Linux Server release 6.3 (Santiago) due to rubygem-json

Issue #17989 has been updated by Phoenix Zeus. Status changed from Unreviewed to Closed Assignee set to Phoenix Zeus As no one else had a chance to look at it, here is how I solved and found a work around. The issue was the rubygems rpm which is part of rhel-x86_64-server-optional-6

[Puppet - Bug #15329] Puppet lacks a proper undefined value

Issue #15329 has been updated by Reid Vandewiele. Thanks for clarifying. Everything is starting to make more sense now. :-) I understand the use case for `undef` when used as I described. When using the DSL I've actually never thought to try and use undef to override a defined resource

[Puppet - Bug #18021] (Unreviewed) daemontools service provider ignores restart command

Issue #18021 has been reported by Amos Shapira. Bug #18021: daemontools service provider ignores restart command https://projects.puppetlabs.com/issues/18021 Author: Amos Shapira Status: Unreviewed Priority: Normal Assignee: Category: provider Target

[Puppet - Bug #17616] Package update via Gem provider fails when running Puppet via bundler

Issue #17616 has been updated by Josh Nichols. I've run into this too. Basically, bundler 'infects' the environment to make sure any rubygems things go through bundler, so if the gem isn't in the Gemfile, `gem install` won't see it. To get around that, Bundler has a `Bundler.with_clean_env`

[Puppet - Feature #16804] scheduled_task : add support for every X minutes or hours mode

Issue #16804 has been updated by Josh Cooper. I meant to say we don't currently support as opposed to can't support. We could create a new scheduled_task provider to support these capabilities and confine it to Vista or later. There are a variety of ways to accomplish this (schtasks.exe,

[Puppet - Bug #17305] puppet module build fails with Error: undefined method `downcase' for nil:NilClass

Issue #17305 has been updated by Josh Cooper. I'm not able to reproduce this with 3.0.0 or later. I think it is a dup of #13070, but Jeff can you confirm? Bug #17305: puppet module build fails with Error: undefined method `downcase' for nil:NilClass

[Puppet - Feature #4248] Load library plugins that are used by multiple puppet functions and delivered via pluginsync

Issue #4248 has been updated by Josh Cooper. The proposed fix for #7316 will ensure an application can require custom facts, types, providers, applications, faces and actions from the modulepath or gem, and that code can in turn require utility code, also from the modulepath or gem. However,

[Puppet - Bug #16651] Installing the cloud provisioner module breaks the node subcommand

Issue #16651 has been updated by Josh Cooper. And the trace: pre Error: Could not autoload puppet/face/node_aws/bootstrap: --tags=: already defined in puppet /Users/josh/work/puppet/lib/puppet/interface/option.rb:31:in `initialize' /Users/josh/work/puppet/lib/puppet/interface/option.rb:13:in

[Puppet - Bug #16753] Need the ability to list all nodes

Issue #16753 has been updated by Andrew Parker. Branch changed from https://github.com/puppetlabs/puppet/pull/1305 to https://github.com/puppetlabs/puppet/pull/1317 Fixed a few issues in Henrik's changes. New pull request submitted. Bug #16753: Need the

[Puppet - Feature #16426] Publish API documentation automatically

Issue #16426 has been updated by eric sorenson. Keywords changed from documentation, docs, yard, API to documentation docs yard API backlog Feature #16426: Publish API documentation automatically

[Puppet - Bug #18023] (Accepted) Puppet needs a public, clearly-defined Ruby API

Issue #18023 has been reported by eric sorenson. Bug #18023: Puppet needs a public, clearly-defined Ruby API https://projects.puppetlabs.com/issues/18023 Author: eric sorenson Status: Accepted Priority: Normal Assignee: eric sorenson Category: Target

[Puppet - Feature #18024] (Unreviewed) Make a shorthand alias for scope.lookupvar()

Issue #18024 has been reported by Yuri Arabadji. Feature #18024: Make a shorthand alias for scope.lookupvar() https://projects.puppetlabs.com/issues/18024 Author: Yuri Arabadji Status: Unreviewed Priority: Normal Assignee: Category: Target version:

[Puppet - Bug #17305] (Duplicate) puppet module build fails with Error: undefined method `downcase' for nil:NilClass

Issue #17305 has been updated by Jeff McCune. Status changed from Needs More Information to Duplicate Assignee deleted (Jeff McCune) Josh Cooper wrote: I'm not able to reproduce this with 3.0.0 or later. I think it is a dup of #13070, but Jeff can you confirm? Confirmed. -Jeff

[Puppet - Bug #17156] Regression: Can't restrict the plugins loaded by puppet doc with --modulepath in 3.0.1

Issue #17156 has been updated by Josh Cooper. I'm digging into this issue as it relates to #7316. I'm actually having trouble reproducing the problem, see comments below: Nick Fagerlund wrote: In 3.0.0, puppet doc would ONLY load plugins from the modulepath; the contents of the agent’s

[Puppet - Bug #16753] Need the ability to list all nodes

Issue #16753 has been updated by Andrew Parker. The new implementation can be turned off by doing the following in puppet.conf. pre [master] node_cache_terminus = /pre The code given in the original report should work, but you can also use the `puppet node` subcommand by creating a routes

[Facter - Feature #7559] Fact for identifying Amazon VPC instances.

Issue #7559 has been updated by Ryan Coleman. Josh Cooper wrote: Ryan Coleman wrote: Would it help to make this fact a module that is distributed through the Puppet Forge instead of making a part of core Facter? Those running in EC2 can install the module and pluginsync the fact to

[Facter - Feature #7559] Fact for identifying Amazon VPC instances.

Issue #7559 has been updated by Ryan Coleman. Justin Lambert wrote: Ryan Coleman wrote: Would it help to make this fact a module that is distributed through the Puppet Forge instead of making a part of core Facter? Those running in EC2 can install the module and pluginsync the fact to

[Puppet - Bug #16753] Need the ability to list all nodes

Issue #16753 has been updated by Andrew Parker. Turns out that the routes file isn't needed at all. The same thing can be achieved by using the `--node_terminus` parameter. pre puppet node search '*' --node_terminus yaml --clientyamldir `puppet master --configprint yamldir` /pre

[Puppet - Bug #16753] (Merged - Pending Release) Need the ability to list all nodes

Issue #16753 has been updated by Andrew Parker. Status changed from In Topic Branch Pending Review to Merged - Pending Release Assignee deleted (Henrik Lindberg) Merged in https://github.com/puppetlabs/puppet/commit/86f7e5e4106e00d2b87f7f385a4a65815dae61fd

[Facter - Feature #7559] Fact for identifying Amazon VPC instances.

Issue #7559 has been updated by Jeff McCune. The course we plan to pursue is: 1. Confine the metadata API availability check to `virtual = xenu` in an effort to limit this network call to a subset of Facter users. 2. Confine the metadata API check to a x millisecond timeout. Amazon says the

[Facter - Feature #7559] Fact for identifying Amazon VPC instances.

Issue #7559 has been updated by James Turnbull. Looks good. Will 3. be faster than can_connect? Thanks Jeff! Feature #7559: Fact for identifying Amazon VPC instances. https://projects.puppetlabs.com/issues/7559#change-78412 Author: Nigel Kersten

[Facter - Feature #7559] Fact for identifying Amazon VPC instances.

Issue #7559 has been updated by Michael Arnold. Jeff McCune wrote: Thoughts? Does item 3 break on openstack or eucalyptus? Otherwise, outside of any issues with the timeout, I think this is an acceptable solution. Feature #7559: Fact for identifying

[Puppet - Bug #8974] class variable access from toplevel warnings in bsd service

Issue #8974 has been updated by Josh Cooper. Branch set to https://github.com/puppetlabs/puppet/pull/444 Bug #8974: class variable access from toplevel warnings in bsd service https://projects.puppetlabs.com/issues/8974#change-78414 Author: Max Lincoln

[Puppet - Bug #17713] (Accepted) upstart service provider throws warning: class variable access from toplevel

Issue #17713 has been updated by Josh Cooper. Description updated Status changed from Unreviewed to Accepted Hi Andrew, thanks for patch, but that means we'll check the version for each upstart package, since each package resource has it's own provider instance. I think we probably want to do

[Puppet - Bug #18021] daemontools service provider ignores restart command

Issue #18021 has been updated by Amos Shapira. I've created a pull request with a suggested fix: https://github.com/puppetlabs/puppet/pull/1318 It was tested with puppet 2.7.20 installed from gem on fedora 15 Bug #18021: daemontools service provider

[Puppet - Bug #7316] (In Topic Branch Pending Review) puppet face applications (subcommands) delivered via modules should work

Issue #7316 has been updated by Josh Cooper. Status changed from Code Insufficient to In Topic Branch Pending Review Branch set to https://github.com/puppetlabs/puppet/pull/1319 Bug #7316: puppet face applications (subcommands) delivered via modules

[Puppet - Bug #17951] (Needs More Information) Windows package provider does not re-run installation when subscription updates

Issue #17951 has been updated by Josh Cooper. Status changed from Unreviewed to Needs More Information Hi Andrew, the windows package provider will consider the resource to be insync if the package with that name is installed. So for example, if your package name doesn't contain a version

[Puppet - Feature #16804] scheduled_task : add support for every X minutes or hours mode

Issue #16804 has been updated by Pascal Sartoretti. Maybe support for Windows Server 2003 is not required, as this OS is already in Extended Support phase (no more in Mainstream Support phase), and will be terminated in 2015. Feature #16804: