Jira (PUP-1283) Update win32-service gem
Title: Message Title Josh Cooper commented on an issue Re: Update win32-service gem Note commit https://github.com/puppetlabs/puppet/commit/22e25ec5b213 references this bug, but the commit is actually targeted for PUP-1760. Add Comment Puppet / PUP-1283 Update win32-service gem The win32-service gem was patched upstream to resolve #16080. The fix was merged upstream https://github.com/djberg96/win32-service/pull/8. At a minimum we need to update the gem and remove the patch https://github.com/puppetlabs/puppet-win32-ruby/blob/1.9.3/16080-handle-missing-description.patch. We also need to make sure we can update to the `ffi` b... 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/d/optout.
Jira (PUP-2729) reevaluate config_version whenever an agent checks in.
Title: Message Title
Felix Frank updated an issue
Puppet / PUP-2729
reevaluate config_version whenever an agent checks in.
Change By:
Felix Frank
Whenpuppetmanifestsareedited,puppetmasterdusuallynotices,andcomputesanewconfigurationversionbyinvokingtheconfig_versionscriptorbyusingthedefault(derivedfromthecurrenttime).However,whenfilesareedited,theconfigurationversionremainsunchanged. pre {code} #.../modules/mymodule/manifests/init.ppclassmymodule{file{/dir/filename:ensure=file,source=puppet:///mymodule/filename,}} /pre {code} IfIedit {{ .../modules/mymodule/manifests/init.pp }} ,thentheconfigurationversiongetsupdatednexttimeaclientconnects.Sofarsogood.However,ifIedit {{ .../modules/mymodule/files/filename }} ,theconfigurationversionremainsunchanged.Amessageontheclientsay {noformat} info:Applyingconfigurationversion'oldversionnumberhere'. {noformat} Frommypointofview,IwouldlikeittobeseenasasaconfigurationchangewhenIeditafilethatgetsdeployedfromafilessubdirectoryinamodule.Iusesubversionrevisionnumbersintheconfig_version,andIwanttobeabletotellpeoplecheckthattheconfigurationversionisatleastN,tobesurethatyouhavethelatestchangestofilename.
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/d/optout.
Jira (PUP-2826) http report plugin uses wrong cert store for report upload over https
Title: Message Title Andreas Zuber created an issue Puppet / PUP-2826 http report plugin uses wrong cert store for report upload over https Issue Type: Bug Affects Versions: 3.2.4 Assignee: Andy Parker Components: Server Created: 24/Jun/14 1:35 AM Environment: Everywhere Labels: puppet reports https Priority: Normal Reporter: Andreas Zuber It seams that the http.rb plugin uses the same classes to get a HTTP connection puppet usually uses to talk to the master, configured with puppets own cert store. There may be cases where the https endpoint uses a certificate signed by the puppet CA. However in the case of the Dashboard or similar endpoints it uses a web interface which is usually protected by a cert signed by an official or a company internal CA which is also recognized by the
Jira (PUP-2827) Incorrect return code for --noop
Title: Message Title
Patrick McAndrew created an issue
Puppet / PUP-2827
Incorrect return code for --noop
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Unassigned
Created:
24/Jun/14 5:32 AM
Environment:
Ubuntu 14.04
Priority:
Normal
Reporter:
Patrick McAndrew
t.pp – node default { }
running ```puppet apply --noop t.pp```
Running under 3.6.2 returns 1 with the following errors:
Error: Failed to apply catalog: Operation not permitted - /var/lib/jenkins/.puppet/var/state/state.yaml20140624-3338-egqchx Error: Could not save last run local report: Operation not permitted - /var/lib/jenkins/.puppet/var/state/last_run_summary.yaml20140624-3338-187sv5a Error: Could not send report: Operation not permitted - /var/lib/jenkins/.puppet/var/state/last_run_report.yaml20140624-3338-djuxtb
Running under 3.2.4 returns 0 with following output: Notice: Finished catalog run in 1.93 seconds
If this change was/is desired behaviour (not to us, but perhaps that decision was made), would be great to have an additional flag to turn off that behaviour for automated testing.
Jira (FACT-602) puppetlabs_spec_helper does not provide code coverage for any currently supported Ruby versions
Title: Message Title Cassiano Leal created an issue Facter / FACT-602 puppetlabs_spec_helper does not provide code coverage for any currently supported Ruby versions Issue Type: Bug Assignee: Eric Sorenson Components: QA Created: 24/Jun/14 6:08 AM Labels: rspec coverage Priority: Normal Reporter: Cassiano Leal The puppetlabs_spec_helper gem creates a coverage Rake task. Unfortunately it's currently broken as it uses rcov and that only works on a deprecated Ruby version. Replacing it with simplecov would probably be the way to go forward. Add Comment
Jira (FACT-602) puppetlabs_spec_helper does not provide code coverage for any currently supported Ruby versions
Title: Message Title Cassiano Leal commented on an issue Re: puppetlabs_spec_helper does not provide code coverage for any currently supported Ruby versions I'm terribly sorry I just realised I've created this on the wrong project. Could you please direct me to the correct project for this issue? :-/ Add Comment Facter / FACT-602 puppetlabs_spec_helper does not provide code coverage for any currently supported Ruby versions The puppetlabs_spec_helper gem creates a coverage Rake task. Unfortunately it's currently broken as it uses rcov and that only works on a deprecated Ruby version. Replacing it with simplecov would probably be the way to go forward. 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-2389) Create ruby 2.0 branch for x64 in puppet-win32-ruby
Title: Message Title Ethan Brown commented on an issue Re: Create ruby 2.0 branch for x64 in puppet-win32-ruby Matthaus Owens Moses Mendoza How do we get these changes into the local mirror at github.delivery.puppetlabs.net/puppetlabs-puppet-win32-ruby.git? In diagnosing todays fails... I discovered that the mirror was causing acceptance jobs to fail because it was last updated 4 months ago. I assumed that the jobs would specify a commit-ish to use a specific puppet-win32-ruby version, but they do not. Log at https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/job/Puppet-Acceptance-Windows-master-vcloud-and-github/355/label=acc-coord,platform=win2003r2/consoleText Clone git://github.delivery.puppetlabs.net/puppetlabs-puppet-win32-ruby.git if needed ud5b76jk06e7we2 (agent-r2-i386) 01:09:24$ test -d /opt/puppet-git-repos || mkdir -p /opt/puppet-git-repos ud5b76jk06e7we2 (agent-r2-i386) executed in 0.23 seconds ud5b76jk06e7we2 (agent-r2-i386) 01:09:24$ test -d /opt/puppet-git-repos/puppet-win32-ruby || git clone git://github.delivery.puppetlabs.net/puppetlabs-puppet-win32-ruby.git /opt/puppet-git-repos/puppet-win32-ruby Cloning into '/opt/puppet-git-repos/puppet-win32-ruby'... ud5b76jk06e7we2 (agent-r2-i386) executed in 34.36 seconds Update puppet-win32-ruby and check out revision ud5b76jk06e7we2 (agent-r2-i386) 01:09:59$ cd /opt/puppet-git-repos/puppet-win32-ruby git remote rm origin git remote add origin git://github.delivery.puppetlabs.net/puppetlabs-puppet-win32-ruby.git git fetch origin git clean -fdx git checkout -f From git://github.delivery.puppetlabs.net/puppetlabs-puppet-win32-ruby [new branch] 1.8.7 - origin/1.8.7 [new branch] 1.9.3 - origin/1.9.3 [new branch] master - origin/master [new branch] update_openssl - origin/update_openssl ud5b76jk06e7we2 (agent-r2-i386) executed in 6.41 seconds And the gems that came along for the ride
Jira (PUP-2750) expand profiler signature to support hierarchical profiling data
Title: Message Title Christopher Price commented on an issue Re: expand profiler signature to support hierarchical profiling data Fix was merged here: https://github.com/puppetlabs/puppet/commit/ab3735ae68084f2c6fb86919a5f84239b6b9d2fd Add Comment Puppet / PUP-2750 expand profiler signature to support hierarchical profiling data The current profiling system only accepts a String as the argument to the call to `profile`. This is useful, but limits the amount of interesting aggregation that a specific profiler implementation can achieve. If we were to expand the signature of the `profile` method to accept a metric id, composed of basically a list of nested keys, then profiler... 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/d/optout.
Jira (PUP-2828) Support pinning puppet-win32-ruby version for Puppet
Title: Message Title Ethan Brown created an issue Puppet / PUP-2828 Support pinning puppet-win32-ruby version for Puppet Issue Type: Task Assignee: Ethan Brown Created: 24/Jun/14 7:42 AM Fix Versions: 3.7.0 Priority: Normal Reporter: Ethan Brown Presently Windows acceptance tests simply clone the https://github.com/puppetlabs/puppet-win32-ruby from the local internal mirror without specifying a revision. As we start to build Ruby 2 x64 on Windows, we're going to need to pin different jobs at different Ruby architecture / patch / gemsets for the sake of acceptance. This is a stopgap solution until we can test MSI packages during acceptance, which will already contain bundled Ruby versions (and will have a source of truth from the RE pipeline) Add Comment
Jira (PUP-2828) Support pinning puppet-win32-ruby version for Puppet
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2828 Support pinning puppet-win32-ruby version for Puppet Change By: Ethan Brown Sprint: Week2014-6-18to2014-6-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/d/optout.
Jira (FACT-599) Facter assumes sysctl is located at '/sbin/'
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Facter / FACT-599 Facter assumes sysctl is located at '/sbin/' Change By: Ethan Brown Assignee: EthanBrown 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/d/optout.
Jira (FACT-601) Facter produces mangled output with plaintext output and structured data
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Facter / FACT-601 Facter produces mangled output with plaintext output and structured data Change By: Ethan Brown Assignee: EthanBrown 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/d/optout.
Jira (FACT-575) Is the code ready for release?
Title: Message Title Adrien Thebo commented on an issue Re: Is the code ready for release? Reopening this because we need to restart the build. Add Comment Facter / FACT-575 Is the code ready for release? All tests (spec, acceptance) should be passing on all platforms for both stable master. * If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. * If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through sp... 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/d/optout.
Jira (FACT-578) Update version number in source
Title: Message Title
Adrien Thebo commented on an issue
Re: Update version number in source
Reopening this because we need to restart the release.
Add Comment
Facter / FACT-578
Update version number in source
Bump VERSION in lib/{#project}/version.rb to correct version. * Commit the updated version file. * e.g) commit -m (packaging) Update FACTERVERSION to 1.7.3-rc1. * If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). * Once this is done, hand the SHA to be built to RelEng to be tag...
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/d/optout.
Jira (FACT-576) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Adrien Thebo commented on an issue Re: Is there a JIRA ticket targeted at the release for every commit? Reopening this because we need to restart the release. Add Comment Facter / FACT-576 Is there a JIRA ticket targeted at the release for every commit? Ensure all tickets referenced in the commit log have a bug targeted at the release * git log old tag..new tag * look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release * Also, make sure the code itself is sane, that you understand why the change was made, etc. et... 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/d/optout.
Jira (FACT-577) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Adrien Thebo commented on an issue Re: Is there a commit for every JIRA ticket targeted at the release? Reopening this because we need to restart the release. Add Comment Facter / FACT-577 Is there a commit for every JIRA ticket targeted at the release? Ensure all tickets targeted at the release have a corresponding commit * git log old tag..new tag * This time, look through tickets targeted at this release in JIRA, and compare it to the commit log, looking for the corresponding numbers * [ticketmatch.rb script|https://gist.github.com/hlindberg/9520023] is a ruby script that helps with Is ther... 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/d/optout.
Jira (FACT-580) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Adrien Thebo commented on an issue Re: Is the Jira tidy-up done for this release and prepared for the next one? Reopening this because we need to restart the release. Add Comment Facter / FACT-580 Is the Jira tidy-up done for this release and prepared for the next one? This happens on Jira - we need to clean up the current release and prepare for the next release. * Mark the version that's going out as Released in the Project Admin - Versions panel. * Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7... 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/d/optout.
Jira (FACT-579) Merge master into stable
Title: Message Title
Adrien Thebo commented on an issue
Re: Merge master into stable
Reopening this because we need to restart the release.
Add Comment
Facter / FACT-579
Merge master into stable
For some releases, the code base will need to be merged down to stable. *NOTE:* This is usually only during a x.y.0-rc1 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: {noformat} git fetch up...
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/d/optout.
Jira (PUP-2389) Create ruby 2.0 branch for x64 in puppet-win32-ruby
Title: Message Title Moses Mendoza commented on an issue Re: Create ruby 2.0 branch for x64 in puppet-win32-ruby Hi Ethan Brown, Matthaus Owens is currently out on leave, and Melissa Stone will be helping out with the ruby 2.0 work as soon as the compiled software tooling wraps up. As for how to get the changes into the internal git mirror, I'm afraid I don't know - I'm surprised to hear that it's not kept up to date automatically? I think our infrastructure and tooling team manages the mirror. Scott Schneider do you know how we would get the internal repo of puppet-win32-ruby updated (and kept up to date)? Add Comment Puppet / PUP-2389 Create ruby 2.0 branch for x64 in puppet-win32-ruby We need to vendor x64 versions of ruby 2.0, and install the appropriate sets of gems into both branches. Ruby 2.1 is not yet released on Windows. The work here includes: # create 2.0.0-x64 branch # vendor ruby 2.0.0-p545 (x64) from rubyinstaller.org OR newer if they release a patched version # upgrade/install gems for x64 versions 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
Jira (FACT-601) Facter produces mangled output with plaintext output and structured data
Title: Message Title
Ethan Brown commented on an issue
Re: Facter produces mangled output with plaintext output and structured data
In latest commit on OSX Mavericks 10.9 using sample structured fact
Facter.add(:interfaces_array) do
setcode do
interfaces = Facter.value(:interfaces)
# the 'interfaces' fact returns a single comma-delimited string, e.g., lo0,eth0,eth1
interfaces_array = interfaces.split(',')
interfaces_array
end
end
Facter.add(:interfaces_hash) do
setcode do
interfaces_array = Facter.value(:interfaces_array)
interfaces_hash = {}
interfaces_array.each do |interface|
ipaddress = Facter.value(ipaddress_#{interface})
if ipaddress
interfaces_hash[interface] = ipaddress
end
end
interfaces_hash
end
end
Prior to merge:
interfaces_array = lo0gif0stf0en0en3en4bridge0p2p0vmnet1vmnet2vmnet8
interfaces_hash = lo0127.0.0.1vmnet1192.168.121.1vmnet2192.168.42.1vmnet8172.16.253.1en0192.168.0.102
After merge commit:
interfaces_array = [lo0, gif0, stf0, en0, en3, en4, bridge0, p2p0, vmnet1, vmnet2, vmnet8]
interfaces_hash = {vmnet1=192.168.121.1, vmnet2=192.168.42.1, vmnet8=172.16.253.1, lo0=127.0.0.1, en0=192.168.0.102}
Looks good to me!
Add Comment
Facter / FACT-601
Facter produces mangled output with plaintext output and structured data
Jira (PUP-2750) expand profiler signature to support hierarchical profiling data
Title: Message Title Andy Parker assigned an issue to Christopher Price Puppet / PUP-2750 expand profiler signature to support hierarchical profiling data Change By: Andy Parker Assignee: ChristopherPrice 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/d/optout.
Jira (PUP-2750) expand profiler signature to support hierarchical profiling data
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-2750 expand profiler signature to support hierarchical profiling data Change By: Andy Parker Assignee: ChristopherPrice HenrikLindberg 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/d/optout.
Jira (PUP-2828) Support pinning puppet-win32-ruby version for Puppet
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2828 Support pinning puppet-win32-ruby version for Puppet Change By: Rob Reynolds Component/s: Client 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/d/optout.
Jira (PUP-2828) Support pinning puppet-win32-ruby version for Puppet
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2828 Support pinning puppet-win32-ruby version for Puppet Change By: Rob Reynolds Labels: windows 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/d/optout.
Jira (PUP-2750) expand profiler signature to support hierarchical profiling data
Title: Message Title Henrik Lindberg commented on an issue Re: expand profiler signature to support hierarchical profiling data A delay of 0.01 was added to make the system report some time. Add Comment Puppet / PUP-2750 expand profiler signature to support hierarchical profiling data The current profiling system only accepts a String as the argument to the call to `profile`. This is useful, but limits the amount of interesting aggregation that a specific profiler implementation can achieve. If we were to expand the signature of the `profile` method to accept a metric id, composed of basically a list of nested keys, then profiler... 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/d/optout.
Jira (PDB-719) PR (995): (RE-1497) Remove quantal from build_defaults - clantant
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-719 PR (995): (RE-1497) Remove quantal from build_defaults - clantant Issue Type: Task Assignee: Unassigned Created: 24/Jun/14 9:40 AM Labels: github Priority: Normal Reporter: gepetto-bot (RE-1497) Remove quantal from build_defaults Author: Eric Timmerman eet1...@gmail.com Company: Github ID: clantant Pull Request 995 Discussion Pull Request 995 File Diff Pull Request Description This commit removes quantal from all build defaults because it is end of life. It removes the defaults from the build_defaults yaml. (webhooks-id: 27ab2afdc6b497cf8235a211e05ac7f4)
Jira (PDB-719) PR (995): (RE-1497) Remove quantal from build_defaults - clantant
Title: Message Title gepetto-bot commented on an issue Re: PR (995): (RE-1497) Remove quantal from build_defaults - clantant pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-719 PR (995): (RE-1497) Remove quantal from build_defaults - clantant h2. (RE-1497) Remove quantal from build_defaults * Author: Eric Timmerman eet1...@gmail.com * Company: * Github ID: [clantant|https://github.com/clantant] * [Pull Request 995 Discussion|https://github.com/puppetlabs/puppetdb/pull/995] * [Pull Request 995 File Diff|https://github.com/puppetlabs/puppetdb/pull/995/files] h2. Pull Request Descriptio... 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/d/optout.
Jira (PDB-719) PR (995): (RE-1497) Remove quantal from build_defaults - clantant
Title: Message Title gepetto-bot commented on an issue Re: PR (995): (RE-1497) Remove quantal from build_defaults - clantant pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-719 PR (995): (RE-1497) Remove quantal from build_defaults - clantant h2. (RE-1497) Remove quantal from build_defaults * Author: Eric Timmerman eet1...@gmail.com * Company: * Github ID: [clantant|https://github.com/clantant] * [Pull Request 995 Discussion|https://github.com/puppetlabs/puppetdb/pull/995] * [Pull Request 995 File Diff|https://github.com/puppetlabs/puppetdb/pull/995/files] h2. Pull Request Descriptio... 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/d/optout.
Jira (PDB-240) anonymize uses read-string
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-240 anonymize uses read-string Change By: Wyatt Alt Assignee: WyattAlt 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/d/optout.
Jira (PDB-240) anonymize uses read-string
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-240 anonymize uses read-string Change By: Wyatt Alt Sprint: 20140618to20140702 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/d/optout.
Jira (FACT-603) Allow to configure acceptance using github mirror
Title: Message Title Rob Reynolds created an issue Facter / FACT-603 Allow to configure acceptance using github mirror Issue Type: Improvement Assignee: Eric Sorenson Created: 24/Jun/14 10:04 AM Priority: Normal Reporter: Rob Reynolds In the same way that we do puppet. 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
Jira (FACT-603) Allow to configure acceptance using github mirror
Title: Message Title Rob Reynolds updated an issue Facter / FACT-603 Allow to configure acceptance using github mirror Change By: Rob Reynolds Inthesamewaythatwedopuppet. ThisshouldbedoneafterFacter2.1hasbeenreleasedinstable...sometimemeaningperhapsafewweeksafteritisreleased. 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/d/optout.
Jira (FACT-603) Allow to configure acceptance using github mirror
Title: Message Title Rob Reynolds commented on an issue Re: Allow to configure acceptance using github mirror Adrien Thebo FYI - thoughts Add Comment Facter / FACT-603 Allow to configure acceptance using github mirror In the same way that we do puppet. This should be done after Facter 2.1 has been released in stable... sometime meaning perhaps a few weeks after it is released. 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/d/optout.
Jira (FACT-603) Allow to configure acceptance using github mirror
Title: Message Title Rob Reynolds updated an issue Facter / FACT-603 Allow to configure acceptance using github mirror Change By: Rob Reynolds Fix Version/s: 2.1.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/d/optout.
Jira (PUP-2828) Support pinning puppet-win32-ruby version for Puppet
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-2828 Support pinning puppet-win32-ruby version for Puppet Change By: Ethan Brown Assignee: EthanBrown 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/d/optout.
Jira (PUP-2828) Support pinning puppet-win32-ruby version for Puppet
Title: Message Title Ethan Brown commented on an issue Re: Support pinning puppet-win32-ruby version for Puppet Upon further discussion, this PR will be modified to instead create a yaml file which can be used both by packaging and acceptance jobs place the appropriate git commit references to puppet-win32-ruby in the repo itself, rather than specifying in transient Jenkins jobs use an environment variable to choose which architecture the job is using and update jenkins jobs to specify this architecture variable Add Comment Puppet / PUP-2828 Support pinning puppet-win32-ruby version for Puppet Presently Windows acceptance tests simply clone the https://github.com/puppetlabs/puppet-win32-ruby from the local internal mirror without specifying a revision. As we start to build Ruby 2 x64 on Windows, we're going to need to pin different jobs at different Ruby architecture / patch / gemsets for the sake of acceptance. This is a stopgap solution... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2389) Create ruby 2.0 branch for x64 in puppet-win32-ruby
Title: Message Title Scott Schneider commented on an issue Re: Create ruby 2.0 branch for x64 in puppet-win32-ruby Moses Mendoza, Ethan Brown: puppetlabs-puppet-win32-ruby mirror is up to date on the gitmirror now. I renamed the directory and re-ran Puppet on the mirror and it re-checked out the repository. Please ping me again if you push to this repo and the changes are not reflected on the mirror within ~5 minutes. Add Comment Puppet / PUP-2389 Create ruby 2.0 branch for x64 in puppet-win32-ruby We need to vendor x64 versions of ruby 2.0, and install the appropriate sets of gems into both branches. Ruby 2.1 is not yet released on Windows. The work here includes: # create 2.0.0-x64 branch # vendor ruby 2.0.0-p545 (x64) from rubyinstaller.org OR newer if they release a patched version # upgrade/install gems for x64 versions 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
Jira (PDB-719) PR (995): (RE-1497) Remove quantal from build_defaults - clantant
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-719 PR (995): (RE-1497) Remove quantal from build_defaults - clantant Change By: Kenneth Barber Sprint: 20140618to20140702 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/d/optout.
Jira (PDB-719) PR (995): (RE-1497) Remove quantal from build_defaults - clantant
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-719 PR (995): (RE-1497) Remove quantal from build_defaults - clantant Change By: Kenneth Barber Story Points: 0 Fix Version/s: 2.1.0 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/d/optout.
Jira (PDB-719) PR (995): (RE-1497) Remove quantal from build_defaults - clantant
Title: Message Title gepetto-bot commented on an issue Re: PR (995): (RE-1497) Remove quantal from build_defaults - clantant Pull request (RE-1497) Remove quantal from build_defaults has been closed. Add Comment PuppetDB / PDB-719 PR (995): (RE-1497) Remove quantal from build_defaults - clantant h2. (RE-1497) Remove quantal from build_defaults * Author: Eric Timmerman eet1...@gmail.com * Company: * Github ID: [clantant|https://github.com/clantant] * [Pull Request 995 Discussion|https://github.com/puppetlabs/puppetdb/pull/995] * [Pull Request 995 File Diff|https://github.com/puppetlabs/puppetdb/pull/995/files] h2. Pull Request Descriptio... 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/d/optout.
Jira (FACT-603) Allow to configure acceptance using github mirror
Title: Message Title Adrien Thebo commented on an issue Re: Allow to configure acceptance using github mirror Rob Reynolds If we do this then we really need to extract a common repository for our acceptance tests, this isn't possible without copying code from puppet/acceptance so if we're going to be doing this we should take the time to refactor our acceptance test structure. Add Comment Facter / FACT-603 Allow to configure acceptance using github mirror In the same way that we do puppet. This should be done after Facter 2.1 has been released in stable... sometime meaning perhaps a few weeks after it is released. 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/d/optout.
Jira (PUP-2079) puppet module generate can't copy template files without parsing/renaming them
Title: Message Title Aaron Armstrong commented on an issue Re: puppet module generate can't copy template files without parsing/renaming them Ryan Coleman - can you prioritize this issue WRT the PE 3.4 release? Add Comment Puppet / PUP-2079 puppet module generate can't copy template files without parsing/renaming them When creating a new module with puppet module generate, any files in the skeleton dir named *.erb are parsed as Ruby erb templates and renamed, removing the file extension. This is a pain if you want to include template files in your skeleton directory. 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/d/optout.
Jira (PUP-2079) puppet module generate can't copy template files without parsing/renaming them
Title: Message Title Pieter van de Bruggen commented on an issue Re: puppet module generate can't copy template files without parsing/renaming them Since I've so far failed up update the ticket, there is a PR for this: https://github.com/puppetlabs/puppet/pull/2759 Add Comment Puppet / PUP-2079 puppet module generate can't copy template files without parsing/renaming them When creating a new module with puppet module generate, any files in the skeleton dir named *.erb are parsed as Ruby erb templates and renamed, removing the file extension. This is a pain if you want to include template files in your skeleton directory. 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/d/optout.
Jira (PUP-1548) Facter deliver wrong architecture to puppet
Title: Message Title
Stefan Schulte commented on an issue
Re: Facter deliver wrong architecture to puppet
what facter version are you running on your agent (facter --version)?
Add Comment
Puppet / PUP-1548
Facter deliver wrong architecture to puppet
I got this params.pp {noformat} case $::operatingsystem{ 'Debian', 'Ubuntu': { $package_name = SnareLinux-3.0.0-2_$::architecture.deb $provider = 'dpkg' $install_name = 'snarelinux' } {noformat} On Ubuntu Client puppet says: {noformat} root@PC3214ub:~# puppet agent -t info: Retrieving plugin ...
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/d/optout.
Jira (PUP-1548) Facter deliver wrong architecture to puppet
Title: Message Title
Stefan Schulte updated an issue
Puppet / PUP-1548
Facter deliver wrong architecture to puppet
Change By:
Stefan Schulte
Igotthisparams.pp {noformat} case$::operatingsystem{'Debian','Ubuntu':{$package_name=SnareLinux-3.0.0-2_$::architecture.deb$provider='dpkg'$install_name='snarelinux'} {noformat} OnUbuntuClientpuppetsays: {noformat} root@PC3214ub:~#puppetagent-tinfo:Retrievingplugininfo:Loadingfactsin/var/lib/puppet/lib/facter/root_home.rbinfo:Loadingfactsin/var/lib/puppet/lib/facter/puppet_vardir.rbinfo:Loadingfactsin/var/lib/puppet/lib/facter/vmwaretools_version.rbinfo:Loadingfactsin/var/lib/puppet/lib/facter/pper_installed.rbinfo:Loadingfactsin/var/lib/puppet/lib/facter/pe_version.rbinfo:Loadingfactsin/var/lib/puppet/lib/facter/os_maj_version.rbinfo:Loadingfactsin/var/lib/puppet/lib/facter/environment.rbinfo:Loadingfactsin/var/lib/puppet/lib/facter/facter_dot_d.rbinfo:Cachingcatalogforpc3214ubinfo:Applyingconfigurationversion'1391100647'err:/Stage[main]/Snare/File[/usr/local/src/SnareLinux-3.0.0-2_x86_64.deb]:Couldnotevaluate:Couldnotretrieveinformationfromenvironmentproductionsource(s)puppet:///modules/snare/SnareLinux-3.0.0-2_x86_64.debat/etc/puppet/modules/snare/manifests/init.pp:17notice:/Stage[main]/Snare/Package[installsnare]:DependencyFile[/usr/local/src/SnareLinux-3.0.0-2_x86_64.deb]hasfailures:truewarning:/Stage[main]/Snare/Package[installsnare]:Skippingbecauseoffaileddependenciesnotice:/Stage[main]/Snare/File[/etc/audit/snare.conf]:DependencyFile[/usr/local/src/SnareLinux-3.0.0-2_x86_64.deb]hasfailures:truewarning:/Stage[main]/Snare/File[/etc/audit/snare.conf]:Skippingbecauseoffaileddependenciesnotice:/Stage[main]/Snare/File[/etc/snare.conf]:DependencyFile[/usr/local/src/SnareLinux-3.0.0-2_x86_64.deb]hasfailures:truewarning:/Stage[main]/Snare/File[/etc/snare.conf]:Skippingbecauseoffaileddependenciesnotice:Finishedcatalogrunin11.03seconds {noformat} FacteronUbuntuClientsays: {noformat} root@PC3214ub:~#facterarchitectureamd64 {noformat} Thearchitectureis {{ amd64 }} butpuppetagentislookingfor {{ x86_64 }} .Thefileforamd64ispresent: {noformat} ll/etc/puppet/modules/snare/files/insgesamt283K-rw-rw-r--+1beckerbbeckerb42117.Okt12:55snare.conf-rw-rw-r--+1beckerbbeckerb59K17.Okt15:18SnareLinux-2.1.0-1.x86_64.rpm-rw-rw-r--+1beckerbbeckerb54K17.Okt13:41SnareLinux-3.0.0-1.i386.rpm-rw-rw-r--+1beckerbbeckerb56K17.Okt12:16SnareLinux-3.0.0-1.x86_64.rpm-rw-rw-r--+1beckerbbeckerb52K17.Okt12:15SnareLinux-3.0.0-2_amd64.deb-rw-rw-r--+1beckerbbeckerb50K17.Okt14:57SnareLinux-3.0.0-2_i386.deb {noformat} Myclientversionis: {noformat} root@PC3214ub:~#puppet--version2.7.11 {noformat} I'mnotsuretobecorrecthere,butIguessthisisabug..
Add Comment
Jira (PUP-2828) Support pinning puppet-win32-ruby version for Puppet
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-2828 Support pinning puppet-win32-ruby version for Puppet Change By: Josh Cooper Assignee: JoshCooper 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/d/optout.
Jira (PUP-2777) Support Bundler workflow on x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2777 Support Bundler workflow on x64 Change By: Josh Cooper Sprint: Week2014-6- 18 25 to2014- 6 7 - 25 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/d/optout.
Jira (PUP-514) Add optional type to parameters
Title: Message Title
Kurt Wall commented on an issue
Re: Add optional type to parameters
NAB because $name is a keyword in some contexts. Same with $title.
Add Comment
Puppet / PUP-514
Add optional type to parameters
It is of great value to be able to optionally type the parameters of defines and classes (as well as types). This is quite easy to implement as there now is a type system. The default type is Optional[Variant[Object,Type]] i.e. anything To optionally type a parameter simply enter the type before the parameter: {code} define foo(String $x, Integ...
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/d/optout.
Jira (PUP-2806) puppet module generate ignores ERB files beginning with a dot
Title: Message Title
Ryan Coleman commented on an issue
Re: puppet module generate ignores ERB files beginning with a dot
Thanks for clarifying Trey Dockendorf. This is being discussed in PUP-2079 with this PR: https://github.com/puppetlabs/puppet/pull/2759
I'm going to close this as a duplicate but link it so that others have more context. Thanks for the report!
Add Comment
Puppet / PUP-2806
puppet module generate ignores ERB files beginning with a dot
When using 'puppet module generate' with a custom skeleton directory, any files prefixed with a dot (for example, .fixtures.yml.erb) are ignored by the 'populate_erb_templates' method. Example: After running 'puppet module generate treydock-munge' using a custom skeleton directory. {code} $ ls -la treydock-munge/ total 112 drwxr-xr-x 18 tr...
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
Jira (FACT-570) Remove windows-pr as a Windows gem dependency
Title: Message Title Josh Cooper commented on an issue Re: Remove windows-pr as a Windows gem dependency The change to puppet-win32-ruby was reverted from the 1.9.3 branch, because we don't want to mix the FFI work with older releases, e.g. FOSS 3.6 and PE 3.3. For example, if we have to issue a securitypatch, we don't want to accidentally pull in the FFI work. A new 1.9.3-x86 branch was created containing the updated windows gems. Newer releases, e.g. FOSS 3.7 and PE 3.4, will pull from there moving forward. Add Comment Facter / FACT-570 Remove windows-pr as a Windows gem dependency Facter uses the windows-pr gem, and its win32-api dependency, when determining if facter is running as root or not. We need to eliminate usages of this gem now that everything is ffi'ed. The code that needs to be replaced is already in puppet, and just needs to be copied over. 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-2829) Puppet should not accept name or title for class names
Title: Message Title Kurt Wall updated an issue Puppet / PUP-2829 Puppet should not accept name or title for class names Change By: Kurt Wall Component/s: Server Fix Version/s: 3.x 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/d/optout.
Jira (PUP-2829) Puppet should not accept name or title for class names
Title: Message Title Kurt Wall created an issue Puppet / PUP-2829 Puppet should not accept name or title for class names Issue Type: Bug Assignee: Unassigned Created: 24/Jun/14 11:56 AM Priority: Normal Reporter: Kurt Wall The parser should reject class names (and other identifiers) which use name or title. These have special meanings in certain contexts but not others, resulting in odd failures. Failure occurs in because attempts to re-assign the value of name (or title) when it is used as the name of a default parameter and a class is instantiated using the default value. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2831) Puppet does not work with RGen 0.7.0
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2831 Puppet does not work with RGen 0.7.0 Issue Type: Bug Assignee: Andy Parker Components: DSL Created: 24/Jun/14 12:05 PM Fix Versions: 3.7.0 Priority: Major Reporter: Henrik Lindberg As discovered in PUP-2755 , strange things happen when using RGen 0.7.0 with puppet. Add Comment
Jira (PUP-2830) Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
Title: Message Title Branan Purvine-Riley created an issue Puppet / PUP-2830 Version of win32-security expected by puppet master branch is not in puppet-win32-ruby Issue Type: Bug Assignee: Unassigned Created: 24/Jun/14 12:05 PM Priority: Normal Reporter: Branan Purvine-Riley Puppet master branch has been updated to expect version 0.2.5 of the win32-security gem. However, the version of the gem included in our puppet-win32-security repo is still 0.1.4. This is causing test failures, since there are some incompatibilities between those versions. Either puppet needs to be made to expect 0.1.4 again, or the win32-ruby repo needs to be updated to 0.2.5. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2830) Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
Title: Message Title
Josh Cooper commented on an issue
Re: Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
Branan Purvine-Riley where are you seeing this issue? PE acceptance? We are in the process of rejiggering the puppet-win32-ruby repo to ensure we maintain compatibility with old versions, while allowing x64 work to continue in a different branch
Add Comment
Puppet / PUP-2830
Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
Puppet master branch has been updated to expect version 0.2.5 of the win32-security gem. However, the version of the gem included in our {{puppet-win32-security}} repo is still 0.1.4. This is causing test failures, since there are some incompatibilities between those versions. Either puppet needs to be made to expect 0.1.4 again, or the win32-ruby repo...
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,
Jira (PUP-2831) Puppet does not work with RGen 0.7.0
Title: Message Title
Henrik Lindberg commented on an issue
Re: Puppet does not work with RGen 0.7.0
This snippet reproduces the problem:
{a=1, b=2, c=3}.each |$item| { notice $item }
It should output notice of 1,2,3, now it notices [a, 1], [b, 2], [c, 3] this happens because the function dispatcher does not recognize a Hash as a Hash and instead chooses a more general path.
Add Comment
Puppet / PUP-2831
Puppet does not work with RGen 0.7.0
As discovered in PUP-2755, strange things happen when using RGen 0.7.0 with puppet.
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
Jira (PUP-2830) Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
Title: Message Title
Branan Purvine-Riley commented on an issue
Re: Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
Josh Cooper The symptom of this was reported as a potential QE issue in the flakiness ticket. The affect is visible in https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Windows-Per-Commit-master/403/
Inspecting the code deployed to the system in that test run shows version 0.1.4 of the gem, but a version of puppet that rescues a SystemError instead of a Win32::Security::SID::Error.
Add Comment
Puppet / PUP-2830
Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
Puppet master branch has been updated to expect version 0.2.5 of the win32-security gem. However, the version of the gem included in our {{puppet-win32-security}} repo is still 0.1.4. This is causing test failures, since there are some incompatibilities between those versions. Either puppet needs to be made to expect 0.1.4 again, or the win32-ruby repo...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are
Jira (PUP-2389) Create ruby 2.0 branch for x64 in puppet-win32-ruby
Title: Message Title Rob Reynolds commented on an issue Re: Create ruby 2.0 branch for x64 in puppet-win32-ruby Note this for the 1.9.3 branch - https://tickets.puppetlabs.com/browse/FACT-570?focusedCommentId=77640page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-77640 Add Comment Puppet / PUP-2389 Create ruby 2.0 branch for x64 in puppet-win32-ruby We need to vendor x64 versions of ruby 2.0, and install the appropriate sets of gems into both branches. Ruby 2.1 is not yet released on Windows. The work here includes: # create 2.0.0-x64 branch # vendor ruby 2.0.0-p545 (x64) from rubyinstaller.org OR newer if they release a patched version # upgrade/install gems for x64 versions 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-2830) Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
Title: Message Title
Rob Reynolds commented on an issue
Re: Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
https://tickets.puppetlabs.com/browse/FACT-570?focusedCommentId=77640page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-77640 is the comment where we are backing out the changes in 1.9.3 and creating a 1.9.3-x86 branch for the new gem changes.
Add Comment
Puppet / PUP-2830
Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
Puppet master branch has been updated to expect version 0.2.5 of the win32-security gem. However, the version of the gem included in our {{puppet-win32-security}} repo is still 0.1.4. This is causing test failures, since there are some incompatibilities between those versions. Either puppet needs to be made to expect 0.1.4 again, or the win32-ruby repo...
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-2830) Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
Title: Message Title
Rob Reynolds commented on an issue
Re: Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
Branan Purvine-Riley Yes, that's where we realized the mirror wasn't being updated, which has now been resolved.
Add Comment
Puppet / PUP-2830
Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
Puppet master branch has been updated to expect version 0.2.5 of the win32-security gem. However, the version of the gem included in our {{puppet-win32-security}} repo is still 0.1.4. This is causing test failures, since there are some incompatibilities between those versions. Either puppet needs to be made to expect 0.1.4 again, or the win32-ruby repo...
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-2830) Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
Title: Message Title
Rob Reynolds commented on an issue
Re: Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
Rereading the description, the issue is due to my last comment - our github mirror was not updating correctly. That has been resolved, so this can be closed I believe.
Add Comment
Puppet / PUP-2830
Version of win32-security expected by puppet master branch is not in puppet-win32-ruby
Puppet master branch has been updated to expect version 0.2.5 of the win32-security gem. However, the version of the gem included in our {{puppet-win32-security}} repo is still 0.1.4. This is causing test failures, since there are some incompatibilities between those versions. Either puppet needs to be made to expect 0.1.4 again, or the win32-ruby repo...
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-2787) Rename Object to Any
Title: Message Title Rob Reynolds commented on an issue Re: Rename Object to Any FR the naming change. Looks good from my perspective. Prefer the name Any definitely over Object. Add Comment Puppet / PUP-2787 Rename Object to Any Object has, over time, become the top type of the puppet language's type system. However, Object has too many connections to the word class that we fear that using it will cause some confusion in what is already a confusing system. Calling the top type Any would avoid all of this, be a shorter word, and actually be more naturally indicative as to what... 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/d/optout.
Jira (PUP-2787) Rename Object to Any
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-2787 Rename Object to Any Change By: Rob Reynolds Assignee: RobReynolds 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/d/optout.
Jira (PUP-2557) Deprecate and remove node inheritance
Title: Message Title Rob Reynolds commented on an issue Re: Deprecate and remove node inheritance Shouldn't FR also verify that --parser future emits an error? Add Comment Puppet / PUP-2557 Deprecate and remove node inheritance Node inheritance causes a large number of complications and ambiguities that make understanding puppet code difficult. There is very little reason to use it since much more effective reuse can be achieved using classes and defined types. On the next 3 series puppet that is using the current parser: the system must issue a deprecation warning when it en... 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/d/optout.
Jira (PUP-2557) Deprecate and remove node inheritance
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-2557 Deprecate and remove node inheritance Change By: Rob Reynolds Assignee: RobReynolds 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/d/optout.
Jira (PUP-514) Add optional type to parameters
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-514 Add optional type to parameters Change By: Kurt Wall Assignee: KurtWall 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/d/optout.
Jira (FACT-570) Remove windows-pr as a Windows gem dependency
Title: Message Title Josh Cooper commented on an issue Re: Remove windows-pr as a Windows gem dependency Updated facter acceptance setup step to install puppet-win32-ruby from 1.9.3-x86 branch which contains the correct FFI gemsets, see https://github.com/puppetlabs/facter/commit/a5e552de509bf7a9696fadee4b1a4317ee15404c Add Comment Facter / FACT-570 Remove windows-pr as a Windows gem dependency Facter uses the windows-pr gem, and its win32-api dependency, when determining if facter is running as root or not. We need to eliminate usages of this gem now that everything is ffi'ed. The code that needs to be replaced is already in puppet, and just needs to be copied over. 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/d/optout.
Jira (FACT-575) Is the code ready for release?
Title: Message Title Adrien Thebo commented on an issue Re: Is the code ready for release? All spec and acceptance tests are passing and all Facter issues are resolved. Add Comment Facter / FACT-575 Is the code ready for release? All tests (spec, acceptance) should be passing on all platforms for both stable master. * If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. * If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through sp... 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/d/optout.
Jira (FACT-577) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Adrien Thebo commented on an issue Re: Is there a commit for every JIRA ticket targeted at the release? All issues targeted at 2.1.0 have a related commit. Add Comment Facter / FACT-577 Is there a commit for every JIRA ticket targeted at the release? Ensure all tickets targeted at the release have a corresponding commit * git log old tag..new tag * This time, look through tickets targeted at this release in JIRA, and compare it to the commit log, looking for the corresponding numbers * [ticketmatch.rb script|https://gist.github.com/hlindberg/9520023] is a ruby script that helps with Is ther... 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/d/optout.
Jira (FACT-576) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Adrien Thebo commented on an issue Re: Is there a JIRA ticket targeted at the release for every commit? All JIRA issues really present and extra accounted for. Add Comment Facter / FACT-576 Is there a JIRA ticket targeted at the release for every commit? Ensure all tickets referenced in the commit log have a bug targeted at the release * git log old tag..new tag * look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release * Also, make sure the code itself is sane, that you understand why the change was made, etc. et... 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/d/optout.
Jira (FACT-579) Merge master into stable
Title: Message Title
Adrien Thebo commented on an issue
Re: Merge master into stable
Merged facter-2 into stable in 82f8734 and merged up to facter-2 and master.
Add Comment
Facter / FACT-579
Merge master into stable
For some releases, the code base will need to be merged down to stable. *NOTE:* This is usually only during a x.y.0-rc1 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: {noformat} git fetch up...
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/d/optout.
Jira (FACT-580) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Adrien Thebo commented on an issue Re: Is the Jira tidy-up done for this release and prepared for the next one? Jira is already tidied from last time around. Add Comment Facter / FACT-580 Is the Jira tidy-up done for this release and prepared for the next one? This happens on Jira - we need to clean up the current release and prepare for the next release. * Mark the version that's going out as Released in the Project Admin - Versions panel. * Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7... 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/d/optout.
Jira (PDB-720) Port already in use with cli/services.clj test
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-720 Port already in use with cli/services.clj test Issue Type: Bug Affects Versions: 2.0.0 Assignee: Unassigned Created: 24/Jun/14 1:03 PM Labels: trivial Priority: Normal Reporter: Kenneth Barber The tests in services.clj are using a fixed port 8080, which is causing some intermittent test failures. We should switch to using the dynamic ports instead. Some of this code was already implemented in import_export.clj, we should generalize this and use it in both places. Add Comment
Jira (PDB-720) Port already in use with cli/services.clj test
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-720 Port already in use with cli/services.clj test Change By: Kenneth Barber Sprint: 20140702to20140716 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/d/optout.
Jira (FACT-582) Tag the release and create packages
Title: Message Title Adrien Thebo commented on an issue Re: Tag the release and create packages Packages should be built against 82f8734. Add Comment Facter / FACT-582 Tag the release and create packages Tag and create packages * Developer provides the SHA - [~adrien] - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb) * checkout the sha * NOTE: If this is a final release, make sure you're releasing only the code that already went through rc, so don't let any new code get into the final releas... 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/d/optout.
Jira (PDB-720) Port already in use with cli/services.clj test
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-720 Port already in use with cli/services.clj test Example failure: https://jenkins.puppetlabs.com/job/PuppetDB%20Unit%20Tests/2024/PUPPETDB_DBTYPE=postgres,coordinator=coordinator/console 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/d/optout.
Jira (PUP-2557) Deprecate and remove node inheritance
Title: Message Title
Rob Reynolds commented on an issue
Re: Deprecate and remove node inheritance
site.pp:
node default {
package {'roundhouse':
ensure = latest,
provider = chocolatey,
}
}
node 'common' inherits default {
}
node /win*/ inherits 'common' {
#yup
}
current parser emits warnings:
C:\code\puppetlabs\puppetbundle exec puppet apply c:\vagrantshared\puppet\manifests\site.pp
Warning: Deprecation notice: Node inheritance is not supported in Puppet = 4.0.
0. See http://links.puppetlabs.com/puppet-node-inheritance-deprecation
(at c:/vagrantshared/puppet/manifests/site.pp:9)
Warning: Deprecation notice: Node inheritance is not supported in Puppet = 4.0.
0. See http://links.puppetlabs.com/puppet-node-inheritance-deprecation
(at c:/vagrantshared/puppet/manifests/site.pp:12)
Future parser emits warnings and errors:
C:\code\puppetlabs\puppetbundle exec puppet apply c:\vagrantshared\puppet\manifests\site.pp --parser future
Error: Node inheritance is not supported in Puppet = 4.0.0. See http://links.pu
ppetlabs.com/puppet-node-inheritance-deprecation at c:/vagrantshared/puppet/mani
fests/site.pp:9:24
Error: Node inheritance is not supported in Puppet = 4.0.0. See http://links.pu
ppetlabs.com/puppet-node-inheritance-deprecation at c:/vagrantshared/puppet/mani
fests/site.pp:12:22
Error: Could not parse for environment production: Found 2 errors. Giving up in
c:/vagrantshared/puppet/manifests/site.pp on node win-e5k8tm30719.corp.puppetlab
s.net
Error: Could not parse for environment production: Found 2 errors. Giving up in
c:/vagrantshared/puppet/manifests/site.pp on node win-e5k8tm30719.corp.puppetlab
s.net
The link works (comes to this issue currently)
Add Comment
Jira (PDB-121) Add Ruby 2.0 to spec test matrix for puppetdb
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-121 Add Ruby 2.0 to spec test matrix for puppetdb Change By: Kenneth Barber Sprint: 20140702to20140716 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/d/optout.
Jira (PUP-2557) Deprecate and remove node inheritance
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2557 Deprecate and remove node inheritance Change By: Rob Reynolds Assignee: RobReynolds 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/d/optout.
Jira (PUP-2557) Deprecate and remove node inheritance
Title: Message Title Rob Reynolds commented on an issue Re: Deprecate and remove node inheritance Henrik Lindberg Andy Parker is it fine to expect the above (a warning for EACH usage of inherits)? Add Comment Puppet / PUP-2557 Deprecate and remove node inheritance Node inheritance causes a large number of complications and ambiguities that make understanding puppet code difficult. There is very little reason to use it since much more effective reuse can be achieved using classes and defined types. On the next 3 series puppet that is using the current parser: the system must issue a deprecation warning when it en... 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/d/optout.
Jira (PUP-2828) Support pinning puppet-win32-ruby version for Puppet
Title: Message Title Josh Cooper commented on an issue Re: Support pinning puppet-win32-ruby version for Puppet Merged deeeda0be00 to stable. Add Comment Puppet / PUP-2828 Support pinning puppet-win32-ruby version for Puppet Presently Windows acceptance tests simply clone the https://github.com/puppetlabs/puppet-win32-ruby from the local internal mirror without specifying a revision. As we start to build Ruby 2 x64 on Windows, we're going to need to pin different jobs at different Ruby architecture / patch / gemsets for the sake of acceptance. This is a stopgap solution... 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/d/optout.
Jira (PUP-2557) Deprecate and remove node inheritance
Title: Message Title Henrik Lindberg commented on an issue Re: Deprecate and remove node inheritance That is how it is implemented - one warning per source location where node ... inherits is used in 'current', and an error when used in 'future'. The deprecation warnings can be squelched like other deprecation warnings. Add Comment Puppet / PUP-2557 Deprecate and remove node inheritance Node inheritance causes a large number of complications and ambiguities that make understanding puppet code difficult. There is very little reason to use it since much more effective reuse can be achieved using classes and defined types. On the next 3 series puppet that is using the current parser: the system must issue a deprecation warning when it en... 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
Jira (PUP-514) Add optional type to parameters
Title: Message Title
Kurt Wall commented on an issue
Re: Add optional type to parameters
Lambdas work. A single typed parameter is recognized:
$ bepa -e 'with (1)| Integer $x | { notice $x }' --parser future
Notice: 1
Notice: Compiled catalog for centos6-5-base.localdomain in environment production in 0.29 seconds
Notice: Finished catalog run in 0.03 seconds
An invalid type is rejected: $ bepa -e 'with (1)| String $x | { notice $x }
' --parser future Error: Evaluation Error: Error while evaluating a Function Call, lambda called with mis-matched arguments expected: lambda(String x) - arg count {1} actual: lambda(Integer) - arg count {1}
at line 1:1 on node centos6-5-base.localdomain Error: Evaluation Error: Error while evaluating a Function Call, lambda called with mis-matched arguments expected: lambda(String x) - arg count {1} actual: lambda(Integer) - arg count {1}
at line 1:1 on node centos6-5-base.localdomain
Multiple parameters also work
$ bepa -e 'with(Jenny,Ive,got,your,number) | String $x, String $y, String $z | { notice $x $y $z }
' --parser future Notice: Jenny Ive got Notice: Compiled catalog for centos6-5-base.localdomain in environment production in 0.30 seconds Notice: Finished catalog run in 0.04 seconds
As does captures-rest:
$ bepa -e 'with(Jenny,Ive,got,your,number) | String $x, String *$y | { notice $x $y }
' --parser future Notice: Jenny [Ive, got, your, number] Notice: Compiled catalog for centos6-5-base.localdomain in environment production in 0.30 seconds Notice: Finished catalog run in 0.03 seconds
Add Comment
Jira (PUP-2828) Support pinning puppet-win32-ruby version for Puppet
Title: Message Title Josh Cooper commented on an issue Re: Support pinning puppet-win32-ruby version for Puppet Merged ea304a0 to master. Verified the normal run installed ruby 1.9.3-x86. Also verified that setting environment variable allows ruby arch to be specified: $ env WIN32_RUBY_ARCH=x64 bundle exec rake ci:test:git SHA=b04c45643bcbf56d412651bae9cfc1181341d07d CONFIG=config/nodes/win2008r2.yaml TESTS=tests/puppet_apply_basics.rb And the ruby 2.0 x64 is installed as expected: teyrcl75hriadwm (agent) 13:25:13$ cd /opt/puppet-git-repos/puppet-win32-ruby git remote rm origin git remote add origin git://github.com/puppetlabs/puppet-win32-ruby.git git fetch origin git clean -fdx git checkout -f 2.0.0-x64 >From git://github.com/puppetlabs/puppet-win32-ruby * [new branch] 1.8.7 - origin/1.8.7 * [new branch] 1.9.3 - origin/1.9.3 * [new branch] 1.9.3-x86 - origin/1.9.3-x86 * [new branch] 2.0.0-x64 - origin/2.0.0-x64 * [new branch] update_openssl - origin/update_openssl Checking out files: 100% (7532/7532), done. Switched to a new branch '2.0.0-x64' Branch 2.0.0-x64 set up to track remote branch 2.0.0-x64 from origin. Add Comment Puppet / PUP-2828 Support pinning puppet-win32-ruby version for Puppet Presently Windows acceptance tests simply clone the https://github.com/puppetlabs/puppet-win32-ruby from the local internal mirror without specifying a revision. As we start to build Ruby 2 x64 on Windows, we're going to need to pin different
Jira (PUP-2755) Move iterative functions to 4x function API
Title: Message Title Henrik Lindberg commented on an issue Re: Move iterative functions to 4x function API The reason 0.7.0 causes problem was due to a bug in the logic that defines an optional or required lambda for a functions in the Functions API. It reused the same all callables object for all dispatchers. This is a no-no since that object ends up being contained in another type. A modeled object (types are all modeled) can only be contained by one container at a time, and an assignment to another container MOVES the object. The result was that the signature for Hash ended up getting its callable block moved from its signature type to however needed an all callables next. This did not happen when using RGen prior to 0.7.0 because of a bug in RGen that did not always move object that were moved between containers. Now, with the fixed bug, we were bitten by a bug in Puppet. So... good to catch this! (Fix coming). Add Comment Puppet / PUP-2755 Move iterative functions to 4x function API The iterative functions (each, map, filter, reduce, slice) should be moved to the 4x function API. (Currently there is a cheat implemented in the evaluator when these are called to avoid having the arguments transformed to the 3x function API). This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-721) Prepared statement cache uses a high amount of RAM for postgresql JDBC
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-721 Prepared statement cache uses a high amount of RAM for postgresql JDBC Issue Type: Improvement Assignee: Unassigned Created: 24/Jun/14 1:54 PM Priority: Normal Reporter: Kenneth Barber Had some reports of the prepared statement cache consuming RAM. In this case around 60 mb. Now arguably this could be the cost of performance, but after looking at the memory dumps we are finding these objects retaining as much as 200k of space in memory, (avg 150k in one sample). For now, users can obviously reduce the statement-cache-size to a lower number (like 200). This is a runtime configurable option. We should investigate why these objects are consuming so much RAM, potentially try upgrading to the 9.3 jdbc driver, (with 4.1 support) to see if this reduces the size. It might be that this excessive retention is a bug, or something we are doing. Hard to say. In some cases we believe the prepared statements are actually identical queries but with hard-coded parameters. We should go through our code and remove as much hard-coded SQL, and replace it with parameterization where possible as well. Add Comment
Jira (PUP-2511) Add parser function digest: uses digest_algorithm to hash, not strictly md5
Title: Message Title Henrik Lindberg commented on an issue Re: Add parser function digest: uses digest_algorithm to hash, not strictly md5 When future parser is used, the argument is a Puppet::Resource if the input is an upper case Bare Word. The error message isn't great in many respects (To many mentions of Error in the preamble. Add Comment Puppet / PUP-2511 Add parser function digest: uses digest_algorithm to hash, not strictly md5 Puppet has an md5 parser function, which returns the MD5 digest of its argument. On hosts configured for compliance with U.S. Federal Information Processing Standard (FIPS) 140-2, attempts to use the MD5 algorithm cause errors, because MD5 is no longer FIPS Approved. This patch adds a parser function called digest, which returns the digest of its arg... 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 (PDB-721) Prepared statement cache uses a high amount of RAM for postgresql JDBC
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-721 Prepared statement cache uses a high amount of RAM for postgresql JDBC Change By: Kenneth Barber Attachment: ScreenShot2014-06-24at13.45.11.png 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/d/optout.
Jira (PUP-335) Functions that require the future parser should be concretely identifiable
Title: Message Title Henrik Lindberg commented on an issue Re: Functions that require the future parser should be concretely identifiable Iterative functions are now moved. 4x functions are now very distinguishable from 3x functions. We are currently cheating by having a function stub with documentation in the 3x implementation of the 4x functions. Do we still need this umbrella issue? Now it is more a matter of concretely handle the documentation (in 3.7), and then later use new better doc tools (yard). Add Comment Puppet / PUP-335 Functions that require the future parser should be concretely identifiable Take a look at the function reference: http://docs.puppetlabs.com/references/3.latest/function.html There are a bunch of functions in there that will just plain explode on a stock Puppet 3.x install. (each, collect, etc.) This is because there’s no indication in these functions' code that they require the future parser. We need an indication of 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
Jira (PUP-2831) Puppet does not work with RGen 0.7.0
Title: Message Title Henrik Lindberg commented on an issue Re: Puppet does not work with RGen 0.7.0 We also have other issues (5 total) when running with RGen 0.7.0. Add Comment Puppet / PUP-2831 Puppet does not work with RGen 0.7.0 As discovered in PUP-2755, strange things happen when using RGen 0.7.0 with puppet. 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/d/optout.
Jira (PUP-796) Deprecate couchdb facts terminus and associated settings
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-796 Deprecate couchdb facts terminus and associated settings Change By: Adrien Thebo Component/s: NetworkingServices 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/d/optout.
Jira (PUP-1874) Deprecate the inventory service on master
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1874 Deprecate the inventory service on master Change By: Adrien Thebo Component/s: NetworkingServices 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/d/optout.
Jira (PUP-2379) Deprecate `recurse = inf` for file type
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2379 Deprecate `recurse = inf` for file type Change By: Josh Cooper Sprint: Week2014-7-23to2014-8-6 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/d/optout.
Jira (PUP-406) Deprecate stringify_fact = true
Title: Message Title Josh Cooper updated an issue Puppet / PUP-406 Deprecate stringify_fact = true Change By: Josh Cooper Sprint: Week2014-7-23to2014-8-6 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/d/optout.
Jira (PUP-2691) Real-world module skeletons still use the 'description' metadata property
Title: Message Title Anderson Mills assigned an issue to Anderson Mills Puppet / PUP-2691 Real-world module skeletons still use the 'description' metadata property Change By: Anderson Mills Assignee: PietervandeBruggen AndersonMills 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/d/optout.
Jira (PUP-586) Deprecate Instrumentation system
Title: Message Title Josh Cooper updated an issue Puppet / PUP-586 Deprecate Instrumentation system Change By: Josh Cooper Sprint: Week2014-7-23to2014-8-6 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/d/optout.
Jira (PUP-2614) Deprecate default source_permissions :use on all platforms
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2614 Deprecate default source_permissions :use on all platforms Change By: Josh Cooper Sprint: Week2014-7-23to2014-8-6 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/d/optout.
Jira (FACT-583) Smoke test packages
Title: Message Title
Eric Sorenson commented on an issue
Re: Smoke test packages
Smoke tested on EL5 and saw the new 'partitions' fact come all the way through to Puppet:
[root@gl5tch ~]# puppet apply --no-stringify_facts -e 'notice(inline_template(%= @partitions.inspect %))'
Notice: Scope(Class[main]): {sda2={size=41720805}, sda1={uuid=6fe41d81-a377-4740-a1b0-54529158806e, mount=/boot, size=208782, fi
lesystem=ext3\ SEC_TYPE=\ext2}}
Notice: Compiled catalog for gl5tch.local in environment production in 0.06 seconds
Add Comment
Facter / FACT-583
Smoke test packages
Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through th...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2777) Support Bundler workflow on x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2777 Support Bundler workflow on x64 Change By: Josh Cooper Sprint: Week2014- 6 7 - 25 9 to2014-7- 9 23 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/d/optout.
Jira (PUP-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-391 Validate FFI'ed native windows code against Ruby 2 x64 Change By: Josh Cooper Sprint: Week2014- 6 7 - 25 9 to2014-7- 9 23 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/d/optout.
