[Puppet - Bug #18092] (Unreviewed) network device - enable password with a sharp is not correctly parsed

Issue #18092 has been reported by Guillaume Rose. Bug #18092: network device - enable password with a sharp is not correctly parsed https://projects.puppetlabs.com/issues/18092 Author: Guillaume Rose Status: Unreviewed Priority: Normal Assignee:

[Puppet - Bug #18092] network device - enable password with a sharp is not correctly parsed

Issue #18092 has been updated by Guillaume Rose. I wrote a patch for [this](https://github.com/puppetlabs/puppet/pull/1327). Bug #18092: network device - enable password with a sharp is not correctly parsed

[Puppet - Bug #17287] CentOS client ensuring package every run when set to purge not absent

Issue #17287 has been updated by Dean Wilson. I'm seeing this on puppet-2.7.19-1.el5 too. # adds an extra notice $ puppet apply -e 'package { yum-priorities: ensure = 'purged', provider = 'yum' }' --verbose notice: /Stage[main]//Package[yum-priorities]/ensure: created**

[Puppet - Bug #18093] (Unreviewed) Case and selectors don't work

Issue #18093 has been reported by Guillaume Fenollar. Bug #18093: Case and selectors don't work https://projects.puppetlabs.com/issues/18093 Author: Guillaume Fenollar Status: Unreviewed Priority: Normal Assignee: Category: modules Target version:

[Puppet - Feature #16856] (Needs More Information) puppet should support data in modules

Issue #16856 has been updated by R.I. Pienaar. Status changed from Investigating to Needs More Information I've updated my pull request incorporating these items and the stuff from the list about the default hierarchy. the problem with the backend only being there by default when using

[Puppet - Bug #17564] Puppet stops applying catalog updates once in a while

Issue #17564 has been updated by Hari Sekhon. I understand the request but unfortunately there is no way to actively reproduce this problem. Run a large scale infrastructure with the same standardized version of clients and puppetmasters (2.7.12 right now) in 4xmongrel+apache balancer

[Puppet - Bug #16277] (Duplicate) Initialise Puppet settings before running tests to enable autoloader

Issue #16277 has been updated by Josh Cooper. Status changed from Investigating to Duplicate Target version changed from 3.x to 3.1.0 Jeff McCune wrote: I find it strange that the second invocation works, but the first doesn't. This leads me to suspect

[Puppet - Bug #15529] Puppet settings should be initialized prior to running any tests and reinitialized before each test

Issue #15529 has been updated by Josh Cooper. Subject changed from puppetlabs_spec_helper: autoload files from installed modules to Puppet settings should be initialized prior to running any tests and reinitialized before each test Description updated

[Puppet - Bug #15529] Puppet settings should be initialized prior to running any tests and reinitialized before each test

Issue #15529 has been updated by Josh Cooper. Description updated Bug #15529: Puppet settings should be initialized prior to running any tests and reinitialized before each test https://projects.puppetlabs.com/issues/15529#change-78677 Author: Dominic

[Facter - Bug #17925] (In Topic Branch Pending Review) Could not retrieve ec2_userdata: 404 Not Found

Issue #17925 has been updated by Jeff McCune. Status changed from Accepted to In Topic Branch Pending Review Branch set to https://github.com/puppetlabs/hiera/pull/98 # Pull Request https://github.com/puppetlabs/hiera/pull/98 I'll have this merged in and up shortly. -Jeff

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

Issue #17925 has been updated by Jeff McCune. Branch changed from https://github.com/puppetlabs/hiera/pull/98 to https://github.com/puppetlabs/facter/pull/375 Bug #17925: Could not retrieve ec2_userdata: 404 Not Found

[Facter - Bug #17925] (Merged - Pending Release) Could not retrieve ec2_userdata: 404 Not Found

Issue #17925 has been updated by Jeff McCune. Status changed from In Topic Branch Pending Review to Merged - Pending Release Target version changed from 1.6.x to 1.6.17 # Merged into 1.6.x And up through master as 656c5ae. This fix will be released in Facter 1.6.17. -Jeff

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

Issue #15496 has been updated by Andrew Parker. Branch changed from https://github.com/puppetlabs/puppet/pull/1323 to https://github.com/puppetlabs/puppet/pull/1330 Cleaned up the tests some. Opened a new pull request. Bug #15496: Puppet incorrectly

[Puppet - Bug #15837] (Tests Insufficient) [PATCH] Fix mount with options specified on Linux

Issue #15837 has been updated by Jeff McCune. Status changed from Needs More Information to Tests Insufficient Priority changed from High to Normal Also, I don’t really know how to write a test for puppet at all; and would be very thankful if someone could assist. Hopefully the text above is

[Facter - Feature #11663] Add FreeBSD support to blockdevice fact(s)

Issue #11663 has been updated by Jeff McCune. Assignee deleted (Adrien Thebo) I'm reviewing this now. I hope to merge it or provide next actions ASAP. -Jeff Feature #11663: Add FreeBSD support to blockdevice fact(s)

[Puppet - Bug #15496] (Merged - Pending Release) Puppet incorrectly determining offset for certain timezones

Issue #15496 has been updated by Andrew Parker. Status changed from In Topic Branch Pending Review to Merged - Pending Release Target version set to 3.1.0 Merged in https://github.com/puppetlabs/puppet/commit/3a63d287bc06615479c3fe99a2f3eb4842530121 Bug

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

Issue #15496 has been updated by Andrew Parker. Affected Puppet version set to 2.7.12 Bug #15496: Puppet incorrectly determining offset for certain timezones https://projects.puppetlabs.com/issues/15496#change-78685 Author: Ken Johnson Status: Merged -

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

Issue #15496 has been updated by Andrew Parker. Assignee deleted (eric sorenson) Bug #15496: Puppet incorrectly determining offset for certain timezones https://projects.puppetlabs.com/issues/15496#change-78686 Author: Ken Johnson Status: Merged -

[Facter - Feature #11663] (Code Insufficient) Add FreeBSD support to blockdevice fact(s)

Issue #11663 has been updated by Jeff McCune. Status changed from In Topic Branch Pending Review to Code Insufficient Please see my comments for next actions in the pull request at https://github.com/puppetlabs/facter/pull/248. -Jeff Feature #11663:

[Facter - Feature #17612] (In Topic Branch Pending Review) Facter didn't recognize Google Compute Engine VM as virtual ressources

Issue #17612 has been updated by Jeff McCune. Category set to cloud - gce Status changed from Accepted to In Topic Branch Pending Review Branch set to https://github.com/puppetlabs/facter/pull/354 # Pull request https://github.com/puppetlabs/facter/pull/354

[Facter - Feature #17612] Facter didn't recognize Google Compute Engine VM as virtual ressources

Issue #17612 has been updated by Jeff McCune. Branch changed from https://github.com/puppetlabs/facter/pull/354 to https://github.com/puppetlabs/facter/pull/376 New pull request using sysfs approach in addition to the lspci approach: https://github.com/puppetlabs/facter/pull/376

[Facter - Feature #17612] (Merged - Pending Release) Facter didn't recognize Google Compute Engine VM as virtual ressources

Issue #17612 has been updated by Jeff McCune. Status changed from In Topic Branch Pending Review to Merged - Pending Release Target version set to 1.7.0 # merged into 1.7.x As a43d6f8 This functionality will be released in Facter 1.7.0 -Jeff Feature

[Facter - Feature #17612] Facter didn't recognize Google Compute Engine VM as virtual ressources

Issue #17612 has been updated by Jeff McCune. Josh Cooper wrote: Hi Pierre-Gilles, do you know of any publicly documented way to determine this information reliably, e.g. API, command? I see `gcutil`, but perhaps there's a better way? This is mentioned in the YARD API docs and in the

[Puppet - Bug #7580] (Code Insufficient) puppet always try to change user's gid on LDAP with same value.

Issue #7580 has been updated by Jeff McCune. Status changed from Tests Insufficient to Code Insufficient Please see next actions in the pull request at https://github.com/puppetlabs/puppet/pull/1291. Basically, I suspect this change in behavior should be implemented in the

[Puppet - Bug #3947] puppet executable does not load all ruby files from modulepath/MODULENAME/lib

Issue #3947 has been updated by Josh Cooper. Target version changed from 3.x to 3.1.0 To follow up on Andy's comment, when running `puppet agent`, the libdir will be in the $LOAD_PATH, so `Kernel.require` will be able to load utility code (specified as a relative path) from your pluginsync'ed

[Puppet - Bug #17136] puppet node doesn't respect ssldir from puppet.conf

Issue #17136 has been updated by Josh Cooper. Description updated Bug #17136: puppet node doesn't respect ssldir from puppet.conf https://projects.puppetlabs.com/issues/17136#change-78747 Author: Johan van den Dorpe Status: Needs More Information

[Puppet - Bug #15214] (Needs More Information) Get rid of coupling between run_mode and confdir/vardir

Issue #15214 has been updated by Josh Cooper. Status changed from Accepted to Needs More Information Assignee changed from Andrew Parker to Jeff McCune Can we close this as a dup of #16637, now that vardir and confdir are no longer dependent on run_mode?

[Puppet - Bug #17136] (Closed) puppet node doesn't respect ssldir from puppet.conf

Issue #17136 has been updated by Josh Cooper. Status changed from Needs More Information to Closed Target version deleted (3.1.0) Hi Johan, in puppet 2.7.x, the clean action would set the global run_mode to master, so that puppet would search in the master section. The coupling of run_mode