Jira (PUP-4926) Relationship with a parameter does not work
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-4926
Relationship with a parameter does not work
Change By:
Julien Pivotto
Test.pp:{code}notify{'1':}definemynotify(Type[Notify]$req){notify{$title:}$req-Mynotify[$title]}mynotify{'2':req=Notify['1']}{code}Expected:Relationshipworks:Notify['1']istriggeredbeforeNotify['2']Result:{code}puppetapplytest.ppError:EvaluationError:Illegalrelationshipoperand,cannotformarelationshipwithanObject.ACatalogtypeisrequired.at/root/test.pp:9:8onnodefoo{code} Workaround:{code}notify{'1':}definemynotify(String$prereq){$req=Notify[$prereq]notify{$title:}$req-Mynotify[$title]}mynotify{'2':prereq='1'}{code}{code}Notice:Compiledcatalogforfooinenvironmentproductionin0.48secondsNotice:1Notice:/Stage[main]/Main/Notify[1]/message:defined'message'as'1'Notice:2Notice:/Stage[main]/Main/Mynotify[2]/Notify[2]/message:defined'message'as'2'Notice:Appliedcatalogin0.06seconds{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-4926) Relationship with a parameter does not work
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-4926
Relationship with a parameter does not work
Change By:
Julien Pivotto
Test.pp: {code}notify{'1':}definemynotify(Type[Notify]$req){notify{$title:}$req-Mynotify[$title]}mynotify{'2':req=Notify['1']}{code} h2. Expected:Relationshipworks:Notify['1']istriggeredbeforeNotify['2'] h2. Result:{code}puppetapplytest.ppError:EvaluationError:Illegalrelationshipoperand,cannotformarelationshipwithanObject.ACatalogtypeisrequired.at/root/test.pp:9:8onnodefoo{code} h2. Workaround:{code}notify{'1':}definemynotify(String$prereq){$req=Notify[$prereq]notify{$title:}$req-Mynotify[$title]}mynotify{'2':prereq='1'}{code}{code}Notice:Compiledcatalogforfooinenvironmentproductionin0.48secondsNotice:1Notice:/Stage[main]/Main/Notify[1]/message:defined'message'as'1'Notice:2Notice:/Stage[main]/Main/Mynotify[2]/Notify[2]/message:defined'message'as'2'Notice:Appliedcatalogin0.06seconds{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-4926) Relationship with a parameter does not work
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-4926
Relationship with a parameter does not work
Change By:
Julien Pivotto
Test.pp:{code}notify{'1':}definemynotify(Type[Notify]$req){notify{$title:}$req-Mynotify[$title]}mynotify{'2':req=Notify['1']}{code} Expected: Relationshipworks:Notify['1']istriggeredbeforeNotify['2'] Result:{code}puppetapplytest.ppError:EvaluationError:Illegalrelationshipoperand,cannotformarelationshipwithanObject.ACatalogtypeisrequired.at/root/test.pp:9:8onnodenmdev195.be.alcatel-lucent.com{code} Expect:Relationshipworks
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-4926) Relationship with a parameter does not zork
Title: Message Title
Julien Pivotto created an issue
Puppet / PUP-4926
Relationship with a parameter does not zork
Issue Type:
Bug
Affects Versions:
puppet-agent 1.2.2
Assignee:
Unassigned
Components:
DSL, Language
Created:
2015/07/27 5:57 AM
Priority:
Normal
Reporter:
Julien Pivotto
Test.pp:
notify {
'1':
}
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider And you're OK with 'scope' being the default? Keeping it that way will be more backward compatible but having 'lookup' be the default seems more logical. 'scope' should be default, yes. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4926) Relationship with a parameter does not work
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-4926
Relationship with a parameter does not work
Change By:
Julien Pivotto
Test.pp:{code}notify{'1':}definemynotify(Type[Notify]$req){notify{$title:}$req-Mynotify[$title]}mynotify{'2':req=Notify['1']}{code}Expected:Relationshipworks:Notify['1']istriggeredbeforeNotify['2']Result:{code}puppetapplytest.ppError:EvaluationError:Illegalrelationshipoperand,cannotformarelationshipwithanObject.ACatalogtypeisrequired.at/root/test.pp:9:8onnode nmdev195.be.alcatel-lucent.com foo {code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-4926) Relationship with a parameter does not work
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-4926
Relationship with a parameter does not work
Change By:
Julien Pivotto
Test.pp:{code}notify{'1':}definemynotify(Type[Notify]$req){notify{$title:}$req-Mynotify[$title]}mynotify{'2':req=Notify['1']}{code} Result: {code}puppetapplytest.ppError:EvaluationError:Illegalrelationshipoperand,cannotformarelationshipwithanObject.ACatalogtypeisrequired.at/root/test.pp:9:8onnodenmdev195.be.alcatel-lucent.com{code} Expect:Relationshipworks
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-4926) Relationship with a parameter does not work
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-4926 Relationship with a parameter does not work Change By: Julien Pivotto Summary: Relationshipwithaparameterdoesnot zork work Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider The lookup part can be qualified in the Puppet way with double colons, but from a hiera perspective the double colons are just part of the key - there is no difference in semantics between x::y::z and say xaayaaz except for the final step of directing a fully qualified key to the corresponding module data provider - e.g. x::a is directed to module a's provider if the global and environment providers did not find a resolution for the full key. The operations of applying dot notation expressions comes after the resolution of the name. Don't see why we need two lookup mechanisms? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider Another detail that we need to sort out is the Hiera qualified lookup using dot-separated names. Do we want two types of qualified names? Not sure what you mean by that, can you clarify? The format should be compatible with current hiera data. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider We use double colon to access module data a::b and in Hiera we recently introduced dot notation to navigate in hashes and arrays. We now face the possibility of names like a::b.c.d or a::b.3. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4927) Add logfile option to exec
Title: Message Title Jeff Sparrow created an issue Puppet / PUP-4927 Add logfile option to exec Issue Type: New Feature Assignee: Unassigned Components: Platform Created: 2015/07/27 6:26 AM Environment: Windows Priority: Normal Reporter: Jeff Sparrow It would be very beneficial if puppet had a attribute for the exec parameter to log output to a file. Currently, running a command in windows and redirecting to a file really seems to be it or miss. It required fiddling around with different redirects for cmd, different ones for different versions of powershell, etc. In addition you have to actually call C:\Windows\System32\cmd.exe for puppet to even understand redirects (aside from |). Give windows users a way to handle logging to files without having to monkey around with different path calls, or different redirects in different environments.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider No need to have two mechanisms. Just wanted to assert that we do intend to use names that have both double colons and dot-notations in them. There are alternatives such as allowing a name to be separated by either dots or double colon (but not both in the same name). Another thing to have in mind is that a JSON or YAML provider doesn't necessarily imply a hiera provider (or does it?). I intend to make the concept of interpolation available to all providers b.t.w. Not just by Hiera with JSON and YAML. I see that as implied when weaving this together. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider The providers we are doing now are hiera specific data providers following the current hiera scheme as much as possible. I can imagine supporting a different version of that format some time in the future - to clean up and make the format sane. I think it may be premature to try to implement general json/yaml backends, or to think too much about what a better format should be (except possibly where there are implementation concerns we want to address) - for now just do what is required for backward compatible hiera data. Not sure about what bringing interpolation to all implementations means in the context of say the function data provider. Does that mean that users can get interpolation by returning interpolation expressions in strings? When using the function provider, there is also the opportunity to use more advanced lookup semantics - e.g. specify deep merge etc, but we have no way of making such calls be lazy. I see such functionality as a stretch goal and not covered by this ticket. Regarding names - we have keys, they follow puppet naming (no dots), and navigation of a resulting value of a lookup (has dots). You cannot lookup a value for a key with dots in it - it is an illegal puppet name anyway. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4930) Provide helpful error message when provider does not have instances defined
Title: Message Title
Daniele Sluijters updated an issue
Puppet / PUP-4930
Provide helpful error message when provider does not have instances defined
Change By:
Daniele Sluijters
WhenusingtheRALtogetalistofresources,iftheproviderdoesnothavethe{{instances}}methoddefinedyouget:{code}Error:Couldnotrun:Providergetsetseboolhasnotdefinedthe'instances'classmethod{code}Regurgitating and an implementationdetailisincrediblyunhelpfulexceptforthosefewthatactuallyknowhowtypesandproviderswork.I'dliketosuggestweaddadefault{{instances}}methodonprovidersthatgivesusamorehelpfulerrormessagewhicheveryprovidermustthenoverride(whichthey'lldoanywayiftheywanttoprovidethisfeature,ifnottheygetauserfriendlyerrormessageforfree).
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-4928) PMT calculates puppetlabs/concat dependencies incorrectly
Title: Message Title Ben Ford created an issue Puppet / PUP-4928 PMT calculates puppetlabs/concat dependencies incorrectly Issue Type: Bug Assignee: Unassigned Components: PMT Created: 2015/07/27 9:30 AM Priority: Normal Reporter: Ben Ford Modules that depend on puppetlabs/concat can sometimes fail dependency resolution due to concat-2.0 being pulled. See transcript below: root@master:~ # puppet module install gentoo-portage --modulepath /etc/puppetlabs/code/modules/ Notice: Preparing to install into /etc/puppetlabs/code/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ...
Jira (PUP-4928) PMT calculates puppetlabs/concat dependencies incorrectly
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-4928
PMT calculates puppetlabs/concat dependencies incorrectly
Change By:
Ben Ford
Ifyoucurrentlyhave{{puppetlabs/concat-2.0.0}}installed, dodules modules thatdependon{{puppetlabs/concat}}willfaildependencyresolutionduetothatversionofconcatbeingpulled.Seetranscriptbelow:{code}root@master:~#puppetmoduleinstallgentoo-portage--modulepath/etc/puppetlabs/code/modules/Notice:Preparingtoinstallinto/etc/puppetlabs/code/modules...Notice:Downloadingfromhttps://forgeapi.puppetlabs.com...Error:Couldnotinstallmodule'gentoo-portage'(latest)Dependency'ripienaar-concat'(v0.2.0)wouldoverwrite/etc/puppetlabs/code/modules/concatCurrently,'puppetlabs-concat'(v2.0.0)isinstalledtothatdirectoryUse`puppetmoduleinstall--ignore-dependencies`toinstallonlythismoduleroot@master:~#puppetmoduleinstallgentoo-portage--modulepath/etc/puppetlabs/code/modules/--ignore-dependenciesNotice:Preparingtoinstallinto/etc/puppetlabs/code/modules...Notice:Downloadingfromhttps://forgeapi.puppetlabs.com...Notice:Installing--donotinterrupt.../etc/puppetlabs/code/modules└──gentoo-portage(v2.3.0)root@master:~#cat/etc/puppetlabs/code/modules/portage/metadata.json{name:gentoo-portage,version:2.3.0,author:Gentoo,summary:PuppettypesandprovidersforGentooportage,license:GPLv2,source:https://github.com/gentoo/puppet-portage.git,project_page:https://github.com/gentoo/puppet-portage,issues_url:https://github.com/gentoo/puppet-portage/issues,dependencies:[{name:puppetlabs/concat}]}root@master:~#puppetmoduleinstallgentoo-portage--modulepath/etc/puppetlabs/code/modules/--version2.3.0Notice:Preparingtoinstallinto/etc/puppetlabs/code/modules...Notice:Downloadingfromhttps://forgeapi.puppetlabs.com...Notice:Installing--donotinterrupt.../etc/puppetlabs/code/modules└─┬gentoo-portage(v2.3.0)└──puppetlabs-concat(v1.2.4)root@master:~#rm-rf/etc/puppetlabs/code/modules/{concat,portage}root@master:~#puppetmoduleinstallgentoo-portage--modulepath/etc/puppetlabs/code/modules/Notice:Preparingtoinstallinto/etc/puppetlabs/code/modules...Notice:Downloadingfromhttps://forgeapi.puppetlabs.com...Notice:Installing--donotinterrupt.../etc/puppetlabs/code/modules└─┬gentoo-portage(v2.3.0)└─┬puppetlabs-concat(v1.2.4)└──puppetlabs-stdlib(v4.7.0){code}
Add Comment
Jira (PUP-4927) Add logfile option to exec
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-4927 Add logfile option to exec Change By: Rob Reynolds Labels: windows Scrum Team: Windows Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1786) Spike - Exported Resources for HA
Title: Message Title Beth Cornils commented on PDB-1786 Re: Spike - Exported Resources for HA Excellent, I'll follow up with Ryan Coleman. There are some strong feelings about this and I want to make sure I represent current and future state in our plans. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4929) Acceptance test for packages has dependency on rubygems.org
Title: Message Title Michael Smith created an issue Puppet / PUP-4929 Acceptance test for packages has dependency on rubygems.org Issue Type: Bug Assignee: Unassigned Created: 2015/07/27 9:52 AM Priority: Normal Reporter: Michael Smith The acceptance test tests/resource/package.common_package_name_in_different_providers.rb uses rubygems.org during its run to install a gem. This should be updated to use GEM_SOURCE if set so we can use internal infrastructure. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4912) Puppet on french version of windows
Title: Message Title Ethan Brown commented on PUP-4912 Re: Puppet on french version of windows Hi Gabriel Veilleux - We've actually never supported Windows XP as a platform. That said, you could try updating to a newer Puppet version than 3.4.3. The latest in the 3.x line is 3.8.1. As of version 3.7.0, we changed Puppet to use all wide character Win32 APIs. However, Ruby itself was still using ANSI versions of Win32 APIs in 1.9.3 on 32-bit Windows, and still did a poor job of handling encodings like UTF8, so you might still run into issues there. If you're comfortable using our new puppet-agent packages, which build on the latest 4.x version of Puppet, and uses Ruby 2.1, I would suggest giving that a shot. Ruby 2.0 moved (mostly) away from using ANSI versions of the Win32 APIs, so I think you will fare better there. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4928) PMT calculates puppetlabs/concat dependencies incorrectly
Title: Message Title Alex Dreyer commented on PUP-4928 Re: PMT calculates puppetlabs/concat dependencies incorrectly It looks like there are two bugs at play here. 1. PMT doesn't use the local puppetlabs-concats metadata and refuses to consider puppetlabs-concat-2.0.0 in dependency resolution when it is deleted on forge. 2. PMT doesn't constrain dependencies to avoid namespace conflicts during resolution. It looks like this only happens after dependency resolution. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4757) Update pre-suites to install puppet-agent on pe platforms
Title: Message Title Kevin Imber assigned an issue to Kevin Imber Puppet / PUP-4757 Update pre-suites to install puppet-agent on pe platforms Change By: Kevin Imber Assignee: KevinImber Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4927) Add logfile option to exec
Title: Message Title Rob Reynolds commented on PUP-4927 Re: Add logfile option to exec Jeff Sparrow can you expand on what you are trying to do? Write now if you turn on logoutput it will write the output to the puppet log file. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4934) Unit tests for static compiler are broken
Title: Message Title Hailee Kenney created an issue Puppet / PUP-4934 Unit tests for static compiler are broken Issue Type: Bug Assignee: Unassigned Created: 2015/07/27 11:14 AM Priority: Normal Reporter: Hailee Kenney Some of the tests in the static compiler spec are not testing what they are expected to as it seems the catalog never contains any File resources. For more details, see the discussion on these two pull requests: https://github.com/puppetlabs/puppet/pull/4052 https://github.com/puppetlabs/puppet/pull/4041 The tests in question are located here: https://github.com/puppetlabs/puppet/blob/master/spec/unit/indirector/catalog/static_compiler_spec.rb Add Comment
Jira (PUP-4925) Puppet Agent - Failure to Upgrade Agent on Windows 2003 R2
Title: Message Title Rob Reynolds commented on PUP-4925 Re: Puppet Agent - Failure to Upgrade Agent on Windows 2003 R2 Trying to rule out Windows Installer, this should be attempted on a system with Windows Installer (msiexec) less than v5. https://support.microsoft.com/en-us/kb/893803 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4933) Remove cfacter setting
Title: Message Title Josh Cooper created an issue Puppet / PUP-4933 Remove cfacter setting Issue Type: Task Assignee: Unassigned Created: 2015/07/27 10:38 AM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Josh Cooper Remove the cfacter setting which is no longer needed. May also want to remove `Puppet.features.cfacter?` Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4917) puppet resource package does not display McAfee Agent
Title: Message Title Rob Reynolds commented on PUP-4917 Re: puppet resource package does not display McAfee Agent Paul W can you give me the output for where this key is located? HCKU\Software\Microsoft\Windows\CurrentVersion\Uninstall HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall HKLM\Software\Wow6432\Microsoft\Windows\CurrentVersion\Uninstall Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4924) Puppet Windows - Upgrading from 3.7.5 causes Ruby.exe/Rubyw.exe to go missing
Title: Message Title Rob Reynolds commented on PUP-4924 Re: Puppet Windows - Upgrading from 3.7.5 causes Ruby.exe/Rubyw.exe to go missing Note in some cases it required the upgrade / downgrade to be installed twice, even using psexec/winexe. I haven't attempted shutting down the service first to see what happens. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4934) Unit tests for static compiler are broken
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-4934 Unit tests for static compiler are broken Change By: Hailee Kenney Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4928) PMT calculates puppetlabs/concat dependencies incorrectly
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-4928
PMT calculates puppetlabs/concat dependencies incorrectly
Change By:
Ben Ford
Modules Ifyoucurrentlyhave{{puppetlabs/concat-2.0.0}}installed,dodules thatdependon{{puppetlabs/concat}} cansometimes will faildependencyresolutiondueto thatversionof concat -2.0 beingpulled.Seetranscriptbelow:{code}root@master:~#puppetmoduleinstallgentoo-portage--modulepath/etc/puppetlabs/code/modules/Notice:Preparingtoinstallinto/etc/puppetlabs/code/modules...Notice:Downloadingfromhttps://forgeapi.puppetlabs.com...Error:Couldnotinstallmodule'gentoo-portage'(latest)Dependency'ripienaar-concat'(v0.2.0)wouldoverwrite/etc/puppetlabs/code/modules/concatCurrently,'puppetlabs-concat'(v2.0.0)isinstalledtothatdirectoryUse`puppetmoduleinstall--ignore-dependencies`toinstallonlythismoduleroot@master:~#puppetmoduleinstallgentoo-portage--modulepath/etc/puppetlabs/code/modules/--ignore-dependenciesNotice:Preparingtoinstallinto/etc/puppetlabs/code/modules...Notice:Downloadingfromhttps://forgeapi.puppetlabs.com...Notice:Installing--donotinterrupt.../etc/puppetlabs/code/modules└──gentoo-portage(v2.3.0)root@master:~#cat/etc/puppetlabs/code/modules/portage/metadata.json{name:gentoo-portage,version:2.3.0,author:Gentoo,summary:PuppettypesandprovidersforGentooportage,license:GPLv2,source:https://github.com/gentoo/puppet-portage.git,project_page:https://github.com/gentoo/puppet-portage,issues_url:https://github.com/gentoo/puppet-portage/issues,dependencies:[{name:puppetlabs/concat}]}root@master:~#puppetmoduleinstallgentoo-portage--modulepath/etc/puppetlabs/code/modules/--version2.3.0Notice:Preparingtoinstallinto/etc/puppetlabs/code/modules...Notice:Downloadingfromhttps://forgeapi.puppetlabs.com...Notice:Installing--donotinterrupt.../etc/puppetlabs/code/modules└─┬gentoo-portage(v2.3.0)└──puppetlabs-concat(v1.2.4)root@master:~#rm-rf/etc/puppetlabs/code/modules/{concat,portage}root@master:~#puppetmoduleinstallgentoo-portage--modulepath/etc/puppetlabs/code/modules/Notice:Preparingtoinstallinto/etc/puppetlabs/code/modules...Notice:Downloadingfromhttps://forgeapi.puppetlabs.com...Notice:Installing--donotinterrupt.../etc/puppetlabs/code/modules└─┬gentoo-portage(v2.3.0)└─┬puppetlabs-concat(v1.2.4)└──puppetlabs-stdlib(v4.7.0){code}
Add Comment
Jira (PUP-4930) Provide helpful error message when provider does not have instances defined
Title: Message Title Daniele Sluijters created an issue Puppet / PUP-4930 Provide helpful error message when provider does not have instances defined Issue Type: Bug Assignee: Kylo Ginsberg Components: Types and Providers Created: 2015/07/27 10:09 AM Environment: Any Puppet version ever on any platform Priority: Normal Reporter: Daniele Sluijters When using the RAL to get a list of resources, if the provider does not have the instances method defined you get: Error: Could not run: Provider getsetsebool has not defined the 'instances' class method Regurgitating and implementation detail is incredibly unhelpful except for those few that actually know how
Jira (PUP-4931) seboolean type should define instances method
Title: Message Title Ben Ford created an issue Puppet / PUP-4931 seboolean type should define instances method Issue Type: Bug Assignee: Kylo Ginsberg Components: Types and Providers Created: 2015/07/27 10:15 AM Priority: Normal Reporter: Ben Ford According to this page listing SELinux booleans is easy with getsebool -a. The provider should define the instances method so puppet resource works with this type. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html Add Comment
Jira (PUP-4932) Deprecate cfacter setting
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-4932
Deprecate cfacter setting
Change By:
Josh Cooper
Puppet'scfactersettingis not no longerneeded.Thisticketistodeprecatethesettingifsomeonedoessetit,e.g.{{puppetagent--cfacter}}.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-4932) Deprecate cfacter setting
Title: Message Title Josh Cooper created an issue Puppet / PUP-4932 Deprecate cfacter setting Issue Type: Task Assignee: Unassigned Created: 2015/07/27 10:36 AM Fix Versions: PUP 4.3.0 Priority: Normal Reporter: Josh Cooper Puppet's cfacter setting is not longer needed. This ticket is to deprecate the setting if someone does set it, e.g. puppet agent --cfacter. Add Comment This message was sent by
Jira (PUP-4917) puppet resource package does not display McAfee Agent
Title: Message Title Alexander Johnson updated an issue Puppet / PUP-4917 puppet resource package does not display McAfee Agent Change By: Alexander Johnson Scrum Team: Windows Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4927) Add logfile option to exec
Title: Message Title Josh Cooper commented on PUP-4927 Re: Add logfile option to exec Jeff Sparrow The exec type has a logoutput = true/false option, which will write the output of the exec command to stdout, is written to the Application Event Log, and included in the report sent to the master. It works for puppet's built-in exec provider as well as the powershell provider. Is that sufficient for what you're looking for? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4927) Add logfile option to exec
Title: Message Title Josh Cooper assigned an issue to Jeff Sparrow Puppet / PUP-4927 Add logfile option to exec Change By: Josh Cooper Assignee: JeffSparrow Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4912) Puppet on french version of windows
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-4912 Puppet on french version of windows Change By: Rob Reynolds Component/s: Windows Labels: windows Scrum Team: Windows Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4912) Puppet on french version of windows
Title: Message Title Rob Reynolds commented on PUP-4912 Re: Puppet on french version of windows Gabriel Veilleux If after you upgrade from XP to a supported version of Windows for Puppet, you run into this again, please file a new issue. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4912) Puppet on french version of windows
Title: Message Title Rob Reynolds commented on PUP-4912 Re: Puppet on french version of windows Unfortunately XP is not supported. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-891) dynamic library support cannot determine first_load on AIX
Title: Message Title Michael Smith commented on FACT-891 Re: dynamic library support cannot determine first_load on AIX FACT-1129 is solving a problem exposed by this work-around. We should fix the load logic, not introduce extra loadpath init. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4935) $HOME directory of the Puppet user is writable
Title: Message Title Julien Pivotto assigned an issue to Unassigned Puppet / PUP-4935 $HOME directory of the Puppet user is writable Change By: Julien Pivotto Assignee: JulienPivotto Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1151) Downcase os* and dmi* facts
Title: Message Title
Daniele Sluijters created an issue
Facter / FACT-1151
Downcase os* and dmi* facts
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2015/07/27 12:37 PM
Priority:
Normal
Reporter:
Daniele Sluijters
When running Facter the os* facts look like this:
os = {
architecture = amd64,
distro = {
codename = trusty,
description = Ubuntu 14.04.2 LTS,
Jira (PUP-4925) Puppet Agent - Failure to Upgrade Agent on Windows 2003 R2
Title: Message Title Rob Reynolds commented on PUP-4925 Re: Puppet Agent - Failure to Upgrade Agent on Windows 2003 R2 I think Windows Installer is now ruled out. I attached https://tickets.puppetlabs.com/secure/attachment/21987/StockWin2008SP1.png which shows a stock Windows 2008 SP1 install with Windows Installer 4.0.0.6001.0 not experiencing any issues. I believe we determined that we can upgrade a Windows 2003 Windows Installer to 4.5 and still experience the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4925) Puppet Agent - Failure to Upgrade Agent on Windows 2003 R2
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-4925 Puppet Agent - Failure to Upgrade Agent on Windows 2003 R2 Change By: Rob Reynolds Attachment: Win2003_UpgradedWindowsInstaller_Failure.png Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4935) $HOME directory of the Puppet user is writable
Title: Message Title Julien Pivotto created an issue Puppet / PUP-4935 $HOME directory of the Puppet user is writable Issue Type: Bug Affects Versions: puppet-agent 1.2.2 Assignee: Julien Pivotto Components: Platform, Puppet Server Created: 2015/07/27 12:40 PM Environment: Centos 7 Priority: Normal Reporter: Julien Pivotto rpm -q --scripts puppetserver # Add puppet user
Jira (PUP-4925) Puppet Agent - Failure to Upgrade Agent on Windows 2003 R2
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-4925 Puppet Agent - Failure to Upgrade Agent on Windows 2003 R2 Change By: Rob Reynolds Attachment: StockWin2008SP1.png Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1114) Modify acceptance setup to install PE-only agents
Title: Message Title Josh Cooper updated an issue Facter / FACT-1114 Modify acceptance setup to install PE-only agents Change By: Josh Cooper Summary: addpre-suitefor Modify acceptance testsagainst setuptoinstall PE-only platforms agents Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1150) Don't pick scope:link over scope:global IP addresses
Title: Message Title Josh Cooper updated an issue Facter / FACT-1150 Don't pick scope:link over scope:global IP addresses Change By: Josh Cooper Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4757) Update pre-suites to install puppet-agent on pe platforms
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4757 Update pre-suites to install puppet-agent on pe platforms Change By: Josh Cooper Fix Version/s: PUP4.2.2 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1114) add pre-suite for acceptance tests against PE-only platforms
Title: Message Title Josh Cooper updated an issue Facter / FACT-1114 add pre-suite for acceptance tests against PE-only platforms Change By: Josh Cooper Fix Version/s: FACT3.0.3 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1150) Don't pick scope:link over scope:global IP addresses
Title: Message Title Daniele Sluijters commented on FACT-1150 Re: Don't pick scope:link over scope:global IP addresses To clarify, this is what ip a s looks like 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 04:01:5f:2f:c3:01 brd ff:ff:ff:ff:ff:ff inet 178.62.178.58/18 brd 178.62.191.255 scope global eth0
Jira (PUP-4936) Add smf service files for puppet
Title: Message Title Matthaus Owens created an issue Puppet / PUP-4936 Add smf service files for puppet Issue Type: Improvement Assignee: Matthaus Owens Created: 2015/07/27 1:37 PM Priority: Normal Reporter: Matthaus Owens Adding solaris 10 support to puppet means being able to define the puppet service on solaris 10. There are currently smf files for puppet, but they are specific to opencsw and haven't been updated in quite some time. We'll want to bring over the smf files from PE and update them to new paths. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (FACT-1150) Don't pick scope:link over scope:global IP addresses
Title: Message Title
Daniele Sluijters commented on FACT-1150
Re: Don't pick scope:link over scope:global IP addresses
Looking at https://github.com/puppetlabs/facter/commit/4f813e102d8b144f8c90517a5475853dd108d97f this should already be the case but it doesn't appear to be working.
root@EU1:~# facter --version
3.0.2 (commit 5dc120fa9db4c19150466b1bbd1d0cf42c87c6bd)
root@EU1:~# facter networking
{
fqdn = EU1,
hostname = EU1,
interfaces = {
eth0 = {
ip = 178.62.178.58,
Jira (FACT-1150) Don't pick scope:link over scope:global IP addresses
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-1150 Don't pick scope:link over scope:global IP addresses Change By: Peter Huene Assignee: PeterHuene Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1150) Don't pick scope:link over scope:global IP addresses
Title: Message Title Peter Huene updated an issue Facter / FACT-1150 Don't pick scope:link over scope:global IP addresses Change By: Peter Huene Sprint: Client2015-08-19 Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1150) Don't pick scope:link over scope:global IP addresses
Title: Message Title Peter Huene updated an issue Facter / FACT-1150 Don't pick scope:link over scope:global IP addresses Change By: Peter Huene Fix Version/s: FACT3.0.3 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4924) Puppet Windows - Upgrading from 3.7.5 causes Ruby.exe/Rubyw.exe to go missing
Title: Message Title Ryan Gard updated an issue Puppet / PUP-4924 Puppet Windows - Upgrading from 3.7.5 causes Ruby.exe/Rubyw.exe to go missing Change By: Ryan Gard QA Risk Assessment: Medium QA Contact: RyanGard QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1823) Move should be deactivated logic from process-command! down to deactivate-node!
Title: Message Title Rob Browning created an issue PuppetDB / PDB-1823 Move should be deactivated logic from process-command! down to deactivate-node! Issue Type: Improvement Assignee: Unassigned Created: 2015/07/27 3:25 PM Priority: Normal Reporter: Rob Browning Perhaps storage's deactivate-node! command (or some new wrapper) should centralize the deactivation logic instead of having commands/process-command! perform part of the evaluation (looking for any newer records for the certname) and deactivate-node! handle the rest (checking the producer_timestamp). Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4890) Add catalog_version to catalog
Title: Message Title J.D. Welch commented on PUP-4890 Re: Add catalog_version to catalog I'm on board with catalog_id. Or maybe catalog-id; I'm not sure if this is a hype or underscore thing. Either way, I think that makes more sense than 'version' Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1147) Interfaces with multiple IPs are not facted correctly
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-1147 Interfaces with multiple IPs are not facted correctly Change By: Peter Huene Affects Version/s: FACT3.0.2 Assignee: PeterHuene Scrum Team: ClientPlatform Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1140) Facter should translate invalid bytes in DMI data to something representable in UTF-8
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1140 Facter should translate invalid bytes in DMI data to something representable in UTF-8 Change By: Michael Smith Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4891) Add catalog_id to report
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-4891
Add catalog_id to report
Change By:
Josh Cooper
Adda{{ catalog_version catalog_id }}to{{Puppet::Transaction::Report}}whichisserializedoverthewire.Alsoupdatethereportschemaandapidocs.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-4894) Send catalog_id with file_content and file_metadata requests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4894 Send catalog_id with file_content and file_metadata requests Change By: Josh Cooper Modifytheclienttosendits catalog_version catalog_id asanHTTPqueryparameterwhenmakingfile_metadata,file_metadatas,andfile_contentrequests,likeitdoeswiththeenvironment. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1136) Move Ruby API to Leatherman
Title: Message Title Michael Smith commented on FACT-1136 Re: Move Ruby API to Leatherman Failed CI at https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/view/Master/view/Facter/job/platform_aio-facter_pkg-build_master/BUILD_TARGET=el-6-x86_64,SLAVE_LABEL=beaker/102/. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4894) Send catalog_id with file_content and file_metadata requests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4894 Send catalog_id with file_content and file_metadata requests Change By: Josh Cooper Summary: Send catalog_version catalog_id withfile_contentandfile_metadatarequests Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4891) Add catalog_id to report
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4891 Add catalog_id to report Change By: Josh Cooper Summary: Add catalog_version catalog_id toreport Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4893) Update configurer to send catalog_metadata request
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-4893
Update configurer to send catalog_metadata request
Change By:
Josh Cooper
Theconfigurershouldbemodifiedtoloaditscurrent{{catalog_metadata}},extractthe{{ catalog_version catalog_id }}.Aftersendingitsnoderequestandbeforepluginsync,theconfigurershouldsendacatalog_metadatarequest(find)sendingalongits{{ catalog_version catalog_id }}.Theconfigurershouldprocesstheresponseandeitherskiptherun,useitscachedcatalog,ordoanormalrun.Iftoldtodoanormalrun,savethenewcatalog_metadata.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-4892) Create catalog_metadata model and JSON and REST terminii
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-4892
Create catalog_metadata model and JSON and REST terminii
Change By:
Josh Cooper
Createacatalog_metadatamodelcontaining{{ catalog_version catalog_id }}andaJSONandRESTterminiiforserializinglocallyandremotely.Addcatalog_metadatatoschemaandapidocs.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-4900) Fail compilation if client catalog version doesn't match
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-4900
Fail compilation if client catalog version doesn't match
Change By:
Josh Cooper
The{{compiler}}catalogterminusshouldfailthecompilation,iftheclientrequestsa catalogversion {{catalog_id}} thatdoesnotmatchtheserver's version {{catalog_id}} .Thiscanhappenifthecatalog_metadatasaystouseversionA,butbeforetheagentrequeststhecatalog,newcodeispromoted,andthecompilerwillhavenowaytoproduceacatalogforversionA.Inthefuture,theservercouldtelltheagenttoretry,sostarttherunover,sendcatalog_metadatarequest,etc.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-4445) Add support to TLS 1.2 connections to Puppet Forge when SSLv3 is blocked in a corporate network
Title: Message Title Christian Becker commented on PUP-4445 Re: Add support to TLS 1.2 connections to Puppet Forge when SSLv3 is blocked in a corporate network Are there any news on this? I can confirm the issue on CentOS 7 with puppet-agent-1.2.2-1.el7.x86_64 of the PC1 repository. Master config: ssl_protocols TLSv1.2; ssl_ciphers EECDH+AESGCM:EDH+AESGCM:EECDH:!EDH:!MD5:!RC4:!LOW:!MEDIUM:!CAMELLIA:!ECDSA:!DES:!DSS:!3DES:!NULL; which is working fine for puppet 3, but breaking with the new agent package. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4937) puppet agent runs report time spent applying catalogue but omit total time spent
Title: Message Title Geoff Williams created an issue Puppet / PUP-4937 puppet agent runs report time spent applying catalogue but omit total time spent Issue Type: Bug Affects Versions: PUP 4.2.1 Assignee: Unassigned Components: AIO Created: 2015/07/27 6:32 PM Environment: RHEL 7 Priority: Normal Reporter: Geoff Williams Overview Puppet agent reports time spent applying the catalogue but does not report the total time spent running the command (or compiling the catalogue). Problems this causes Sometimes external factors such as https://tickets.puppetlabs.com/browse/PE-11243 cause catalogue compilation to take several minutes but the agent reports that it has only spent a few seconds running. This initially seems to indicate that the VM running puppet is losing time, possibly due to contention in the hypervisor system. This wastes time
Jira (PUP-4890) Add catalog_id to catalog
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4890 Add catalog_id to catalog Change By: Josh Cooper Summary: Add catalog_version catalog_id tocatalog Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4890) Add catalog_id to catalog
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-4890
Add catalog_id to catalog
Change By:
Josh Cooper
Adda{{ catalog_version catalog_id }}to{{Puppet::Resource::Catalog}}whichisserializedoverthewire.Alsoupdatethecatalogschemaandapidocs.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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-1136) Move Ruby API to Leatherman
Title: Message Title Michael Smith commented on FACT-1136 Re: Move Ruby API to Leatherman Also looks like we missed catching some warnings that were changed to exceptions. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider Another detail that we need to sort out is the Hiera qualified lookup using dot-separated names. Do we want two types of qualified names? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4889) Ankeny Direct Puppet
Title: Message Title Michael Stahnke commented on PUP-4889 Re: Ankeny Direct Puppet Excuse my ignorance here, but are there any new packages coming out of this work? Sometimes a terminus is a new package and sometimes it's not. I'm not clear if we'll need one. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4889) Ankeny Direct Puppet
Title: Message Title Kylo Ginsberg commented on PUP-4889 Re: Ankeny Direct Puppet Michael Stahnke no new packages. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-1786) Spike - Exported Resources for HA
Title: Message Title Luke Kanies commented on PDB-1786 Re: Spike - Exported Resources for HA It's also worth noting that we're relying on exported resources for the app mgmt work, and we're hoping to change some aspects of the behavior to better fit that use case. As you work on this, make sure you talk to Ryan Coleman. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider And you're OK with 'scope' being the default? Keeping it that way will be more backward compatible but having 'lookup' be the default seems more logical. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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.
