Jira (PUP-4332) Resource properties frozen if copied from $title
Title: Message Title
Craig Dunn updated an issue
Puppet / PUP-4332
Resource properties frozen if copied from $title
Change By:
Craig Dunn
Thereissomestrangebehaviourwhencreatinguserresourcesfromadefinedtypeviathecreate_resourcesfunction.Takethisexample;{code:title=manifests/accounts.pp}defineaccount($comment=$title,$uid,){user{$title:ensure=present,comment=$comment,}}{code}Notethatthe$commentvariabledefaultsto$title.Thefailurehappenswhenyoutryandusecreate_resourcestospinoffinstancesoftheaccountdefinedtypewithoutsupplyingcomment{code:title=Workingasexpected}account{'test1':uid='2022'}$accounts2={'test23'={'uid'='2024','comment'='foo'}}create_resources('account',$accounts2){code}However,ifweusecreate_resourceswithoutthecomment,IwouldexpectthesamebehaviourIgetwhendeclaringtheresourceusingthedefaultfor$comment(firstexampleabove),howeverthisfails...{code}$accounts={'test2'={'uid'='2023'}}create_resources('account',$accounts)Error:ParametercommentfailedonUser[ troot test2 ]:Mungingfailedforvalue troot test2 inclasscomment:can'tmodifyfrozenStringat...Wrappedexception:Mungingfailedforvalue troot test2 inclasscomment:can'tmodifyfrozenString{code}Itlookslikethe[Thischange|https://github.com/puppetlabs/puppet/commit/065c4f5b5c78ca8f16c189b55051681beb1c5052]aspartofPUP-1473highlightedtheissue.Itappearsthatinthelastscenario,thecommentparameterendsupafrozenstringbecauseitwascopiedfrom$titleandthiscausesforce_encodingtothrowanerror,butIonlyseemtoobservethisbehaviourusingcreate_resources.SoalthoughImseeingtheproblemintheuserstype,Isuspecttherootcausetobeelsewhere-thecommentpropertyshouldnotbefrozen,andwhydon'tIgetthesamebehaviourwhendeclaringtheresourcedirectly?Amodulelevelworkaroundistoquotetheparameterinthedefinedresourcetypeas:{code}$comment=${title},{code}Theabovepassesall3testsThesetestswererunonpuppet3.7.3ruby2.0.0p353
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4189) Add all per-user directories to file_paths specification
Title: Message Title Richard Clamp commented on PUP-4189 Re: Add all per-user directories to file_paths specification mco client needing a user logdir is a configuration decision made during the integration of MCollective into PE (so before my time), but it's not a generic concept for the mcollective client. There's no requirement to have logging configured to write a file, so it doesn't make sense to declare a default for it in the specification. As to the location of client dotfile, I just don't see the benefit in moving it to ~/.puppetlabs/mcollective from ~/.mcollective. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4332) Resource properties frozen if copied from $title
Title: Message Title Craig Dunn created an issue Puppet / PUP-4332 Resource properties frozen if copied from $title Issue Type: Bug Affects Versions: PUP 3.7.3 Assignee: Unassigned Created: 2015/03/27 2:40 AM Priority: Normal Reporter: Craig Dunn There is some strange behaviour when creating user resources from a defined type via the create_resources function. Take this example; manifests/accounts.pp define account ( $comment = $title,
Jira (PUP-3840) purge_ssh_keys doesn't purge keys when multiple keys with same comment are in authorized_keys file
Title: Message Title Jason Corley commented on PUP-3840 Re: purge_ssh_keys doesn't purge keys when multiple keys with same comment are in authorized_keys file I made a simple vagrant test for this. files I used were: Vagrantfile: VAGRANTFILE_API_VERSION = 2 Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| config.vm.box = puppetlabs/centos-7.0-64-puppet config.vm.box_url = https://atlas.hashicorp.com/puppetlabs/boxes/centos-7.0-64-puppet config.vm.provision puppet do |puppet| puppet.module_path = modules end end
Jira (FACT-887) Submodules should use internal mirror if so configured
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-887 Submodules should use internal mirror if so configured Issue Type: Bug Assignee: Eric Sorenson Created: 2015/03/27 7:53 AM Priority: Normal Reporter: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-887) Submodules should use internal mirror if so configured
Title: Message Title Kylo Ginsberg commented on FACT-887 Re: Submodules should use internal mirror if so configured Note that facter packaging jobs have failed because the submodule is pointed at github directly so doesn't use the mirror. Example: https://jenkins.puppetlabs.com/job/Facter-Packaging-master/324/ Github is currently under massive DDOS so we're more exposed to this. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-887) Submodules should use internal mirror if so configured
Title: Message Title Kylo Ginsberg commented on FACT-887 Re: Submodules should use internal mirror if so configured Snippet git submodule init # timeout=10 git submodule sync # timeout=10 git config --get remote.origin.url # timeout=10 git submodule update --init --recursive FATAL: Command git submodule update --init --recursive returned status code 1: stdout: Submodule 'vendor/leatherman' () registered for path 'vendor/leatherman' Cloning into 'vendor/leatherman'... stderr: error: RPC failed; result=7, HTTP code = 0 fatal: The remote end hung up unexpectedly
Jira (FACT-887) Submodules should use internal mirror if so configured
Title: Message Title Justin Stoller commented on FACT-887 Re: Submodules should use internal mirror if so configured I think the best way to handle things like this is to have an init job that resolves the dependencies and then creates a tarball the downstream tests, packaging and promotion can consume. That way you're you limiting your exposure to Github flakiness at one unambiguous point in your pipeline. We do this on the modules side of the house. None of the modules are mirrored internally. We reach out to the internet only once in the init step of each pipe. Combined with the SCM retry feature of Jenkins I don't know if Github has ever been a source of flakiness in the 400+ jobs that run on their Jenkins. This may require tooling updates for some of RE's tools (like the AIO pipeline currently creates said artifact, uses it every test target whether spec or acceptance[1] but then vanagon reaches out to the internet for every build target). 1. We aren't doing this for Windows specs because the slaves aren't currently set up to untar archives. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-888) Facter does not properly detect KVM when CPU type is not qenu32/qumu64
Title: Message Title Melissa Stone created an issue Facter / FACT-888 Facter does not properly detect KVM when CPU type is not qenu32/qumu64 Issue Type: Bug Assignee: Melissa Stone Created: 2015/03/27 10:43 AM Priority: Normal Reporter: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-3959) Acceptance test failure in external_ca_support/jetty_external_root_ca.rb
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3959 Acceptance test failure in external_ca_support/jetty_external_root_ca.rb Nothing for Test Rail here. Change By: Kurt Wall QA Contact: KurtWall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4189) Add all per-user directories to file_paths specification
Title: Message Title Eric Thompson commented on PUP-4189 Re: Add all per-user directories to file_paths specification should consider adding these to the acceptance test as well. qa can subtask if no one wants to do that part... Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4259) puppet-agent 0.9.1 2015-03-25 Release
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4259 puppet-agent 0.9.1 2015-03-25 Release Change By: Kurt Wall QA Contact: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4259) puppet-agent 0.9.1 2015-03-25 Release
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4259 puppet-agent 0.9.1 2015-03-25 Release Nothing for Test Rail here. Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-864) Update facter#2.x acceptance config names to match puppet's
Title: Message Title Kurt Wall updated an issue Facter / FACT-864 Update facter#2.x acceptance config names to match puppet's Nothing for Test Rail here. Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4004) Remove acceptance workaround that creates the puppetserver cache related directories
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4004 Remove acceptance workaround that creates the puppetserver cache related directories Nothing for Test Rail here. Change By: Kurt Wall QA Contact: KurtWall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-864) Update facter#2.x acceptance config names to match puppet's
Title: Message Title Kurt Wall updated an issue Facter / FACT-864 Update facter#2.x acceptance config names to match puppet's Change By: Kurt Wall QA Contact: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (HI-366) Update hiera#master acceptance configs to match puppet#master's
Title: Message Title Kurt Wall updated an issue Hiera / HI-366 Update hiera#master acceptance configs to match puppet#master's Nothing for Test Rail here. Change By: Kurt Wall QA Contact: KurtWall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4150) Puppet-Agent Acceptance on RHEL5/6 failed
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4150 Puppet-Agent Acceptance on RHEL5/6 failed Nothing for Test Rail here. Change By: Kurt Wall QA Contact: KurtWall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-887) Submodules should use internal mirror if so configured
Title: Message Title Branan Riley commented on FACT-887 Re: Submodules should use internal mirror if so configured I'm not sure what the best way to handle this is. We could tell Jenkins not to checkout submodules, then rewrite the target in the build script and check it out ourselves, I suppose. That feels super fragile to me, though. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-1291) scheduled_task : add support for every X minutes or hours mode
Title: Message Title Rob Reynolds commented on PUP-1291 Re: scheduled_task : add support for every X minutes or hours mode I've tested https://gist.github.com/ferventcoder/61ff24e61836dc40aec3 on: Ruby 1.9.3-x86 / Windows 2003 x86 Ruby 2.1.5-x86 / Windows 2003 x86 Ruby 2.1.5-x64 / Windows 7 x64 Ruby 2.0.0-x64 / Windows 7 x64 With the changes. All is working appropriately. Note for the reviewer, there are failure scenarios in the manifest (uncomment them). Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-1291) scheduled_task : add support for every X minutes or hours mode
Title: Message Title Rob Reynolds commented on PUP-1291 Re: scheduled_task : add support for every X minutes or hours mode I'm really not a huge fan of the names though. minutes_interval could probably better be represented as repeat_interval_minutes minutes_duration could probably be represented as repeat_duration_minutes Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-1291) scheduled_task : add support for every X minutes or hours mode
Title: Message Title Rob Reynolds assigned an issue to Ethan Brown Puppet / PUP-1291 scheduled_task : add support for every X minutes or hours mode Change By: Rob Reynolds Assignee: RobReynolds EthanBrown Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-867) Port xendomains fact to Facter 3
Title: Message Title William Hopper commented on FACT-867 Re: Port xendomains fact to Facter 3 The original xendomains fact returned a comma delimited string, such as web01,mailserver. Should we take this opportunity to upgrade this to an array-based structured fact? xendomains = [web01, mailserver] Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-888) Facter does not properly detect KVM when CPU type is not qenu32/qumu64
Title: Message Title Melissa Stone updated an issue Facter / FACT-888 Facter does not properly detect KVM when CPU type is not qenu32/qumu64 Change By: Melissa Stone Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-888) Facter does not properly detect KVM when CPU type is not qenu32/qumu64
Title: Message Title Melissa Stone commented on FACT-888 Re: Facter does not properly detect KVM when CPU type is not qenu32/qumu64 Michael Smith you commented on https://github.com/puppetlabs/facter/pull/849 that this should get into facter 3. I've retargeted the previous pull request against facter/2.x, and I'll look into getting it into facter/master as well. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-3991) scanf only implemented for future parser
Title: Message Title Kurt Wall assigned an issue to Unassigned Tracked as test case C64287 Puppet / PUP-3991 scanf only implemented for future parser Change By: Kurt Wall Assignee: KurtWall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-1227) Test new table structure and fact path/value GC at scale
Title: Message Title Wyatt Alt commented on PDB-1227 Re: Test new table structure and fact path/value GC at scale This patch looks great based on my performance testing. On stable we can reproduce the fact_paths problem with 30,000 simulated nodes checking in every 30 minutes with a random percentage of 10. The problem does not occur on stable at 20,000 nodes, so the breaking point is somewhere between 20k and 30k. The CPUs on the postgres server are pegged on deletes more or less as soon as commands switch from being processed with add-facts! to update-facts!, i.e once the database stores 30k certnames. The gc issues at this point will cause the queue size to explode and all kinds of problems to occur. This patch on the other hand can handle 30k and 50k nodes without breaking a sweat – in fact, using the -i and -n settings we have not been able to submit factsets fast enough to back up the queue. When we set -n to 10, only 17 commands per second were being submitted, which means the benchmark tool was underperforming (or our metrics are wrong). Queue size remains at or around 0 during both additions and updates for any of those numbers. The -n and -N flags of the benchmark tool allow you to submit commands unthrottled. Doing this will back up the queue both here and on stable, but is not a realistic scenario. Migration of 30,000 nodes of data from stable to this patch took two and a half minutes, which is fine. All in all this seems to completely solve our problem. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (FACT-888) Facter does not properly detect KVM when CPU type is not qenu32/qumu64
Title: Message Title Melissa Stone updated an issue Facter / FACT-888 Facter does not properly detect KVM when CPU type is not qenu32/qumu64 Change By: Melissa Stone Fix Version/s: FACT2.4.3 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-867) Port xendomains fact to Facter 3
Title: Message Title William Hopper commented on FACT-867 Re: Port xendomains fact to Facter 3 Also, as per Melissa Stone, we have a community member that may be interested in implementing this fact. He has experience with Xen, which is helpful since we don't really have a great way to do any testing ourselves. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-1328) Update changelog/release notes
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-1328 Update changelog/release notes Change By: Rob Browning Assignee: RobBrowning Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-1327) Is checklist current
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-1327 Is checklist current Change By: Rob Browning Assignee: RobBrowning Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-1391) puppet device cannot create certs when run as root
Title: Message Title Chris Barker updated an issue Puppet / PUP-1391 puppet device cannot create certs when run as root Change By: Chris Barker CS Priority: NeedsPriority Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-887) Submodules should use internal mirror if so configured
Title: Message Title Justin Stoller commented on FACT-887 Re: Submodules should use internal mirror if so configured Relating this to another git mirror ticket as my preferred solution to this issue largely removes our usage of the gitmirror and I want to track the convo that may or may not happen as it relates to both Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-830) xendomains returning empty on debian hosts
Title: Message Title Melissa Stone updated an issue Facter / FACT-830 xendomains returning empty on debian hosts Change By: Melissa Stone Scrum Team: ReleaseEngineering Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-1346) PR (1320): (maint) applied-migrations: don't ignore exceptions - rbrw
Title: Message Title gepetto-bot commented on PDB-1346 Re: PR (1320): (maint) applied-migrations: don't ignore exceptions - rbrw Pull request (maint) applied-migrations: don't ignore exceptions has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-1348) PR (1324): (maint) Clean up BoneCP resources when finished - rbrw
Title: Message Title gepetto-bot commented on PDB-1348 Re: PR (1324): (maint) Clean up BoneCP resources when finished - rbrw wkalt commented: @rlb I'm not sure what I should be doing to verify the change. Could you expand on the demonstration part? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-865) Native facter lost the output from stderr in external (and custom?) facts
Title: Message Title Peter Huene updated an issue Facter / FACT-865 Native facter lost the output from stderr in external (and custom?) facts Change By: Peter Huene Story Points: 2 3 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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.
