[Puppet - Bug #22643] (In Topic Branch Pending Review) Document /env/file_metadata/*

Issue #22643 has been updated by Kylo Ginsberg. Status changed from Investigating to In Topic Branch Pending Review Branch set to https://github.com/puppetlabs/puppet/pull/1961 Bug #22643: Document /env/file_metadata/*

[Puppet - Bug #22212] (Investigating) File Names with ? Cause Failures

Issue #22212 has been updated by Tristan Helmich. Status changed from Unreviewed to Investigating Assignee set to Tristan Helmich Bug #22212: File Names with ? Cause Failures https://projects.puppetlabs.com/issues/22212#change-98241 * Author: Celia

[Puppet - Bug #19149] puppet doc unable to create documentation of class when it encounters a hash of depth 1

Issue #19149 has been updated by simon marechal. Affected Puppet version changed from 3.1.0 to 3.3.0 This also happens when you have that kind of lines in the manifest : $sshChroot = { 'deploygroup' = '%h' } Bug #19149: puppet doc unable to create

[Puppet - Bug #22100] (Investigating) Provide note in Ruby Release Notes Warning that it only affects you if you specifically opt for ruby1.9 instead of the default

Issue #22100 has been updated by Yoann Le Touche. Category set to documentation Status changed from Unreviewed to Investigating Affected Puppet version set to 3.2.1 Keywords set to Ubuntu Precise, Ruby version Bug #22100: Provide note in Ruby Release

[Puppet - Bug #22212] File Names with ? Cause Failures

Issue #22212 has been updated by Tristan Helmich. Hi, can you give an example allowing us to recreate the issue (and specify which version is affected)? I successfully created a file containing a '?' with the following code (Puppet 3.2.4): pre file { '/srv/www/test?moretest': ensure =

[Puppet - Bug #22212] (Needs More Information) File Names with ? Cause Failures

Issue #22212 has been updated by Tristan Helmich. Category set to facter Status changed from Investigating to Needs More Information Assignee changed from Tristan Helmich to Celia Cottle Keywords changed from customer to customer file ? I’ve put this ticket’s status into “Needs more

[Puppet - Bug #22212] File Names with ? Cause Failures

Issue #22212 has been updated by Tristan Helmich. Category changed from facter to file selected wrong category, fixed. Bug #22212: File Names with ? Cause Failures https://projects.puppetlabs.com/issues/22212#change-98246 * Author: Celia Cottle *

[Puppet - Bug #22100] (In Topic Branch Pending Review) Provide note in Ruby Release Notes Warning that it only affects you if you specifically opt for ruby1.9 instead of the default

Issue #22100 has been updated by Yoann Le Touche. Status changed from Investigating to In Topic Branch Pending Review Pull request here: https://github.com/puppetlabs/puppet-docs/pull/224 Bug #22100: Provide note in Ruby Release Notes Warning that it

[Puppet - Bug #18880] (Needs More Information) compile with large number of defines is becoming very slow, ruby 1.9.3 is affected even more

Issue #18880 has been updated by Chris Spence. Status changed from Unreviewed to Needs More Information I have tried to recreate the catalog compile process, but need more of your code for any investigation to be meaningful. Without your other haproxy, nagios and perhaps other

[Puppet - Bug #22660] (Accepted) Use consistent puppet agent service name on all platforms

Issue #22660 has been updated by Jason Antman. Status changed from Unreviewed to Accepted Yes, this appears to be a bug. Looking at https://github.com/puppetlabs/puppet/pull/1166 my impression is that the change was unintended (which is backed up by the fact that fedora 17, which still uses

[Puppet - Bug #15735] (Re-opened) Deprecate 'puppet kick' run mode

Issue #15735 has been updated by Nikita Stupin. Status changed from Closed to Re-opened Target version changed from 3.0.0 to 3.x Please not deprecate puppet kick. We use puppet in some our projects, and not use mcollective, also don't plan use mcollective. Why? Mcollective is require mq

[Puppet - Bug #22563] 3.2.4 invalid byte sequence in US-ASCII for extlookup variables

Issue #22563 has been updated by Luke Alexander. Yes indeed we do have passenger running the puppetmaster via apache and inside the init script is the line: ENV=env -i LANG=C PATH=/usr/local/bin:/usr/bin:/bin This is with apache version: 2.2.22-13 (on wheezy) However, the same env line

[Puppet - Bug #18880] compile with large number of defines is becoming very slow, ruby 1.9.3 is affected even more

Issue #18880 has been updated by konrad rzentarzewski. i don't think that sharing our production config would be suitable - too much sensitive information. we worked around this problem by adding faster cpu. Bug #18880: compile with large number of

[Puppet - Bug #22595] (Duplicate) Invalid dot files generated by puppet when sql queries are involved.

Issue #22595 has been updated by Jason Antman. Status changed from Unreviewed to Duplicate Closing as duplicate of Bug #15531 Bug #22595: Invalid dot files generated by puppet when sql queries are involved.

[Puppet - Bug #22212] File Names with ? Cause Failures

Issue #22212 has been updated by Ken Barber. The example case here is something like: file { /tmp/foo: ensure = directory, recurse = true, purge = true, force = true, owner = root, group = root, mode = 0644, source =

[Puppet - Bug #20479] (Needs Decision) Puppet reports can contain invalid data that break puppet-dashboard.

Issue #20479 has been updated by Yoann Le Touche. Category set to reports Status changed from Unreviewed to Needs Decision Keywords set to Dashboard, Reports Needs decision. Should Dahsboard be able to process such report by changing the db schema like in #18411#note-8. or Should Puppet

[Puppet - Bug #22590] (Needs More Information) record resource evaluation time metrics in the report

Issue #22590 has been updated by Jason Antman. Status changed from Unreviewed to Needs More Information Assignee set to R.I. Pienaar R.I., what version of puppet is this affecting? Using a 3.3.0 agent and master, my reports (as stored on disk in

[Puppet - Bug #22590] record resource evaluation time metrics in the report

Issue #22590 has been updated by R.I. Pienaar. Hmm, I must have been looking at an old report then, we're all good :) thanks Bug #22590: record resource evaluation time metrics in the report https://projects.puppetlabs.com/issues/22590#change-98257 *

[Puppet - Bug #22590] (Rejected) record resource evaluation time metrics in the report

Issue #22590 has been updated by Jason Antman. Status changed from Needs More Information to Rejected Assignee deleted (R.I. Pienaar) Ok, thanks. Bug #22590: record resource evaluation time metrics in the report

[Puppet - Bug #22744] (In Topic Branch Pending Review) static compiler does not filter exported resources from the catalog

Issue #22744 has been updated by Chris Spence. Status changed from Unreviewed to In Topic Branch Pending Review Have updated the code and submitted a PR here https://github.com/puppetlabs/puppet/pull/1962 Bug #22744: static compiler does not filter

[Puppet - Bug #20479] Puppet reports can contain invalid data that break puppet-dashboard.

Issue #20479 has been updated by Yoann Le Touche. File site.pp added File 201310021201.yaml added Bug #20479: Puppet reports can contain invalid data that break puppet-dashboard. https://projects.puppetlabs.com/issues/20479#change-98260 * Author:

[Puppet - Bug #22212] File Names with ? Cause Failures (puppet:// fileserving a directory)

Issue #22212 has been updated by Tristan Helmich. Subject changed from File Names with ? Cause Failures to File Names with ? Cause Failures (puppet:// fileserving a directory) Description updated Category changed from file to fileserving Affected Puppet version set to 3.2.4 Keywords changed

[Puppet - Bug #22732] (Needs More Information) httplog and masterhttplog can be created with incorrect permissions when using WEBrick

Issue #22732 has been updated by Pablo Wright. Status changed from Unreviewed to Needs More Information Assignee set to Nick Lewis I'm having trouble reproducing this. Could you provide more information please? Specific versions, settings that deviate from default and sequence to reproduce

[Puppet - Bug #20479] Puppet reports can contain invalid data that break puppet-dashboard.

Issue #20479 has been updated by Yoann Le Touche. Added a new issue in puppet-dashboard #22759 Bug #20479: Puppet reports can contain invalid data that break puppet-dashboard. https://projects.puppetlabs.com/issues/20479#change-98263 * Author:

[Puppet - Bug #22710] (Investigating) Cannot run Sysem spec tests

Issue #22710 has been updated by Peter Souter. Category set to testing Status changed from Unreviewed to Investigating Assignee set to Peter Souter Bug #22710: Cannot run Sysem spec tests https://projects.puppetlabs.com/issues/22710#change-98264 *

[Facter - Bug #22290] facter fails when on non standard nic

Issue #22290 has been updated by Lee Lowder. Keywords set to customer Bug #22290: facter fails when on non standard nic https://projects.puppetlabs.com/issues/22290#change-98265 * Author: Ohad Basan * Status: Unreviewed * Priority: Normal * Assignee:

[Puppet - Bug #22333] (Needs Decision) puppet corrupts file if non-ascii character found

Issue #22333 has been updated by Kurt Sussman. Status changed from Unreviewed to Needs Decision Tested with Puppet 3.3.0 on Ubuntu Precise amd64 using the apt Ruby 1.9.3-p0 (also tried the default 1.8.7), and could not duplicate. The change was made successfully with the comment line copied

[Puppet - Bug #22710] Cannot run Sysem spec tests

Issue #22710 has been updated by Peter Souter. Hi Dolf, It looks like a environment issue that's probably best solved with bundler. In the repo could you do: $ gem install bundler Then run $ bundle install $ bundle exec rake spec $ bundle exec rake spec_system Should fix the dependancy

[Puppet - Feature #18787] (Accepted) Include information about why a provider is unsuitable

Issue #18787 has been updated by Rob Nelson. Status changed from Unreviewed to Accepted Seems like a reasonable request, triaged as part of the Oct 2013 Triage-a-Thon. Feature #18787: Include information about why a provider is unsuitable

[Puppet - Bug #22491] (Accepted) apt provider doesn't allow packages to be downgraded with ensure=latest

Issue #22491 has been updated by Kurt Sussman. Status changed from Unreviewed to Accepted Affected Puppet version changed from 3.2.2 to 3.3.0 Verified with Ubuntu Precise amd64, Ruby 1.9.3-p0 and Puppet 3.3.0. Pinned package isn't downgraded by puppet run, but 'apt-get upgrade' will downgrade

[Puppet - Bug #22438] (Closed) import shouldn't error out when there is no file matching the file pattern

Issue #22438 has been updated by Peter Souter. Status changed from Unreviewed to Closed Assignee changed from eric sorenson to Peter Souter Hi Eric, This is intentional behaviour for the puppet run, as it will error out if it tries to load something and it doesn't exist. The work-around, as

[Puppet - Feature #21103] Add puppet yum provider retry operation

Issue #21103 has been updated by Klavs Klavsen. I was trying to implement this feature, in my puppet ruleset: Exec['expire yum cache'] - Package | tag != 'virtual' | exec { expire yum cache: command = /usr/bin/yum clean expire-cache, refreshonly = true } Package { subscribe =

[Puppet - Feature #19258] (Needs More Information) please provide ability for install_options for the portage provider

Issue #19258 has been updated by Rob Nelson. Status changed from Unreviewed to Needs More Information Assignee set to Theo Chatzimichos Theo, some time has elapsed and line 123 doesn't look to be relevant anymore, do you mean

[Puppet - Bug #22212] File Names with ? Cause Failures (puppet:// fileserving a directory)

Issue #22212 has been updated by Tristan Helmich. Assignee deleted (Celia Cottle) Bug #22212: File Names with ? Cause Failures (puppet:// fileserving a directory) https://projects.puppetlabs.com/issues/22212#change-98278 * Author: Celia Cottle *

[Puppet - Feature #19259] (Accepted) ability to show emerge -q output for portage provider

Issue #19259 has been updated by Rob Nelson. Category set to provider Status changed from Unreviewed to Accepted Seems like a reasonable request, triaged as part of the Oct 2013 Triage-a-Thon. Feature #19259: ability to show emerge -q output for portage

[Puppet - Feature #19258] please provide ability for install_options for the portage provider

Issue #19258 has been updated by Theo Chatzimichos. Rob Nelson wrote: Theo, some time has elapsed and line 123 doesn't look to be relevant anymore, do you mean https://github.com/gentoo/puppet-portage/blob/master/manifests/package.pp#L181 or somewhere else? Please CP the snippet for

[Puppet - Feature #19258] (Needs More Information) please provide ability for install_options for the portage provider

Issue #19258 has been updated by Rob Nelson. Status changed from Needs Decision to Needs More Information Assignee changed from Rob Nelson to Theo Chatzimichos Great! Now, what about an example of how you are dealing with this now, and how you think a future implementation might look?

[Puppet - Feature #19188] (Needs Decision) configurable behavior with non-existing hiera variables

Issue #19188 has been updated by Rob Nelson. Status changed from Unreviewed to Needs Decision Assignee set to Peter Meier Needs decision, assigning to Peter Meier. Feature #19188: configurable behavior with non-existing hiera variables

[Puppet - Feature #19472] (Rejected) Would like to see the ability to selectively sync facts.

Issue #19472 has been updated by Rob Nelson. Status changed from Unreviewed to Rejected Trevor, you appear to be asking for puppet to determine what work needs to be done before it determines what work needs to be done. While this might be feasible in some situations, the amount of work

[Puppet - Bug #22729] (Investigating) New future-parser-only functions are loaded although one is not using the future parser

Issue #22729 has been updated by Charlie Sharpsteen. Status changed from Unreviewed to Investigating Bug #22729: New future-parser-only functions are loaded although one is not using the future parser

[Puppet - Feature #19556] (Closed) Meta resource type as a container for multiple resource types

Issue #19556 has been updated by Rob Nelson. Status changed from Unreviewed to Closed In addition to using anchors, you could put the packages in another class, something like module::install::deps, and require = module::install::deps wherever you need it.

[Puppet - Feature #19786] (Accepted) Error messages should include puppet master that was connected to.

Issue #19786 has been updated by Rob Nelson. Status changed from Unreviewed to Accepted Seems like a reasonable request, triaged as part of the Oct 2013 Triage-a-Thon. Feature #19786: Error messages should include puppet master that was connected to.

[Puppet - Feature #19902] (Needs Decision) Flexible configuration for agent SSL handling

Issue #19902 has been updated by Rob Nelson. Status changed from Unreviewed to Needs Decision Needs a decision from the product owner. Feature #19902: Flexible configuration for agent SSL handling

[Puppet - Feature #19473] (Needs Decision) Provide the ability to mark directories as non-parseable.

Issue #19473 has been updated by Rob Nelson. Status changed from Unreviewed to Needs Decision Feature request, needs decision. Feature #19473: Provide the ability to mark directories as non-parseable.

[Puppet - Feature #19258] please provide ability for install_options for the portage provider

Issue #19258 has been updated by Theo Chatzimichos. Apologies for the lack of information. Right now, I need to write my own exec resource, with the arguments I need for the emerge command. One example is the snippet I gave earlier (Let me know if you need more examples). In this example, I

[Puppet - Feature #19258] (Needs Decision) please provide ability for install_options for the portage provider

Issue #19258 has been updated by Theo Chatzimichos. Status changed from Needs More Information to Needs Decision Assignee changed from Theo Chatzimichos to Rob Nelson Feature #19258: please provide ability for install_options for the portage provider

[Puppet - Bug #22762] (Unreviewed) Puppet uses inherited unclean environment when starting services

Issue #22762 has been reported by Kristian Glass. Bug #22762: Puppet uses inherited unclean environment when starting services https://projects.puppetlabs.com/issues/22762 * Author: Kristian Glass * Status: Unreviewed * Priority: Normal * Assignee: *

[Puppet - Bug #22121] (Investigating) Documentation about testing for existence of variable in template is subtly wrong

Issue #22121 has been updated by Yoann Le Touche. Status changed from Unreviewed to Investigating Assignee set to Yoann Le Touche Keywords set to template, test, variable Bug #22121: Documentation about testing for existence of variable in template is

[Puppet - Bug #21935] (Needs Decision) Puppet agent will raise an unhelpful exception if client returns a non-numeric result.

Issue #21935 has been updated by Alexander Fortin. Status changed from Unreviewed to Needs Decision Seems that it has been fixed in 3.3.0: precode # puppet --version; ruby --version ; puppet agent --onetime --no-daemonize --server fake-server; echo $? 3.3.0 ruby 1.9.3p194 (2012-04-20 revision

[Puppet - Bug #22729] New future-parser-only functions are loaded although one is not using the future parser

Issue #22729 has been updated by Henrik Lindberg. It is difficult to provide an easy fix for this because there is no mechanism in the auto loader to make it continue its search if a found file contains something that is disqualified. An implementation could raise an exception (or throw

[Puppet - Bug #22539] passwd key is set incorrectly when managing root's password using the puppet user provider

Issue #22539 has been updated by Nigel Kersten. Odd. This does in fact look to be a bug with only the root user account. Verified that managing a non-root user works fine. The original bug report described the problem as being Puppet making the password entry a single string rather than an

[Puppet - Feature #19484] (Needs Decision) Maintenance task for the filebucket

Issue #19484 has been updated by Rob Nelson. Status changed from Unreviewed to Needs Decision Feature request, needs decision from product owner. Feature #19484: Maintenance task for the filebucket

[Puppet - Bug #22539] (Accepted) authentication_authority key is not set when managing root's password using the puppet user provider

Issue #22539 has been updated by Nigel Kersten. Status changed from Unreviewed to Accepted Bug #22539: authentication_authority key is not set when managing root's password using the puppet user provider

[Puppet - Feature #19561] (Needs More Information) Providers should be able to extend the type they implement

Issue #19561 has been updated by Rob Nelson. Status changed from Unreviewed to Needs More Information Assignee set to Anthony Ryan Anthony, can you provide some examples of what you are implementing currently and how you envision a fix would be implemented? At first blush this sounds

[Puppet - Bug #22366] (Needs Decision) The future parser validator doesn't catch using bad resource types in collection queries

Issue #22366 has been updated by Alexander Fortin. Status changed from Unreviewed to Needs Decision Still reproducible in v3.3.0 precode # ruby --version; puppet --version; puppet apply --parser=future -e '1||' ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux] 3.3.0 Error: Resource type

[Puppet - Bug #22539] authentication_authority key is not set when managing root's password using the puppet user provider

Issue #22539 has been updated by Nate Walck. That is correct. I thought the second item may be relevant, but it turns out that it is not. I had tested it manually as well, but forgot to update the bug report. Thanks! Bug #22539:

[Puppet - Bug #22121] Documentation about testing for existence of variable in template is subtly wrong

Issue #22121 has been updated by Yoann Le Touche. From the documentation : [...] Thus, testing @variable for nil is the best option available right now. The has_variable? function should probably just go away, but removing it will definitely break existing code. To check if a variable is

[Puppet - Bug #21935] Puppet agent will raise an unhelpful exception if client returns a non-numeric result.

Issue #21935 has been updated by Josh Partlow. Sadly, I'm still seeing this on 3.3.1-rc2, at least running a source checkout With a running puppet master at puppetmaster $ bundle exec puppet agent -t --server puppetmaster To establish a good cert Then $ bundle exec puppet agent

[Puppet - Bug #22121] (Closed) Documentation about testing for existence of variable in template is subtly wrong

Issue #22121 has been updated by Yoann Le Touche. Status changed from Investigating to Closed Bug #22121: Documentation about testing for existence of variable in template is subtly wrong https://projects.puppetlabs.com/issues/22121#change-98321 *

[Puppet - Bug #22121] Documentation about testing for existence of variable in template is subtly wrong

Issue #22121 has been updated by Thomas Vander Stichele. If @variable.nil? works, then that's great! Did you notice that this section of the documentation is a) very long and b) *does not contain the solution written out* ? It's great that it tells you you should test for nil, but it doesn't

[Puppet - Feature #19350] (Rejected) Stateful Cleanup Messages

Issue #19350 has been updated by Rob Nelson. Status changed from Unreviewed to Rejected The posture of puppet is manage what you specify, and only what you specify. At this time there is no goal to remove unmanaged resources in general or unmanage during a delta. If you wish to specifically

[Puppet - Bug #22212] File Names with ? Cause Failures (puppet:// fileserving a directory)

Issue #22212 has been updated by Nigel Kersten. Here's a simpler manifest to reproduce the issue without a puppet master: pre file { '/tmp/source': ensure = directory, } file { 'problem_file': ensure = file, path = '/tmp/source/?', } file { '/tmp/dest': ensure = directory,

[Puppet - Bug #22121] Documentation about testing for existence of variable in template is subtly wrong

Issue #22121 has been updated by Yoann Le Touche. At the start of the section you have the short version of the explanation telling you to test if @variable is nil Short version: When testing for undefinedness, check whether the instance variable (@variable) is nil – if the corresponding

[Puppet - Bug #22212] (Investigating) File Names with ? Cause Failures (puppet:// fileserving a directory)

Issue #22212 has been updated by Nigel Kersten. Status changed from Needs More Information to Investigating Bug #22212: File Names with ? Cause Failures (puppet:// fileserving a directory) https://projects.puppetlabs.com/issues/22212#change-98325 *

[Puppet - Bug #22282] (Needs Decision) Invalid version string '1'! when using puppet module install

Issue #22282 has been updated by Alexander Fortin. Status changed from Unreviewed to Needs Decision Can't reproduce it with 3.3.0 pre # ruby --version; puppet --version; HTTPS_PROXY=http://proxy.lan:3128 HTTP_PROXY=$HTTPS_PROXY puppet module install camptocamp/ruby ruby 1.9.3p194 (2012-04-20

[Puppet - Feature #18882] (Accepted) Report # of relationships in --summarize

Issue #18882 has been updated by Rob Nelson. Subject changed from Report # of edges in --summarize to Report # of relationships in --summarize Status changed from Unreviewed to Accepted Assignee set to Ken Barber Assigning to Ken. Feature #18882:

[Puppet - Bug #22212] (Accepted) File Names with ? cause failures with recursive copies

Issue #22212 has been updated by Nigel Kersten. Subject changed from File Names with ? Cause Failures (puppet:// fileserving a directory) to File Names with ? cause failures with recursive copies Status changed from Investigating to Accepted Bug #22212:

[Puppet - Bug #22366] (Accepted) The future parser validator doesn't catch using bad resource types in collection queries

Issue #22366 has been updated by Henrik Lindberg. Status changed from Needs Decision to Accepted The validator should catch this and give better error message. Bug #22366: The future parser validator doesn't catch using bad resource types in collection

[Puppet - Bug #19972] (Accepted) puppet doc fails against forge.puppetlabs.com/ispavailability/logstash

Issue #19972 has been updated by Yoann Le Touche. Status changed from Unreviewed to Accepted Bug #19972: puppet doc fails against forge.puppetlabs.com/ispavailability/logstash https://projects.puppetlabs.com/issues/19972#change-98334 * Author: James

[Puppet - Bug #22582] (Investigating) Puppet ignores schedules

Issue #22582 has been updated by Nigel Kersten. Status changed from Unreviewed to Investigating Are you sure this actually fixed it Jan? I'm seeing the same problem with `ruby 1.9.3p448 (2013-06-27 revision 41675) [x86_64-linux]` and this simple standalone manifest: pre define

[Puppet - Feature #22640] (Needs Decision) puppetlabs_spec_helper only supports Git

Issue #22640 has been updated by Justin Holguin. Tracker changed from Bug to Feature Status changed from Unreviewed to Needs Decision Assignee set to Branan Purvine-Riley Keywords set to SCM, mercurial, puppetlabs_spec_helper Assigning this to Branan just because he has the most commits to this

[Puppet - Bug #22582] (Rejected) Puppet ignores schedules

Issue #22582 has been updated by Nigel Kersten. Status changed from Investigating to Rejected Actually, let me correct that. The schedule type always shows that output, it's irrelevant to this issue. Rejecting this bug as it's no longer an issue for the reporter.

[Puppet - Bug #22539] authentication_authority key is not set when managing root's password using the puppet user provider

Issue #22539 has been updated by Nigel Kersten. (the formatting above isn't quite working the way diff -u should, but this should indicate where the problem lies) Bug #22539: authentication_authority key is not set when managing root's password using

[Puppet - Bug #22116] certificate clean or revoke does not work with passenger

Issue #22116 has been updated by Nigel Kersten. Description updated Bug #22116: certificate clean or revoke does not work with passenger https://projects.puppetlabs.com/issues/22116#change-98341 * Author: Sami Kerola * Status: Unreviewed * Priority:

[Puppet - Feature #19561] (Needs Decision) Providers should be able to extend the type they implement

Issue #19561 has been updated by Anthony Ryan. Status changed from Needs More Information to Needs Decision Assignee changed from Anthony Ryan to Rob Nelson To provide a concrete example, I maintain a replacement for the default portage.rb provider that adds support for use flags, keywords and

[Puppet - Feature #21515] (Needs Decision) user_role_add provider can't handle local users in LDAP environment

Issue #21515 has been updated by Justin Holguin. Tracker changed from Bug to Feature Status changed from Unreviewed to Needs Decision Assignee set to eric sorenson Going off of the referenced ticket (#7911), the request appears to be for a local provider to optionally override LDAP for

[Puppet - Feature #10111] Puppet should deprecate the use of CRLs and move towards OCSP

Issue #10111 has been updated by Nigel Kersten. Do we have any updates here? Feature #10111: Puppet should deprecate the use of CRLs and move towards OCSP https://projects.puppetlabs.com/issues/10111#change-98345 * Author: Nigel Kersten * Status: Code

[Puppet - Bug #22145] (Needs More Information) Puppet Agent fails (with stack trace) when run through passenger/rack and a dupe UID exists for a user

Issue #22145 has been updated by Yoann Le Touche. Status changed from Unreviewed to Needs More Information Assignee set to Tom Vachon To try to reproduce the problem we will need some more information : - Manifest or part of the manifest with the user creation posing problem - Does this user

[Puppet - Bug #21739] puppet cert generate on a new host may leave the host unable to initialize ssl

Issue #21739 has been updated by Nigel Kersten. Was this really with the same puppet.conf settings? I just reproduced this on CentOS 6, and I can't see any way that there's an actual OS difference here. I suspect it's actually a difference in configuration.

[Puppet - Bug #21739] (Needs More Information) puppet cert generate on a new host may leave the host unable to initialize ssl

Issue #21739 has been updated by Nigel Kersten. Status changed from Unreviewed to Needs More Information Bug #21739: puppet cert generate on a new host may leave the host unable to initialize ssl https://projects.puppetlabs.com/issues/21739#change-98349

[Puppet - Bug #19955] Misleading error when Hiera databindings fail

Issue #19955 has been updated by Andrew Parker. Branch changed from https://github.com/puppetlabs/puppet/pull/1941 to https://github.com/puppetlabs/puppet/pull/1964 Did some more cleanup to the change and opened https://github.com/puppetlabs/puppet/pull/1964

[Puppet - Bug #18982] (Closed) Mount type doesnt handle SELinux context for NFS

Issue #18982 has been updated by Rob Nelson. Status changed from Unreviewed to Closed It appears this issue is patched and 2.6.17 is now EOL. Closing. Bug #18982: Mount type doesnt handle SELinux context for NFS

[Puppet - Feature #20176] (Accepted) puppet describe type should indicate which providers are avaiable via confines for the local system

Issue #20176 has been updated by Rob Nelson. Status changed from Unreviewed to Accepted Accepted, needs a product owner. Feature #20176: puppet describe type should indicate which providers are avaiable via confines for the local system

[Puppet - Bug #22455] (Needs Decision) Changing a variable in a custom fact, after the fact changes the earlier set fact

Issue #22455 has been updated by Justin Holguin. Category set to facter Status changed from Unreviewed to Needs Decision Assignee set to eric sorenson Priority changed from High to Normal Keywords set to facter, ruby I was able to replicate this behavior with facter 1.7.3/ruby 1.8.7.

[Puppet - Bug #19242] (Needs More Information) The static compiler does not infer the puppet server as a file source.

Issue #19242 has been updated by Justin Holguin. Status changed from Unreviewed to Needs More Information Would you please verify that this issue still affects the current version of puppet? It looks like a number of changes have been made to the way files are handled since 3.1.0.

[Puppet - Bug #20305] (Needs More Information) Selinux type appears to be changed prior to acting on the object.

Issue #20305 has been updated by Pablo Wright. Status changed from Unreviewed to Needs More Information Assignee set to Trevor Vaughan Tried to reproduce on a standard CentOS 6.4 install and selinux enforcing with Puppet 3.3.0 since 2.7.x went EOL, but it seemed to do both the unlink and the

[Puppet - Bug #22766] (Unreviewed) Fix rubygem-json rpm file permissions

Issue #22766 has been reported by Paul Tittle. Bug #22766: Fix rubygem-json rpm file permissions https://projects.puppetlabs.com/issues/22766 * Author: Paul Tittle * Status: Unreviewed * Priority: Normal * Assignee: * Category: * Target version: *

[Puppet - Bug #21198] hiera calling_module / calling_class not set for automatic parameter lookups

Issue #21198 has been updated by Andrew Parker. Merged into master in [d6fce02](https://github.com/puppetlabs/puppet/commit/d6fce029f8d21f4e2cfb0ecacf61f482f808577a) Bug #21198: hiera calling_module / calling_class not set for automatic parameter

[Puppet - Bug #21198] hiera calling_module / calling_class not set for automatic parameter lookups

Issue #21198 has been updated by Andrew Parker. Oops...updated the wrong ticket Bug #21198: hiera calling_module / calling_class not set for automatic parameter lookups https://projects.puppetlabs.com/issues/21198#change-98370 * Author: Robert Frank

[Puppet - Bug #19955] (Merged - Pending Release) Misleading error when Hiera databindings fail

Issue #19955 has been updated by Andrew Parker. Status changed from In Topic Branch Pending Review to Merged - Pending Release Merged into master in [d6fce0](https://github.com/puppetlabs/puppet/commit/d6fce029f8d21f4e2cfb0ecacf61f482f808577a) Bug

[Puppet - Feature #17843] (Accepted) Add splay option support for 'puppet inspect' runs

Issue #17843 has been updated by Rob Nelson. Status changed from Unreviewed to Accepted Support Urls deleted (https://support.puppetlabs.com/tickets/1709) Marking as accepted based on Eric's escalation Feature #17843: Add splay option support

[Puppet - Feature #20095] (Accepted) Add support for managing home directories to directoryservice provider on OS X

Issue #20095 has been updated by Rob Nelson. Status changed from Unreviewed to Accepted Assignee set to Nigel Kersten Accepted, assigning to Nigel Kersten. Feature #20095: Add support for managing home directories to directoryservice provider on OS X

[Puppet - Feature #20170] (Needs Decision) puppet describe type should list `defaultto` values

Issue #20170 has been updated by Rob Nelson. Status changed from Unreviewed to Needs Decision This needs a decision by the product owner. Embedding the default value in the description could cause a discrepancy with the actual defaultto value, but would require updating many descriptions

[Puppet - Feature #19561] Providers should be able to extend the type they implement

Issue #19561 has been updated by Rob Nelson. Assignee deleted (Rob Nelson) This needs a decision from the product owner. Feature #19561: Providers should be able to extend the type they implement https://projects.puppetlabs.com/issues/19561#change-98380

[Puppet - Feature #18873] (Needs Decision) Puppet should have a type to change SMF settings on Solaris 11

Issue #18873 has been updated by Rob Nelson. Status changed from Unreviewed to Needs Decision Needs decision from product owner, does this go in core or remain in puppet-solaris? Feature #18873: Puppet should have a type to change SMF settings on

[Facter - Bug #22622] (Accepted) Puppet 3.3.0 and Facter completely broken on Windows Server 2003

Issue #22622 has been updated by Josh Cooper. Status changed from Investigating to Accepted Bug #22622: Puppet 3.3.0 and Facter completely broken on Windows Server 2003 https://projects.puppetlabs.com/issues/22622#change-98388 * Author: Martijn

[Puppet - Feature #20785] (Needs Decision) hiera hash priority

Issue #20785 has been updated by Rob Nelson. Status changed from Unreviewed to Needs Decision Needs decision from product owner. Feature #20785: hiera hash priority https://projects.puppetlabs.com/issues/20785#change-98389 * Author: Chris Denneen *

[Puppet - Feature #20758] (Needs Decision) Accessing arguments in exported resource collection override for override.

Issue #20758 has been updated by Rob Nelson. Status changed from Unreviewed to Needs Decision In spite of how awesome this feature may be, it still needs a decision from the product owner. Feature #20758: Accessing arguments in exported resource

[Puppet - Feature #20375] (Accepted) Alternate README file locations for global __site__ level documentation

Issue #20375 has been updated by Rob Nelson. Status changed from Unreviewed to Accepted Marking as accepted by Charlie Feature #20375: Alternate README file locations for global __site__ level documentation

[Puppet - Bug #22043] (Needs More Information) Catalog retrieval request unnecessarily double escapes facts

Issue #22043 has been updated by Pablo Wright. Status changed from Unreviewed to Needs More Information Tried to reproduce on Puppet 3.3.0, I hit /production/catalog/{certname}, /production/facts/{certname}, /production/facts_search/search?facts.{somefact} but no dice, things look fine.

  1   2   3   4   5   6   7   8   9   10   >