Jira (PUP-1347) AIX user provider changes gecos field on every run if comment is ''
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1347
AIX user provider changes gecos field on every run if comment is ''
Issue Type:
Bug
Assignee:
Unassigned
Created:
03/Jan/14 1:20 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
if you define the following test class
user { 'aixtest': comment = '', }
puppet is going to change the geocs (comment) field on every run, executing `chuser gecos= aixtest`. this happens because
lsuser -c aixtest
does not include the gecos field if it is empty. just change the class to
user { 'aixtest': comment = 'aixtest', }
and it only gets changed once, as `lsuser -c aixtest` now reports the gecos field.
thanks toni
Add Comment
Jira (PUP-1346) Implement changes for AIX Memory facts (already commited)
Title: Message Title redmine.exporter created an issue Puppet / PUP-1346 Implement changes for AIX Memory facts (already commited) Issue Type: New Feature Assignee: Unassigned Created: 03/Jan/14 1:20 AM Labels: redmine Priority: Normal Reporter: redmine.exporter We are running facter 1.7.3 on AIX systems and they are not reporting memorysize and memoryfree facts. This has already been implemented on May 31st 2013 according to the git history: Commit: 183b2ba4035cd0e532a7bfcb90047c816a4dfd4d (#20994) fix incorrect memoryfree fact on AIX (was set to 0) Commit: b739a96626a5bbc48ffa99a5b5f3fb9ce5f8bf83 (#20994) fix incorrectly set memorysize on AIX using svmon (was set to 0) Please pull these in for the next release as they are not implemented in 1.7.2 and 1.7.3 Add Comment
Jira (PUP-1348) Support for Microsoft .msu packages
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1348
Support for Microsoft .msu packages
Issue Type:
New Feature
Assignee:
Unassigned
Created:
03/Jan/14 1:22 AM
Labels:
redmine customer
Priority:
Normal
Reporter:
redmine.exporter
[ED: SO SORRY, hit the wrong button and deleted the whole thread instead of my comment.]
Hi,
I had to download a .msu package to include Powershell 3.0 on my Windows 7 Machine. Is there any support with Puppet using the Package Resource Type?
Related to Puppet - Feature #16991: Puppet should support *.msp upgrade packages on Windows Accepted History
#1 UPDATED BY JOSH COOPER 10 MONTHS AGO 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?
#2 UPDATED BY LUIS MAYORGA 10 MONTHS AGO 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.
#3 UPDATED BY LUIS MAYORGA 10 MONTHS AGO class ps3{ file { 'ps3': name = 'C:\Temp\WMF30.msu', ensure = present, source = 'puppet:///puppetfs/WMF30.msu' }
exec { 'ps3': command = 'C:\Windows\System32\wusa.exe C:\Temp\WMF30.msu /quiet /norestart /log C:\Temp\Poweshellv3.htm', require = [File[ps3],Class[netfx45]] }
} #4 UPDATED BY JOSH COOPER 9 MONTHS AGO Luis
Jira (PUP-1349) improve error message when File[undef] occurs
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1349
improve error message when File[undef] occurs
Issue Type:
Bug
Assignee:
Unassigned
Created:
03/Jan/14 1:28 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
If you create a File resource from a variable that is not defined, the error message doesn't mention the position in the manifest nor the class name that the problematic resource occurs in. This makes it difficult to find out which File resource is broken.
$ echo 'file { $foo: ensure = present }
' | puppet apply Error: Failed to apply catalog: Parameter path failed on File[undef]: File paths must be fully qualified, not 'undef'
Add Comment
Jira (PUP-1347) PR (2215): Don't replace original stacktrace when error happens parsing inline template - carlossg
Title: Message Title gepetto-bot created an issue Puppet / PUP-1347 PR (2215): Don't replace original stacktrace when error happens parsing inline template - carlossg Issue Type: Task Assignee: Unassigned Components: Community Created: 03/Jan/14 1:40 AM Priority: Normal Reporter: gepetto-bot Don't replace original stacktrace when error happens parsing inline template Author: Carlos Sanchez git...@carlossanchez.eu Company: Github ID: carlossg Pull Request 2215 Discussion Pull Request 2215 File Diff Pull Request Description Helps with debugging errors in template before Puppet::Error: Failed to parse inline template: `@32bit_packages' is not allowed as an instance variable name at
Jira (PUP-1350) PR (2215): Don't replace original stacktrace when error happens parsing inline template - carlossg
Title: Message Title gepetto-bot created an issue Puppet / PUP-1350 PR (2215): Don't replace original stacktrace when error happens parsing inline template - carlossg Issue Type: Task Assignee: Unassigned Components: Community Created: 03/Jan/14 1:40 AM Labels: github Priority: Normal Reporter: gepetto-bot Don't replace original stacktrace when error happens parsing inline template Author: Carlos Sanchez git...@carlossanchez.eu Company: Github ID: carlossg Pull Request 2215 Discussion Pull Request 2215 File Diff Pull Request Description
Jira (PUP-1351) Load ext/packaging/packaging.rake instead of ext/packaging/tasks/**
Title: Message Title Sam Kottler created an issue Puppet / PUP-1351 Load ext/packaging/packaging.rake instead of ext/packaging/tasks/** Issue Type: Improvement Affects Versions: 2.7.24 Assignee: Sam Kottler Components: Community Created: 03/Jan/14 2:59 AM Priority: Normal Reporter: Sam Kottler This currently gets printed each time rake gets executed, updating to just load the packaging.rake will prevent that. DEPRECATED: The packaging repo tasks are now loaded by 'packaging.rake'. Please update your Rakefile or loading task to load 'ext/packaging/packaging.rake' instead of 'ext/packaging/tasks/*' (25-Jun-2013). Add Comment
Jira (PUP-1350) PR (2215): Don't replace original stacktrace when error happens parsing inline template - carlossg
Title: Message Title gepetto-bot commented on an issue Re: PR (2215): Don't replace original stacktrace when error happens parsing inline template - carlossg puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1350 PR (2215): Don't replace original stacktrace when error happens parsing inline template - carlossg h2. Don't replace original stacktrace when error happens parsing inline template * Author: Carlos Sanchez git...@carlossanchez.eu * Company: * Github ID: [carlossg|https://github.com/carlossg] * [Pull Request 2215 Discussion|https://github.com/puppetlabs/puppet/pull/2215] * [Pull Request 2215 File Diff|https://github.com/puppetlabs/puppet/pull/22... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1347) PR (2215): Don't replace original stacktrace when error happens parsing inline template - carlossg
Title: Message Title gepetto-bot commented on an issue Re: PR (2215): Don't replace original stacktrace when error happens parsing inline template - carlossg puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1347 PR (2215): Don't replace original stacktrace when error happens parsing inline template - carlossg h2. Don't replace original stacktrace when error happens parsing inline template * Author: Carlos Sanchez git...@carlossanchez.eu * Company: * Github ID: [carlossg|https://github.com/carlossg] * [Pull Request 2215 Discussion|https://github.com/puppetlabs/puppet/pull/2215] * [Pull Request 2215 File Diff|https://github.com/puppetlabs/puppet/pull/22... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1348) PR (2216): (PUP-1351) Load ext/packaging/packaging.rake instead of ext/packaging/tasks/** - skottler
Title: Message Title gepetto-bot created an issue Puppet / PUP-1348 PR (2216): (PUP-1351) Load ext/packaging/packaging.rake instead of ext/packaging/tasks/** - skottler Issue Type: Task Assignee: Unassigned Components: Community Created: 03/Jan/14 3:03 AM Priority: Normal Reporter: gepetto-bot (PUP-1351) Load ext/packaging/packaging.rake instead of ext/packaging/tasks/** Author: Sam Kottler s...@linux.com Company: Red Hat Github ID: skottler Pull Request 2216 Discussion Pull Request 2216 File Diff Pull Request Description (webhooks-id: 8f7ead149f3f1e2f96254268415d4604)
Jira (PUP-1348) PR (2216): (PUP-1351) Load ext/packaging/packaging.rake instead of ext/packaging/tasks/** - skottler
Title: Message Title gepetto-bot commented on an issue Re: PR (2216): (PUP-1351) Load ext/packaging/packaging.rake instead of ext/packaging/tasks/** - skottler Pull request (PUP-1351) Load ext/packaging/packaging.rake instead of ext/packaging/tasks/** has been closed. Add Comment Puppet / PUP-1348 PR (2216): (PUP-1351) Load ext/packaging/packaging.rake instead of ext/packaging/tasks/** - skottler h2. (PUP-1351) Load ext/packaging/packaging.rake instead of ext/packaging/tasks/** * Author: Sam Kottler s...@linux.com * Company: Red Hat * Github ID: [skottler|https://github.com/skottler] * [Pull Request 2216 Discussion|https://github.com/puppetlabs/puppet/pull/2216] * [Pull Request 2216 File Diff|https://github.com/puppetlabs/puppet/pull/2216/f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For
Jira (PUP-1351) Load ext/packaging/packaging.rake instead of ext/packaging/tasks/**
Title: Message Title Dominic Cleal updated an issue Puppet / PUP-1351 Load ext/packaging/packaging.rake instead of ext/packaging/tasks/** Change By: Dominic Cleal Fix Version/s: 2.7.25 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1348) PR (2216): (PUP-1351) Load ext/packaging/packaging.rake instead of ext/packaging/tasks/** - skottler
Title: Message Title gepetto-bot commented on an issue Re: PR (2216): (PUP-1351) Load ext/packaging/packaging.rake instead of ext/packaging/tasks/** - skottler domcleal commented: Thanks @skottler! Add Comment Puppet / PUP-1348 PR (2216): (PUP-1351) Load ext/packaging/packaging.rake instead of ext/packaging/tasks/** - skottler h2. (PUP-1351) Load ext/packaging/packaging.rake instead of ext/packaging/tasks/** * Author: Sam Kottler s...@linux.com * Company: Red Hat * Github ID: [skottler|https://github.com/skottler] * [Pull Request 2216 Discussion|https://github.com/puppetlabs/puppet/pull/2216] * [Pull Request 2216 File Diff|https://github.com/puppetlabs/puppet/pull/2216/f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1351) Load ext/packaging/packaging.rake instead of ext/packaging/tasks/**
Title: Message Title
Dominic Cleal commented on an issue
Re: Load ext/packaging/packaging.rake instead of ext/packaging/tasks/**
Merged in efc3d081b for 2.7.25.
Add Comment
Puppet / PUP-1351
Load ext/packaging/packaging.rake instead of ext/packaging/tasks/**
This currently gets printed each time rake gets executed, updating to just load the packaging.rake will prevent that. {noformat} DEPRECATED: The packaging repo tasks are now loaded by 'packaging.rake'. Please update your Rakefile or loading task to load 'ext/packaging/packaging.rake' instead of 'ext/packaging/tasks/*' (25-Jun-2013). {noformat}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1353) configurable nice value (explicitly on service and exec calls)
Title: Message Title redmine.exporter created an issue Puppet / PUP-1353 configurable nice value (explicitly on service and exec calls) Issue Type: New Feature Assignee: Unassigned Created: 03/Jan/14 3:25 AM Labels: redmine Priority: Normal Reporter: redmine.exporter We would like to be able to set the nice value on puppetd, but we don't want everything NICEd that is started by puppet. When searching for this i found this almost identical request from 2010 on http://markmail.org/message/2xscb6v6l7pi6zqn: The requestor, Trevor, said he was about to add this as a request here, but did not have his account data. It seems though he never did, as i could not find the request in here. So i will just copy and paste it here. quote: So, some of us would like to be able to set the nice value on puppetd. However, we don't want all of our services (and some of our execs) re-niced. Would it be feasible/practical to have the ability to set the nice value explicitly on Service and Exec calls? This is what we are also interested in.
Jira (PUP-1352) package ensure = purged is too noisy!
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1352
package ensure = purged is too noisy!
Issue Type:
Bug
Assignee:
Unassigned
Created:
03/Jan/14 3:24 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
pre $packages = [ one, two, three ] package { $packages: ensure = purged, }
/pre
is too noisy.
The logs are filled with: pre /Stage[main]/MODULE/Package[one]/ensure created. /Stage[main]/MODULE/Package[two]/ensure created. /Stage[main]/MODULE/Package[three]/ensure created. /pre on every run of puppet-agent.
Add Comment
Jira (PUP-1193) pip provider does not detect existance of system installed packages
Title: Message Title Mark Egan-Fuller commented on an issue Re: pip provider does not detect existance of system installed packages This issue is still a problem, seems to be the difference between freeze and list. $ pip freeze | grep -i distribute $ pip list | grep -i distribute distribute (0.7.3) $ pip install --upgrade distribute Requirement already up-to-date: distribute in /usr/local/lib/python2.7/dist-packages Requirement already up-to-date: setuptools=0.7 in /usr/local/lib/python2.7/dist-packages (from distribute) Cleaning up... Add Comment Puppet / PUP-1193 pip provider does not detect existance of system installed packages When, using the pip provider, I get events that the same package is installed, everytime puppet runs pre pip freeze | grep xenapi #returns nothing /pre pre pip install xenapi Requirement already satisfied (use --upgrade to upgrade): xenapi in /usr/local/lib/python2.6/dist-packages Cleaning up... /pre This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (MCO-144) mcollective-package-agent broken with Puppet 3.4
Title: Message Title
Pieter Loubser commented on an issue
Re: mcollective-package-agent broken with Puppet 3.4
It looks like the change in behaviour was introduced in https://github.com/puppetlabs/puppet/commit/732d4509ac52010727ac0331a5470833dc438c85. In the past our package agent was expecting a hash with fields {symbol = string}
instead of {symbol = Puppet::Util::Execution::ProcessOutput}
.
This causes a problem when MCollective tries to deserialise the reply from the package agent. It has no notion of Puppet::Util::Execution::ProcessOutput which causes Marshal.load to fail.
Add Comment
MCollective / MCO-144
mcollective-package-agent broken with Puppet 3.4
As per the thread on the list, the mcollective-package-agent fails when used with Puppet 3.4. The data structure that the provider methods return has changed slightly and we should update the agent to deal with this.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs
Jira (HI-125) Can't interpolate hash or array members with %{} tokens
Title: Message Title
redmine.exporter created an issue
Hiera / HI-125
Can't interpolate hash or array members with %{} tokens
Issue Type:
New Feature
Assignee:
Eric Sorenson
Created:
03/Jan/14 3:50 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
Although Hiera receives all of Puppet's variables, it can only interpolate strings/numbers/bools it can't get members of arrays or hashes. Trying (with `% {my_array[3]}
`) results in an endless loop. (This is probably related to #17094.)
For now, this probably isn't a big deal. If we ever move to making facts available in a hash, it'll become critical.
Add Comment
Jira (PDB-249) temp-usage and store-usage in config.ini throw exception java.lang.IllegalArgumentException
Title: Message Title Kenneth Barber commented on an issue Re: temp-usage and store-usage in config.ini throw exception java.lang.IllegalArgumentException Working branch: https://github.com/kbarber/puppetdb/tree/ticket/master/PDB-249_commands-config-exceptions Add Comment PuppetDB / PDB-249 temp-usage and store-usage in config.ini throw exception java.lang.IllegalArgumentException If we use temp-usage or store-usage in [command-processing] blocks in the config.ini file, we get exceptions as per this gist: https://gist.github.com/kbarber/8220568 Tests haven't picked this up either, so we probably need to remedy that also. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1178) Forced to kill and restart Puppet demon after update to 3.2.3
Title: Message Title Jason Burks commented on an issue Re: Forced to kill and restart Puppet demon after update to 3.2.3 I just stated seeing the behavior described after updating a node from 3.3.2 to 3.4.1 via the PL Yum repo. Ruby 1.9.3 is not installed on the affected node, so that does not appear to be the answer. I have a handful of other nodes running the same version of Puppet and Ruby (1.8.7), with the same kernel, that are so far unaffected. Details for the impacted node: [root@cl0526 ~]# ruby --version ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] [root@cl0526 ~]# puppet --version 3.4.1 [root@cl0526 ~]# facter kernelrelease 2.6.32-358.el6.x86_64 The catalog applied fine after the first update. However, that first update caused puppet.conf to change, and upon the re-load/re-parse, the failures started. A restart of the Puppet agent seems to have fixed the issue (at least for now). Jan 2 16:26:48 cl0526 puppet-agent[7695]: Finished catalog run in 4.95 seconds Jan 2 16:27:00 cl0526 puppet-agent[5842]: Config file /etc/puppet/puppet.conf changed; triggering re-parse of all config files. Jan 2 16:34:46 cl0526 puppet-agent[8169]: Could not autoload puppet/util/instrumentation/listeners/performance: Class Performance is already defined in Puppet::Util::Instrumentation Jan 2 16:34:46 cl0526 puppet-agent[8169]: Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/performance: Class Performance is already defined in Puppet::Util::Instrumentation Add Comment Puppet / PUP-1178 Forced to kill and restart Puppet demon after update to 3.2.3 I just updated to Puppet 3.2.3-1 using yum.puppetlabs.com as repo. It worked fine at the beginning but after a random time, each of my Fedora18 node became unworking. Here is the error I got in Puppet Dashboard 1.2.23 : pre err Failed to apply catalog: Could not autoload
Jira (MCO-97) Config class does not parse fixnum config parameters correctly
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-97 Config class does not parse fixnum config parameters correctly Change By: Pieter Loubser Assignee: PieterLoubser RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-184) Using 'ip addr' over ifconfig
Title: Message Title redmine.exporter created an issue Facter / FACT-184 Using 'ip addr' over ifconfig Issue Type: Bug Assignee: Eric Sorenson Created: 03/Jan/14 5:59 AM Labels: redmine Priority: Normal Reporter: redmine.exporter pre facter /usr/lib/ruby/site_ruby/1.8/facter/ipmess.rb:85: command not found: /sbin/ifconfig -a /usr/bin/facter:54: command not found: /sbin/ifconfig -a /usr/bin/facter:54: command not found: dnsdomainname /usr/bin/facter:54: command not found: domainname /usr/bin/facter:54: command not found: /sbin/ifconfig architecture = i386 domain = internal.HIDDEN facterversion = 1.3.8 fqdn = ruby-test.internal.HIDDEN hardwareisa = unknown hardwaremodel = i686 hostname = ruby-test id = root ipaddress = 10.200.201.73 /pre It would be nice if when ifconfig can't be found, it falls back to using 'ip addr' (or the other way around) - also, notice that domainname and dnsdomainname are not present on this system - however facter does appear to get them correct regardless.
Jira (PUP-1354) Something *very* strange is happening with file stats on the master.
Title: Message Title redmine.exporter created an issue Puppet / PUP-1354 Something *very* strange is happening with file stats on the master. Issue Type: Bug Assignee: Unassigned Created: 03/Jan/14 6:06 AM Labels: redmine Priority: Normal Reporter: redmine.exporter Puppet 3.3.0 + puppetdb + puppetdb query which is used right in the site.pp. It is engaging in extensive statting of files and taking a long time. From one run before I restarted: [pid 21236] stat(/opt/puppet3/etc/modules/puppetdbquery/lib/puppet/type/remote_query::handle_key.rb, 0x7f49f9dedab0) = -1 ENOENT (No such file or directory) [rlpowell@shell01 ~]$ grep stat../opt/puppet3/etc/modules/puppetdbquery/lib/puppet/type/remote_query::handle_key.rb /tmp/master.strace | wc -l 118580 That's partial; the strace was at 1.5GiB before I gave up. After a restart, it's noticeably better, but not great: [pid 28105] stat(/opt/puppet3/etc/modules/puppetdbquery/lib/puppet/type/users::handle_special_key.rb, 0x7f49de5e5b30) = -1 ENOENT (No such file or directory) [rlpowell@shell01 ~]$ grep /opt/puppet3/etc/modules/puppetdbquery/lib/puppet/type/users::handle_special_key.rb /tmp/master.strace | wc -l 64410 This is all straces of the puppet master. This all happens somewhere between these two lines of output on the client:
Jira (PDB-249) temp-usage and store-usage in config.ini throw exception java.lang.IllegalArgumentException
Title: Message Title Kenneth Barber commented on an issue Re: temp-usage and store-usage in config.ini throw exception java.lang.IllegalArgumentException This is ready to be reviewed: https://github.com/puppetlabs/puppetdb/pull/782 Add Comment PuppetDB / PDB-249 temp-usage and store-usage in config.ini throw exception java.lang.IllegalArgumentException If we use temp-usage or store-usage in [command-processing] blocks in the config.ini file, we get exceptions as per this gist: https://gist.github.com/kbarber/8220568 Tests haven't picked this up either, so we probably need to remedy that also. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-144) mcollective-package-agent broken with Puppet 3.4
Title: Message Title Justin Lambert commented on an issue Re: mcollective-package-agent broken with Puppet 3.4 I can confirm this fix works for me - thanks! Add Comment MCollective / MCO-144 mcollective-package-agent broken with Puppet 3.4 As per the thread on the list, the mcollective-package-agent fails when used with Puppet 3.4. The data structure that the provider methods return has changed slightly and we should update the agent to deal with this. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1298) manage_membership for unix groups provider
Title: Message Title Gabriel Filion commented on an issue Re: manage_membership for unix groups provider hmm so basically this means that the builtin type doesn't work correctly on linux, and maybe others. Add Comment Puppet / PUP-1298 manage_membership for unix groups provider I searched and didn't see this feature request so if is/was at some point forgive me. I'd like to be able to define the users that belong to a group in the group's resource. My compelling reason is that a specific unix group is used to determine ssh access via AllowGroups in sshd_config, and I'd like to make sure that at all times only specific users a... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-20) add unit tests for MCollective::Facts::Yaml_facts
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-20 add unit tests for MCollective::Facts::Yaml_facts Change By: Pieter Loubser Assignee: PieterLoubser RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1346) PR (2214): (PUP-724,#21922) Autoload compares only integer secs - jpartlow
Title: Message Title gepetto-bot commented on an issue Re: PR (2214): (PUP-724,#21922) Autoload compares only integer secs - jpartlow Pull request (PUP-724,#21922) Autoload compares only integer secs has been closed. Add Comment Puppet / PUP-1346 PR (2214): (PUP-724,#21922) Autoload compares only integer secs - jpartlow h2. (PUP-724,#21922) Autoload compares only integer secs * Author: Josh Partlow * Company: * Github ID: [jpartlow|https://github.com/jpartlow] * [Pull Request 2214 Discussion|https://github.com/puppetlabs/puppet/pull/2214] * [Pull Request 2214 File Diff|https://github.com/puppetlabs/puppet/pull/2214/files] h2. Pull Request Description Alt... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Joshua Cooper commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Merged in commit 917cc40 to be released in 3.5.0 Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-89) Release 1.6.0rc1
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-89 Release 1.6.0rc1 Change By: Melissa Stone Thistasktracksthe1.6.0release.Sub-tasksTODO. Formoreinformationonsubtasks,see:https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process?src=""> Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-253) Module: ubuntu 1004 tests are failing for the puppetdb module automated system tests
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-253 Module: ubuntu 1004 tests are failing for the puppetdb module automated system tests Change By: Kenneth Barber Summary: Module:ubuntu 1204 1004 testsarefailingforthepuppetdbmoduleautomatedsystemtests Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1300) Start 3.4.2 Final - Dec 31, 2013
Title: Message Title Andrew Parker assigned an issue to Unassigned Puppet / PUP-1300 Start 3.4.2 Final - Dec 31, 2013 Change By: Andrew Parker Assignee: AndrewParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1303) Is there a commit for every bug targeted at the release
Title: Message Title Andrew Parker assigned an issue to Unassigned Puppet / PUP-1303 Is there a commit for every bug targeted at the release Change By: Andrew Parker Assignee: AndrewParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1301) Are tests passing (spec, acceptance, all platforms)
Title: Message Title Andrew Parker assigned an issue to Unassigned Puppet / PUP-1301 Are tests passing (spec, acceptance, all platforms) Change By: Andrew Parker Assignee: AndrewParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1304) Is a new version created for the next version in the series?
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1304 Is a new version created for the next version in the series? Change By: Andrew Parker Summary: Isa redmineaffected new version createdforthe new next version intheseries? Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1302) Is there a bug targeting at the release for every commit
Title: Message Title Andrew Parker assigned an issue to Unassigned Puppet / PUP-1302 Is there a bug targeting at the release for every commit Change By: Andrew Parker Assignee: AndrewParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log Change By: Joshua Partlow Fix Version/s: 3.5.0 Fix Version/s: 3.4.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-264) Docs pushed
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-264 Docs pushed Change By: Kenneth Barber Assignee: KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1162) puppet resource error with no suitable provider: Could not run: undefined method `exists?' for nil:NilClass
Title: Message Title
Joshua Cooper commented on an issue
Re: puppet resource error with no suitable provider: Could not run: undefined method `exists?' for nil:NilClass
There used to be an issue on Centos5, where if you weren't running as root, the useradd, etc commands were not executable by group or other, so there wasn't a default user provider. Can you also run with `--trace` and paste the relevant stack trace
Add Comment
Puppet / PUP-1162
puppet resource error with no suitable provider: Could not run: undefined method `exists?' for nil:NilClass
Following [the resources documentation](http://docs.puppetlabs.com/learning/ral.html) I execute the following command as normal user and get: {code} igalic@tynix ~ % puppet resource user root Error: Could not run: undefined method `exists?' for nil:NilClass 1 igalic@tynix ~ % puppet resource user igalic Error: Could not run: undefined method `exists?...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-1355) PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow
Title: Message Title gepetto-bot created an issue Puppet / PUP-1355 PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow Issue Type: Task Assignee: Unassigned Components: Community Created: 03/Jan/14 10:07 AM Labels: github Priority: Normal Reporter: gepetto-bot Maint/master/revert 6857 test changes and match fedora Author: Josh Partlow Company: Github ID: jpartlow Pull Request 2217 Discussion Pull Request 2217 File Diff Pull Request Description
Jira (PUP-1349) PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow
Title: Message Title gepetto-bot created an issue Puppet / PUP-1349 PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow Issue Type: Task Assignee: Unassigned Components: Community Created: 03/Jan/14 10:07 AM Priority: Normal Reporter: gepetto-bot Maint/master/revert 6857 test changes and match fedora Author: Josh Partlow Company: Github ID: jpartlow Pull Request 2217 Discussion Pull Request 2217 File Diff Pull Request Description My previous patch to this test resulted in a regression of coverage on windows and solaris. This reverts and patches the fedora platform match instead. (webhooks-id: 7478d1c522ca05e815c9a760ccc26c80)
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Joshua Partlow commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log We discussed this for a while in hipchat, and consensus was to retarget for 3.4.2, which we hope to release Monday, and then merge to PE 3.2.x Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-672) Informational certificate extensions should be exposed inside the Puppet DSL
Title: Message Title Joshua Partlow commented on an issue Re: Informational certificate extensions should be exposed inside the Puppet DSL There's an acceptance failure I will look into shortly. Add Comment Puppet / PUP-672 Informational certificate extensions should be exposed inside the Puppet DSL Additional information may be encoded in certificate extensions, and when present should be available in the Puppet DSL. Certificate extensions in a specific subtree of an OID should be parsed out in some manner and exposed in some manner, in a specific namespace that indicates that the information is encoded in the certificate itself. The OID subtree ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1349) PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow
Title: Message Title gepetto-bot commented on an issue Re: PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1349 PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow h2. Maint/master/revert 6857 test changes and match fedora * Author: Josh Partlow * Company: * Github ID: [jpartlow|https://github.com/jpartlow] * [Pull Request 2217 Discussion|https://github.com/puppetlabs/puppet/pull/2217] * [Pull Request 2217 File Diff|https://github.com/puppetlabs/puppet/pull/2217/files] h2. Pull Request Description M... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1355) PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow
Title: Message Title gepetto-bot commented on an issue Re: PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1355 PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow h2. Maint/master/revert 6857 test changes and match fedora * Author: Josh Partlow * Company: * Github ID: [jpartlow|https://github.com/jpartlow] * [Pull Request 2217 Discussion|https://github.com/puppetlabs/puppet/pull/2217] * [Pull Request 2217 File Diff|https://github.com/puppetlabs/puppet/pull/2217/files] h2. Pull Request Description M... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1350) PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog
Title: Message Title gepetto-bot created an issue Puppet / PUP-1350 PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog Issue Type: Task Assignee: Unassigned Components: Community Created: 03/Jan/14 11:09 AM Priority: Normal Reporter: gepetto-bot (maint) Add a diagnostic check that lmhosts is running Author: Kylo Ginsberg Company: Github ID: kylog Pull Request 2218 Discussion Pull Request 2218 File Diff Pull Request Description (webhooks-id: 8f2a1657ae3e590ffadff22a28e56348)
Jira (PDB-264) Docs pushed
Title: Message Title Kenneth Barber commented on an issue Re: Docs pushed PR is here: https://github.com/puppetlabs/puppet-docs/pull/264 Nicholas Fagerlund Frederick Lifton ... this is in preparation for the upcoming PuppetDB 1.6.0rc1 release. If you have any questions/concerns let me know. Add Comment PuppetDB / PDB-264 Docs pushed This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1356) PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog
Title: Message Title gepetto-bot created an issue Puppet / PUP-1356 PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog Issue Type: Task Assignee: Unassigned Components: Community Created: 03/Jan/14 11:09 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Add a diagnostic check that lmhosts is running Author: Kylo Ginsberg Company: Github ID: kylog Pull Request 2218 Discussion Pull Request 2218 File Diff Pull Request Description
Jira (PUP-1356) PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog kylog commented: @Iristyle @joshcooper Here's a PR with a diagnostic check along the lines we discussed last night. I opted to put this in the uber-`before` rather than the more proximate `before` specific to the tests I saw failing yesterday because I though that would reduce the burden for someone adding tests in the future, where it might not be obvious which tests had this dependency. Add Comment Puppet / PUP-1356 PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog h2. (maint) Add a diagnostic check that lmhosts is running * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 2218 Discussion|https://github.com/puppetlabs/puppet/pull/2218] * [Pull Request 2218 File Diff|https://github.com/puppetlabs/puppet/pull/2218/files] h2. Pull Request Description ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet
Jira (PDB-268) Modify CI for the new 1.6.x branch
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-268 Modify CI for the new 1.6.x branch Issue Type: Sub-task Assignee: Kenneth Barber Created: 03/Jan/14 11:15 AM Priority: Normal Reporter: Kenneth Barber The PuppetDB build pipeline requires parent jobs to be created for the new 1.6.x branch: https://jenkins.puppetlabs.com/view/B_PuppetDB/ Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) --
Jira (PUP-1350) PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog kylog commented: @Iristyle @joshcooper Here's a PR with a diagnostic check along the lines we discussed last night. I opted to put this in the uber-`before` rather than the more proximate `before` specific to the tests I saw failing yesterday because I though that would reduce the burden for someone adding tests in the future, where it might not be obvious which tests had this dependency. Add Comment Puppet / PUP-1350 PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog h2. (maint) Add a diagnostic check that lmhosts is running * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 2218 Discussion|https://github.com/puppetlabs/puppet/pull/2218] * [Pull Request 2218 File Diff|https://github.com/puppetlabs/puppet/pull/2218/files] h2. Pull Request Description ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet
Jira (PUP-1357) Class names that match the node name are not evaluated
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1357
Class names that match the node name are not evaluated
Issue Type:
Bug
Assignee:
Unassigned
Created:
03/Jan/14 11:37 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
If I setup:
class subversion { warning(I am class subversion) }
and in my nodes.pp I have
node subversion { include subversion }
When i run puppet in verbose mode on subversion, I never see that warning.
Add Comment
Jira (PDB-269) Update dujor
Title: Message Title Melissa Stone created an issue PuppetDB / PDB-269 Update dujor Issue Type: Sub-task Assignee: Unassigned Created: 03/Jan/14 12:08 PM Priority: Normal Reporter: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1358) Push fixes to cover the PE 3.X series
Title: Message Title Michelle Johansen created an issue Puppet / PUP-1358 Push fixes to cover the PE 3.X series Issue Type: Sub-task Assignee: Joshua Cooper Components: Types and Providers Created: 03/Jan/14 12:09 PM Priority: Normal Reporter: Michelle Johansen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-1359) Pull fixes to cover the PE 2.8.X series
Title: Message Title Michelle Johansen created an issue Puppet / PUP-1359 Pull fixes to cover the PE 2.8.X series Issue Type: Sub-task Assignee: Matthaus Owens Components: Types and Providers Created: 03/Jan/14 12:10 PM Priority: Normal Reporter: Michelle Johansen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-1359) Pull fixes to cover the PE 2.8.X series
Title: Message Title Joshua Cooper commented on an issue Re: Pull fixes to cover the PE 2.8.X series Andrew Parker merged 9f16821 into 2.8.x and 4ef269d into 3.1.x. The fix to the specs when run on 2012 3b4e5cb do not need to be backported, since those tests don't exist prior to pe-puppet/3.2.x Add Comment Puppet / PUP-1359 Pull fixes to cover the PE 2.8.X series This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1360) more verbosity in thing-not-found debug logs
Title: Message Title redmine.exporter created an issue Puppet / PUP-1360 more verbosity in thing-not-found debug logs Issue Type: Bug Assignee: Unassigned Created: 03/Jan/14 12:38 PM Labels: redmine Priority: Normal Reporter: redmine.exporter Doing something like this to reproduce a file system permissions issue I had: chmod 000 /etc/puppet/environments/production/modules/puppet And then doing: puppet master --environment production --config /etc/puppet/puppetmaster.conf --debug --verbose --no-daemonize Leads to a message like this in the debug output when trying to do an agent run : Error: Could not find class puppet::agent for a1.cw on node a1.cw Error: Could not find class puppet::agent for a1.cw on node a1.cw Error: Could not find class puppet::agent for a1.cw on node a1.cw But from the strace output, we see that actually it was looking for a specific thing, and couldn't access that thing: lstat(/etc/puppet/environments/production/modules/puppet/manifests/agent.pp, 0x7fff1616b580) = -1 EACCES (Permission denied) Could we please have the reason (File not found, Permission denied, etc.) and the path that the master was looking for also in the debug output following the Could not find class line? For example: Error: Class puppet::agent should be in /etc/puppet/environments/production/modules/puppet/manifests/agent.pp but stat said Permission denied.
Jira (PDB-270) PR (783): Update documentation headers for 1.6.x - kbarber
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-270 PR (783): Update documentation headers for 1.6.x - kbarber Issue Type: Task Assignee: Unassigned Created: 03/Jan/14 12:40 PM Labels: github Priority: Normal Reporter: gepetto-bot Update documentation headers for 1.6.x Author: Ken Barber k...@bob.sh Company: Puppetlabs Inc. Github ID: kbarber Pull Request 783 Discussion Pull Request 783 File Diff Pull Request Description Signed-off-by: Ken Barber k...@bob.sh (webhooks-id: 856c48a406cea45793d5ebec511c6f77)
Jira (PDB-251) PR (110): Support rspec-puppet v1.0.0 - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-251 PR (110): Support rspec-puppet v1.0.0 - kbarber Change By: Kenneth Barber Sprint: 20140101to20140108 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-270) PR (783): Update documentation headers for 1.6.x - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-270 PR (783): Update documentation headers for 1.6.x - kbarber Change By: Kenneth Barber Sprint: 20140101to20140108 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-244) PR (780): Refactor to trapperkeeper - cprice404
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-244 PR (780): Refactor to trapperkeeper - cprice404 Change By: Kenneth Barber Sprint: 20140101to20140108 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-224) PR (773): FOR REVIEW: Port PuppetDB to use trapperkeeper - nwolfe
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-224 PR (773): FOR REVIEW: Port PuppetDB to use trapperkeeper - nwolfe Change By: Kenneth Barber Sprint: 20140101to20140108 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-243) PR (779): Remove illegal keys from fact payload - grimradical
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-243 PR (779): Remove illegal keys from fact payload - grimradical Change By: Kenneth Barber Sprint: 20140101to20140108 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-222) PR (772): FOR REVIEW: Port PuppetDB to use trapperkeeper - cprice404
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-222 PR (772): FOR REVIEW: Port PuppetDB to use trapperkeeper - cprice404 Change By: Kenneth Barber Sprint: 20140101to20140108 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-248) PR (781): Update changelog for 1.6.0 - grimradical
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-248 PR (781): Update changelog for 1.6.0 - grimradical Change By: Kenneth Barber Sprint: 20140101to20140108 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1358) Push fixes to cover the PE 3.X series
Title: Message Title Joshua Cooper commented on an issue Re: Push fixes to cover the PE 3.X series Andrew Parker merged 9f16821 into 2.8.x and 4ef269d into 3.1.x. The fix to the specs when run on 2012 3b4e5cb do not need to be backported, since those tests don't exist prior to pe-puppet/3.2.x Add Comment Puppet / PUP-1358 Push fixes to cover the PE 3.X series This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-226) PR (775): Remove unused `test:package` rake task - cprice404
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-226 PR (775): Remove unused `test:package` rake task - cprice404 Change By: Kenneth Barber Sprint: 20140101to20140108 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-225) PR (774): (maint) Add fedora 20 to mock list - melissaanne
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-225 PR (774): (maint) Add fedora 20 to mock list - melissaanne Change By: Kenneth Barber Sprint: 20140101to20140108 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-227) PR (107): Fix puppetlabs#106 and one other bug when disable_ssl = true - ebarrere
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-227 PR (107): Fix puppetlabs#106 and one other bug when disable_ssl = true - ebarrere Change By: Kenneth Barber Sprint: 20140101to20140108 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-270) PR (783): Update documentation headers for 1.6.x - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (783): Update documentation headers for 1.6.x - kbarber Pull request Update documentation headers for 1.6.x has been closed. Add Comment PuppetDB / PDB-270 PR (783): Update documentation headers for 1.6.x - kbarber h2. Update documentation headers for 1.6.x * Author: Ken Barber k...@bob.sh * Company: Puppetlabs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 783 Discussion|https://github.com/puppetlabs/puppetdb/pull/783] * [Pull Request 783 File Diff|https://github.com/puppetlabs/puppetdb/pull/783/files] h2. Pull Request Description --... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-270) PR (783): Update documentation headers for 1.6.x - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (783): Update documentation headers for 1.6.x - kbarber puppetlabs-jenkins commented: :red_circle: Test failed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/119/ Add Comment PuppetDB / PDB-270 PR (783): Update documentation headers for 1.6.x - kbarber h2. Update documentation headers for 1.6.x * Author: Ken Barber k...@bob.sh * Company: Puppetlabs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 783 Discussion|https://github.com/puppetlabs/puppetdb/pull/783] * [Pull Request 783 File Diff|https://github.com/puppetlabs/puppetdb/pull/783/files] h2. Pull Request Description --... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-1300) Start 3.4.2 Final - Jan 6, 2014
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1300 Start 3.4.2 Final - Jan 6, 2014 Change By: Kylo Ginsberg Summary: Start3.4.2Final- Dec31 Jan6 , 2013 2014 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-185) No EC2 facts shown on newly-built Amazon Linux host
Title: Message Title Justin Honold created an issue Facter / FACT-185 No EC2 facts shown on newly-built Amazon Linux host Issue Type: Bug Affects Versions: 1.7.4 Assignee: Eric Sorenson Components: Community Created: 03/Jan/14 1:16 PM Environment: Amazon Linux AMI release 2013.09 ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux] Priority: Normal Reporter: Justin Honold `facter|grep ec2` yields only the 'domain' and 'fqdn' facts for me, not a gaggle of them including stuff like 'ec2_profile'. The same versions on another host are working fine. Any tips on troubleshooting? An strace isn't showing anything promising to me, although it confirms that it's firing up the ec2.rb library.
Jira (PUP-1361) Puppet `rake gen_manpages` manpages.task broken
Title: Message Title Matthaus Owens created an issue Puppet / PUP-1361 Puppet `rake gen_manpages` manpages.task broken Issue Type: Bug Affects Versions: 3.2.1 Assignee: Unassigned Created: 03/Jan/14 1:24 PM Priority: Normal Reporter: Matthaus Owens I saw the following on puppet 3.4.1-21-g98e9219, but seems to be broken for most/all of the 3 series so far. matthaus@wyclef /Users/matthaus/src/puppet [stable] rake gen_manpages --trace ** Invoke gen_manpages (first_time) ** Execute gen_manpages rake aborted! --name=: already defined in puppet /Users/matthaus/src/puppet/lib/puppet/interface/option.rb:36:in `block in initialize' /Users/matthaus/src/puppet/lib/puppet/interface/option.rb:18:in `each' /Users/matthaus/src/puppet/lib/puppet/interface/option.rb:18:in `initialize' /Users/matthaus/src/puppet/lib/puppet/interface/option_builder.rb:17:in `new' /Users/matthaus/src/puppet/lib/puppet/interface/option_builder.rb:17:in `initialize' /Users/matthaus/src/puppet/lib/puppet/interface/option_builder.rb:12:in `new' /Users/matthaus/src/puppet/lib/puppet/interface/option_builder.rb:12:in `build' /Users/matthaus/src/puppet/lib/puppet/interface/action_builder.rb:93:in `option' /Users/matthaus/.puppet/var/lib/puppet/face/dashboard.rb:102:in `block (2 levels) in top (required)' /Users/matthaus/src/puppet/lib/puppet/interface/action_builder.rb:146:in `instance_eval' /Users/matthaus/src/puppet/lib/puppet/interface/action_builder.rb:146:in `initialize' /Users/matthaus/src/puppet/lib/puppet/interface/action_builder.rb:17:in `new' /Users/matthaus/src/puppet/lib/puppet/interface/action_builder.rb:17:in `build'
Jira (PDB-271) Report docs still say experimental
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-271 Report docs still say experimental Issue Type: Bug Affects Versions: 1.6.0, 1.5.X Assignee: Unassigned Created: 03/Jan/14 1:38 PM Fix Versions: 1.6.0, 1.5.X Priority: Normal Reporter: Ryan Senior Probably should get updated: http://docs.puppetlabs.com/puppetdb/1.5/api/wire_format/report_format.html http://docs.puppetlabs.com/puppetdb/1.5/api/commands.html http://docs.puppetlabs.com/puppetdb/1.6/api/wire_format/report_format.html http://docs.puppetlabs.com/puppetdb/1.6/api/commands.html Add Comment
Jira (PDB-271) Update 1.5.x and 1.6.x docs
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-271 Update 1.5.x and 1.6.x docs Change By: Ryan Senior Summary: Update1.5.xand1.6.x docsReport docs stillsayexperimental Probably JDK1.6 should getupdated sayit'sdeprecated : https://docs.puppetlabs.com/puppetdb/latest/#nix-server-with-jdk-16Reportdocsstillsayexperimental: http://docs.puppetlabs.com/puppetdb/1.5/api/wire_format/report_format.htmlhttp://docs.puppetlabs.com/puppetdb/1.5/api/commands.htmlhttp://docs.puppetlabs.com/puppetdb/1.6/api/wire_format/report_format.htmlhttp://docs.puppetlabs.com/puppetdb/1.6/api/commands.html Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-271) Update 1.5.x and 1.6.x docsReport docs still say experimental
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-271 Update 1.5.x and 1.6.x docsReport docs still say experimental Change By: Ryan Senior Summary: Report Update1.5.xand1.6.xdocsReport docsstillsayexperimental Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-186) Build windows specific gem
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Facter / FACT-186 Build windows specific gem Change By: Joshua Cooper Assignee: EricSorenson JoshuaCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-186) Build windows specific gem
Title: Message Title Joshua Cooper created an issue Facter / FACT-186 Build windows specific gem Issue Type: Bug Assignee: Eric Sorenson Created: 03/Jan/14 1:49 PM Priority: Normal Reporter: Joshua Cooper See PUP-1282 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (FACT-187) Build windows specific gem
Title: Message Title Joshua Cooper created an issue Facter / FACT-187 Build windows specific gem Issue Type: Bug Assignee: Eric Sorenson Created: 03/Jan/14 1:49 PM Labels: windows Priority: Normal Reporter: Joshua Cooper See PUP-1282 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-187) Build windows specific gem
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Facter / FACT-187 Build windows specific gem Change By: Joshua Cooper Assignee: EricSorenson JoshuaCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-126) Build windows specific gem
Title: Message Title Joshua Cooper updated an issue Hiera / HI-126 Build windows specific gem Change By: Joshua Cooper Issue Type: Bug Task Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-126) Build windows specific gem
Title: Message Title Joshua Cooper moved an issue Hiera / HI-126 Build windows specific gem Change By: Joshua Cooper Key: FACT HI - 187 126 Project: Facter Hiera Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1356) PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1356 PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog h2. (maint) Add a diagnostic check that lmhosts is running * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 2218 Discussion|https://github.com/puppetlabs/puppet/pull/2218] * [Pull Request 2218 File Diff|https://github.com/puppetlabs/puppet/pull/2218/files] h2. Pull Request Description ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1350) PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1350 PR (2218): (maint) Add a diagnostic check that lmhosts is running - kylog h2. (maint) Add a diagnostic check that lmhosts is running * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 2218 Discussion|https://github.com/puppetlabs/puppet/pull/2218] * [Pull Request 2218 File Diff|https://github.com/puppetlabs/puppet/pull/2218/files] h2. Pull Request Description ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1362) Rubyize yumhelper.py to remove dependency on python
Title: Message Title redmine.exporter created an issue Puppet / PUP-1362 Rubyize yumhelper.py to remove dependency on python Issue Type: Bug Assignee: Unassigned Created: 03/Jan/14 2:31 PM Labels: redmine Priority: Normal Reporter: redmine.exporter There are several bugs (bug 11380 being one that triggered this patch) that highlight the fact that the version of python used as the default on a system running puppet can break yumhelper.py. This refactor removes yumhelper.py and moves the functionality into the Yum provider in puppet. Add Comment
Jira (PUP-1363) yum helper fails when using a custom yum plugin with custom variables
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1363
yum helper fails when using a custom yum plugin with custom variables
Issue Type:
Bug
Assignee:
Unassigned
Created:
03/Jan/14 2:31 PM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
We have a custom yum plugin that provides a custom variable for use in our .repo files and the Puppet yum helper does not function correctly with custom variables.
First, we ensure our yum plugin is installed on all machines:
package { 'SNC-2-1-1-1:.:.:snc-yum': name = 'snc-yum', ensure = installed }
Then, we set up our repositories.
sncyumrepo { 'SNC-2-1-3-1:.:.:yumrepo-base': name = 'base', alias = 'base', descr = 'CentOS Base Repository', baseurl = 'http://repo/centos/$sncversion/os/$basearch/', enabled = 1, gpgcheck = 1, gpgkey = 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever', require = File['yumparentdir'] }
Notice the baseurl contains our custom variable: $sncversion. This is the variable that is provided by the yum plugin.
This will write our the base.repo file WITH that variable in the final output. The variable is the replaced by yum just like the built-in yum variable $releasever.
Then, we attempt to use the base.repo and it fails!
package { 'SNC-2-1-1-1:.:.:any-package': name = 'any-package', ensure = installed }
Every
Jira (PUP-1364) Yum package arch and version ensuring failing
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1364
Yum package arch and version ensuring failing
Issue Type:
Bug
Assignee:
Unassigned
Created:
03/Jan/14 2:46 PM
Labels:
redmine customer
Priority:
Normal
Reporter:
redmine.exporter
After lots of trial and error I found a bug in our current Puppet version
Having a package line like so:
pre package { firefox.x86_64: ensure = 3.0.12-1.el5.centos, require = Package[xulrunner.x86_64] }
/pre
Would fail with debug output: pre *_ debug: //Node[om012274.drd.int]/workstation/workstation_centos53/mozillasuite53/Package[firefox.x86_64]: Changing ensure debug: //Node[om012274.drd.int]/workstation/workstation_centos53/mozillasuite53/Package[firefox.x86_64]: 1 change(s) debug: Package[firefox.x86_64](provider=yum): Ensuring = 3.0.12-1.el5.centos debug: Puppet::Type::Package::ProviderYum: Executing '/usr/bin/yum -d 0 -e 0 -y install firefox.x86_64-3.0.12-1.el5.centos' debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -q firefox.x86_64 --nosignature --nodigest --qf % {NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH} ' err: //Node[om012274.drd.int]/workstation/workstation_centos53/mozillasuite53/Package[firefox.x86_64]/ensure: change from absent to 3.0.12-1.el5.centos failed: Could not update: Could not find package firefox.x86_64 at /etc/puppet/manifests/CentOS.pp:149_* /pre It didn't matter if I listed ver-release or just ver, same sort of error; it appends the version-[release] to the package name and arch. Which obviously fails as yum packages must be referred to like so: pre name
Jira (PUP-1365) Yum provider doesn't understand globs
Title: Message Title redmine.exporter created an issue Puppet / PUP-1365 Yum provider doesn't understand globs Issue Type: Bug Assignee: Unassigned Created: 03/Jan/14 2:47 PM Labels: redmine Priority: Normal Reporter: redmine.exporter Yum understands globs in regards to version numbers. On the command line, if I say `yum install puppet-2.6*`, I will get the latest version of 2.6 available, even if a 2.7 version exists in my repositories. If I use this in a manifest, such as `ensure = '2.6*'`, puppet attempts to install literally `puppet-2.6*`, as if asterisk was a version number, producing an error err: /Stage[main]/Puppet/Package[puppet]/ensure: change from 2.6.14-1.el5 to 2.6* failed: Could not update: Failed to update to version 2.6*, got version 2.6.14-1.el5 instead Yum exits with `$? = 0` with this format. Add Comment
Jira (PUP-1366) yum provider doesn't respect items provided by a package, only the package name
Title: Message Title Jason Antman updated an issue Puppet / PUP-1366 yum provider doesn't respect items provided by a package, only the package name Change By: Jason Antman Component/s: TypesandProviders Labels: redmine yum Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1366) yum provider doesn't respect items provided by a package, only the package name
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1366
yum provider doesn't respect items provided by a package, only the package name
Issue Type:
Bug
Assignee:
Unassigned
Created:
03/Jan/14 2:48 PM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
A simple use case:
In EL5 and earlier, the curl development headers were included in a package called curl-devel. In EL6 and later that package was renamed to libcurl-devel. However, the libcurl-devel package still provides curl-devel.
When using something like
package { curl-devel: ensure = installed }
puppet looks for this package every time.
[root@centos6-32 ~]# puppet resource package libcurl-devel warning: Package kernel found in both yum and yum; skipping the yum version warning: Package gpg-pubkey found in both yum and yum; skipping the yum version package { 'libcurl-devel': ensure = '7.19.7-26.el6_1.2', }
[root@centos6-32 ~]# puppet resource package curl-devel warning: Package kernel found in both yum and yum; skipping the yum version warning: Package gpg-pubkey found in both yum and yum; skipping the yum version package { 'curl-devel': ensure = 'absent', }
[root@centos6-32 ~]# rpm -q --whatprovides curl-devel libcurl-devel-7.19.7-26.el6_1.2.i686 [root@centos6-32 ~]#
The yum provider should basically use the way yum work to make this happen. If I do yum install curl-devel on EL6, it pulls in libcurl-devel.
Jira (PUP-736) Encoding mis-matches cause package prefetching to fail
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Encoding mis-matches cause package prefetching to fail
An easy re-production environment for this issue is Ubuntu 12.04. The kbd project, which is installed by default, contains smart quotes in the package description.
Add Comment
Puppet / PUP-736
Encoding mis-matches cause package prefetching to fail
One of our RPM packages has some UTF-8 characters in its description, leading to an exception (Error: Could not prefetch package provider 'yum': invalid byte sequence in US-ASCII) in rpm.rb, causing no packages to be upgraded as the yumhelper.py invocation code raises that error. Priority=High because it breaks file { ensure = latest; }.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-736) Encoding mis-matches cause package prefetching to fail
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-736 Encoding mis-matches cause package prefetching to fail Change By: Kylo Ginsberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-736) Encoding mis-matches cause package prefetching to fail
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-736 Encoding mis-matches cause package prefetching to fail Change By: Kylo Ginsberg Sprint: Week2014-1-8to2014-1-15 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1367) behavior change within 2.6 makes it impossible to override class parameters of included parametrized classes
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1367
behavior change within 2.6 makes it impossible to override class parameters of included parametrized classes
Issue Type:
Bug
Assignee:
Unassigned
Created:
03/Jan/14 3:09 PM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
In 2.6.1 the following recipe:
pre class a( $b_c = { 'b' = 'foo' }
) { notice $a::b_c if $a::b_c { notice $a::b_c['b'] }
}
class b { class {'a': b_c = false }
}
class b::c inherits b { Class['a']{ b_c = { 'b' = 'bleh' }
} }
class b::d { include ::b::c }
include b::d /pre
produces the following output:
pre $ puppet foo.pp notice: Scope(Class[A]): bbleh notice: Scope(Class[A]): bleh /pre
Which is what I expected. However with 2.6.3 it produces the following output:
pre
puppet foo.pp notice: Scope(Class[A]): false /pre
Imho likely the changes for #4778 and #5074 are responsible for that behavior
Jira (PUP-736) Encoding mis-matches cause package prefetching to fail
Title: Message Title
Kylo Ginsberg commented on an issue
Re: Encoding mis-matches cause package prefetching to fail
After some discussion on HipChat we decided to provide a short-term quick-fix by yanking the functionality that added description fetching for rpm/apt. This functionality was introduced but never used by any other projects, so should be sfe to remove.
This is a quick-fix and doesn't address the broader issue of checking for encoding incompatibility in these providers. That work is still being scoped.
Add Comment
Puppet / PUP-736
Encoding mis-matches cause package prefetching to fail
One of our RPM packages has some UTF-8 characters in its description, leading to an exception (Error: Could not prefetch package provider 'yum': invalid byte sequence in US-ASCII) in rpm.rb, causing no packages to be upgraded as the yumhelper.py invocation code raises that error. Priority=High because it breaks file { ensure = latest; }.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this
Jira (PUP-1351) PR (2219): (PUP-1068) Add basic auth to HTTP Connection and HTTP Reports - zaphod42
Title: Message Title gepetto-bot created an issue Puppet / PUP-1351 PR (2219): (PUP-1068) Add basic auth to HTTP Connection and HTTP Reports - zaphod42 Issue Type: Task Assignee: Unassigned Components: Community Created: 03/Jan/14 3:29 PM Priority: Normal Reporter: gepetto-bot (PUP-1068) Add basic auth to HTTP Connection and HTTP Reports Author: Andrew Parker Company: Puppet Labs Github ID: zaphod42 Pull Request 2219 Discussion Pull Request 2219 File Diff Pull Request Description This adds logic in Puppet::Reports::Http to properly handle HTTP basic auth using the form http://username:password@host/path In order to make this work more clearly, this also adds actual parameters to the connection class's #get, #post, etc methods. The defaults are
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Joshua Partlow commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Cherry-picked to puppet/stable in 98e9219 Merged to pe-puppet/3.2.x in 5af6e12 Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1355) PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow
Title: Message Title gepetto-bot commented on an issue Re: PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow Pull request Maint/master/revert 6857 test changes and match fedora has been closed. Add Comment Puppet / PUP-1355 PR (2217): Maint/master/revert 6857 test changes and match fedora - jpartlow h2. Maint/master/revert 6857 test changes and match fedora * Author: Josh Partlow * Company: * Github ID: [jpartlow|https://github.com/jpartlow] * [Pull Request 2217 Discussion|https://github.com/puppetlabs/puppet/pull/2217] * [Pull Request 2217 File Diff|https://github.com/puppetlabs/puppet/pull/2217/files] h2. Pull Request Description M... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
