Jira (PUP-6798) Ensuring latest does not use upgrade command in DNF
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6798 Ensuring latest does not use upgrade command in DNF Change By: Geoff Nichols Release Notes Summary: Fixed an issue where ensuring latest did not use the upgrade command in DNF. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6798) Ensuring latest does not use upgrade command in DNF
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6798 Ensuring latest does not use upgrade command in DNF Change By: Geoff Nichols Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-518) Document how to make hiera_xxx functions delegate to lookup()
Title: Message Title Henrik Lindberg commented on HI-518 Re: Document how to make hiera_xxx functions delegate to lookup() No technical reasons except "we changed it, it is different, it may cause unknown things to occur" even if we believe the risk is low. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3107) new-command-schema validation prevents PDB/NewRelic integration
Title: Message Title Susan McNerney commented on PDB-3107 Re: new-command-schema validation prevents PDB/NewRelic integration Will they be able to take Everett? Or are they going to get on Davis LTS and parking for a while? We have a Davis Z going out in February, or Everett in December. Let me know if you want to propose for Davis Z, I can facilitate that. If you feel Everett is ok, then they just need to get the bug into a PE build by the Everett deadline, which is Nov 2. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-518) Document how to make hiera_xxx functions delegate to lookup()
Title: Message Title Nick Walker commented on HI-518 Re: Document how to make hiera_xxx functions delegate to lookup() I tend to agree with Reid's analysis. I suspect that users would be okay with switching their own modules to use lookup although even sometimes that can be hard but when you use a community module that uses a hiera function call you have less recourse and you'd prefer that it just work. Is there a technical reason to not allow lookup to defer to hiera? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-518) Document how to make hiera_xxx functions delegate to lookup()
Title: Message Title Reid Vandewiele commented on HI-518 Re: Document how to make hiera_xxx functions delegate to lookup() Henrik Lindberg ah; I'd glossed over that comment. Eric Sorenson lindsey.smith I think that realistically, to enable users to adopt lookup() we need to make it ridiculously easy for them to start using it. The hiera() incompatibility makes it ridiculously hard. This workaround is a good workaround, if you know about it, but it's still a workaround. Needing a workaround implies a problem. Finding in the documentation a magic incantation to put in their site-specific code to make it work is not ridiculously easy, and does not enable our users to adopt lookup(). We should fix the problem so we can start telling people to use lookup() instead of hiera(), with ease and confidence. Eric Sorenson would you consider re-visiting your docs-only decision on this ticket? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-518) Document how to make hiera_xxx functions delegate to lookup()
Title: Message Title Henrik Lindberg commented on HI-518 Re: Document how to make hiera_xxx functions delegate to lookup() Reid Vandewiele See eric 0's comment earlier about just using the to be documented workaround instead of making any changes to the existing functions. Are you saying that is not enough? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1441) Add "virtualization" fact that identifies AWS, Azure, etc
Title: Message Title
Scott McClellan updated an issue
Facter / FACT-1441
Add "virtualization" fact that identifies AWS, Azure, etc
Change By:
Scott McClellan
We should add a fact that determines whether or not a VM is running in Azure.Fact structure:{code}"virtualization": { "hypervisor": "kvm", "cloud": {"provider": "azure" }}{code}Note that {{hypervisor}} above is the same as the {{virtual}} fact.**How to calculate whether a machine is running in Azure***Windows* {code}$systemEnclosure = Get-WmiObject -class Win32_SystemEnclosure -namespace root\CIMV2$computerSystemProduct = Get-WmiObject -class Win32_ComputerSystemProduct -namespace root\CIMV2'ChassisAssetTag: "{0}"' -f $systemEnclosure.SMBIOSAssetTag{code}*Expected Results*{code}"7783-7084-3265-9085-8269-3286-77"{code}*Linux*{code}sudo dmidecode | grep "Asset Tag: 7783-7084-3265-9085-8269-3286-77" /var/lib/dhcp/dhclient.eth0.leases {code}*Expected Results*{code}Asset Tag: 7783-7084-3265-9085-8269-3286-77{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6612) Scope effort for i18n string externalization
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6612 Scope effort for i18n string externalization Change By: Geoff Nichols Sprint: AP Grooming 2016-11-16 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6612) Scope effort for i18n string externalization
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6612 Scope effort for i18n string externalization Change By: Geoff Nichols Acceptance Criteria: - Automateable reporting of number and types (complexity) of strings by library and section in Puppet codebase. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6612) Scope effort for i18n string externalization
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6612 Scope effort for i18n string externalization Change By: Geoff Nichols Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6847) The network_device configuration parser should not accept trailing whitespace
Title: Message Title Adam Bottchen moved an issue Puppet / PUP-6847 The network_device configuration parser should not accept trailing whitespace Change By: Adam Bottchen Affects Version/s: puppet-agent 1.5.3 Affects Version/s: PUP 4.5.3 Workflow: Release Engineering Scrum Teams Workflow Key: PA PUP - 664 6847 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet
Jira (PUP-6612) Scope effort for i18n string externalization
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6612 Scope effort for i18n string externalization Change By: Geoff Nichols Categorize strings in Puppet that require externalization for i18n, e.g. with aautomated tool that can be expanded later to check PRs and integrated with CIfor all Ruby projects. Categorize strings as basic static strings, simple formattedstrings, strings requiring pluralization and/or additional translation context, complexcases that may require manual intervention, and strings that should not betranslated.Investigate removing line numbers from the POT file to reduce churn. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-518) Document how to make hiera_xxx functions delegate to lookup()
Title: Message Title Reid Vandewiele commented on HI-518 Re: Document how to make hiera_xxx functions delegate to lookup() Henrik Lindberg given that this ticket has been converted to docs, is there now a ticket somewhere else to track making the hiera() functions relay to lookup() rather than failing outright as they do today? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6764) Add PO files with translated strings to Puppet repo
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6764 Add PO files with translated strings to Puppet repo Change By: Geoff Nichols Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6764) Add PO files with translated strings to Puppet repo
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6764 Add PO files with translated strings to Puppet repo Change By: Geoff Nichols Sprint: AP Grooming 2016-11-30 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6764) Add PO files with translated strings to Puppet repo
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6764 Add PO files with translated strings to Puppet repo Change By: Geoff Nichols Summary: Make CI job to add Add PO files with translated strings to Puppet repo Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6764) Make CI job to add PO files with translated strings to repo
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6764 Make CI job to add PO files with translated strings to repo Change By: Geoff Nichols This is a placeholder for the effort to implement, review, or sign off on the way we put translated strings into Puppet codebase. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6764) Make CI job to add PO files with translated strings to repo
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6764 Make CI job to add PO files with translated strings to repo Change By: Geoff Nichols Summary: Make CI job to add PO files with translated strings to repo Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6763) Make CI job to update POT file
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6763 Make CI job to update POT file Change By: Geoff Nichols Sprint: AP Grooming 2016-11-30 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6763) Make CI job to update POT file
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6763 Make CI job to update POT file Change By: Geoff Nichols Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1510) Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows
Title: Message Title Rob Reynolds updated an issue Facter / FACT-1510 Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows Change By: Rob Reynolds CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1510) Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows
Title: Message Title Rob Reynolds updated an issue Facter / FACT-1510 Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows FACT-1276 is where this was fixed, but it appears broken again. Change By: Rob Reynolds Team: Agent & Platform Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1510) Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows
Title: Message Title Rob Reynolds updated an issue Facter / FACT-1510 Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows Change By: Rob Reynolds Labels: testing vagrant windows Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2908) Resolve conflict between i18n and structured-logging
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-2908 Resolve conflict between i18n and structured-logging Change By: Rob Browning Assignee: Rob Browning Story Points: 3 Sprint: SE 2016-11-02 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6758) Fix pkgng provider
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-6758 Fix pkgng provider Change By: Adrien Thebo Assignee: Kylo Ginsberg Adrien Thebo Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3659) Puppet on Windows - Shortcut to Puppet confdir in the Start Menu Folder
Title: Message Title Carthik Sharma commented on PUP-3659 Re: Puppet on Windows - Shortcut to Puppet confdir in the Start Menu Folder Thanks for the note Geoff Nichols, and that seems like a good way to go about it. Cheers. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3673) type validation ignores tags when catalog is being converted to RAL format (on Windows)
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3673 type validation ignores tags when catalog is being converted to RAL format (on Windows) Change By: Geoff Nichols Labels: needs_repro support Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3659) Puppet on Windows - Shortcut to Puppet confdir in the Start Menu Folder
Title: Message Title Geoff Nichols commented on PUP-3659 Re: Puppet on Windows - Shortcut to Puppet confdir in the Start Menu Folder This seems like a good idea, but we haven't heard many other requests for this feature. The CLI feature puppet config set should provide most of the equivalent functionality. We'll close this this for now. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1525) Swap facts are incorrect on AIX in Facter 3
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1525 Swap facts are incorrect on AIX in Facter 3 Change By: Geoff Nichols Sprint: AP Triage Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title
Maggie Dreyer updated an issue
Facter / FACT-1356
External facts should be able to return structured data
Change By:
Maggie Dreyer
Release Notes Summary:
This allows executable external facts to return data in YAML or JSON format, and Facter will correctly parse it into a structured fact. If the returned value is not YAML, Facter will fall back to parsing it as a {{key=value}} pair, and only fail to resolve if the output is none of these formats.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Susan McNerney commented on PUP-6789 Re: Prefer but don't require capabilities matching the node environment Zach Reichert Do you have an estimate of when you'll be able to complete this? Tracking for the HA overall effort, and this is our last dependency. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1526) PA (stable) Facter Tests Failing with Unknown Agent Platform (Windows-2016)
Title: Message Title Maggie Dreyer commented on FACT-1526 Re: PA (stable) Facter Tests Failing with Unknown Agent Platform (Windows-2016) This is only an issue because https://github.com/puppetlabs/puppet-agent/pull/886 has not yet been merged. This test has been updated on master to support Windows 2016. Going to close as fixed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-771) capturing ec2 userdata as a fact may be a security risk
Title: Message Title Kevin Jones assigned an issue to Gareth Rushgrove Facter / FACT-771 capturing ec2 userdata as a fact may be a security risk Change By: Kevin Jones Assignee: Eric Sorenson Gareth Rushgrove Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6846) Obscure error messages caused by error in metadata.json of a module.
Title: Message Title Tiago TT created an issue Puppet / PUP-6846 Obscure error messages caused by error in metadata.json of a module. Issue Type: Bug Affects Versions: PUP 4.3.1 Assignee: Unassigned Components: Modules Created: 2016/10/27 7:13 AM Labels: module metadata Priority: Normal Reporter: Tiago TT Context Introducing a new module in an existing and working puppet environment. Symptoms Running puppet agent fails with the following errors: # puppet agent --test
Jira (PUP-6846) Obscure error messages caused by error in metadata.json of a module.
Title: Message Title
Tiago TT updated an issue
Puppet / PUP-6846
Obscure error messages caused by error in metadata.json of a module.
Change By:
Tiago TT
h2. ContextIntroducing a new module in an existing and working puppet environment.h2. SymptomsRunning puppet agent fails with the following errors:{code}# puppet agent --testInfo: Using configured environment 'test'Info: Retrieving pluginfactsError: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Error 400 on SERVER: string not matchedError: /File[/opt/puppetlabs/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: Error 400 on SERVER: string not matchedInfo: Retrieving pluginError: /File[/opt/puppetlabs/puppet/cache/lib]: Failed to generate additional resources using 'eval_generate': Error 400 on SERVER: string not matchedError: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: Error 400 on SERVER: string not matchedInfo: Loading factsError: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Function Call, string not matched at /etc/puppetlabs/code/environments/test/site.pp:8:1 on node testing.example.comWarning: Not using cache on failed catalogError: Could not retrieve catalog; skipping run{code}Error messages on the server log:{code}# tail -f /var/log/puppetlabs/puppetserver/puppetserver.log...2016-10-27 12:17:07,532 ERROR [qtp350972994-25856] [puppet-server] Puppet string not matchedorg/jruby/RubyString.java:3912:in `[]='/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/module.rb:158:in `load_metadata'org/jruby/RubyArray.java:1613:in `each'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/module.rb:157:in `load_metadata'org/jruby/RubyArray.java:1613:in `each'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/module.rb:151:in `load_metadata'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/module.rb:68:in `initialize'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/node/environment.rb:292:in `modules'org/jruby/RubyArray.java:2407:in `collect'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/node/environment.rb:290:in `modules'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/node/environment.rb:247:in `module'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/file_serving/mount/modules.rb:10:in `find'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/file_server.rb:29:in `find'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:in `find'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:134:in `do_find'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:48:in `call'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:240:in `override'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:47:in `call'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:82:in `process'org/jruby/RubyArray.java:1613:in `each'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:81:in
Jira (FACT-1526) PA (stable) Facter Tests Failing with Unknown Agent Platform (Windows-2016)
Title: Message Title John O'Connor created an issue Facter / FACT-1526 PA (stable) Facter Tests Failing with Unknown Agent Platform (Windows-2016) Issue Type: CI Blocker Assignee: Unassigned Components: Windows Created: 2016/10/27 3:50 AM Priority: Normal Reporter: John O'Connor Jenkins->puppet-agent (stable) Suite Pipeline Step 5 – Facter Tests->beaker,windows2016-64a & windows2016-6432a are failing with the following error: 03:26:04 Warning: tests/facts/ubuntu.rb skipped in 0.00 seconds 03:26:04 Begin tests/facts/windows.rb 03:26:04
