Jira (HI-484) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title Craig Dunn commented on HI-484 Re: parse_string doesnt interpolate %{key} with Puppet 4.0 Thomas Hallgren You appear to be correct here scope['key'] returns true Puppet 3 Debug: Runtime environment: puppet_version=3.8.4, ruby_version=2.0.0, run_mode=user, default_encoding=UTF-8 Debug: hiera(): Scope contains key? true Debug: hiera(): unparsed: foo bar % {key} to parsed: foo bar test::my_key Puppet 4 Debug: Runtime environment: puppet_version=4.0.0, ruby_version=2.0.0, run_mode=user, default_encoding=UTF-8 Debug: hiera(): Scope contains key? true Debug: hiera(): unparsed: foo bar %{key} to parsed: foo bar Hiera CLI DEBUG: 2015-12-04 08:37:30 +0100: Scope contains key? false DEBUG: 2015-12-04 08:37:30 +0100: unparsed: foo bar % {key} to parsed: foo bar my_key This supports your theory, assuming the scope['key'] has always returned true, but in Puppet 3.x this was considered an non-valid value and therefore ignored and the extra_data value used, but in Puppet 4.x because it's considered legal it's being interpolated into the hash This lead me to do a bit more digging - the problem is not related soley to interpolating %{key} . For some reason, `scope.include?('anything')` always returns true, therefore values from the extra_hash are never interpolated thus breaking this option entirely. scope.include?('askdjhajh') => true Hiera::Scope in puppet//lib/hiera/scope.rb has the following method def include?(key) if key == CALLING_CLASS or key == CALLING_MODULE true else @real.lookupvar(key) != "" end end If real.lookupvar returns nil then the method will return true since nil != "" - this is as far as I've got with it This has been reported by two different users of hiera-mysql and hiera-http so far, so it's clearly a behaviour that people need. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (HI-484) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title Thomas Hallgren commented on HI-484 Re: parse_string doesnt interpolate %{key} with Puppet 4.0 Craig Dunn, thanks for confirming my theory and also finding where the problem is. Do you want to submit a PR that fixes this or should I? Either way is find by me but I don't want to steal well earned credit without asking Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-484) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title Craig Dunn commented on HI-484 Re: parse_string doesnt interpolate %{key} with Puppet 4.0 Thomas Hallgren I'm happy to do the PR - is it fair to say that a nil value in the scope should not be considered valid by hiera even though it's valid within Puppet 4.0. eg: Return true unless nil or ""? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-484) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title Thomas Hallgren commented on HI-484 Re: parse_string doesnt interpolate %{key} with Puppet 4.0 I think you should use @real.exist?(key) here. The documentation says "Returns true if the variable of the given name is set to any value (including nil)" which I think is exactly what we want. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-484) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title Craig Dunn commented on HI-484 Re: parse_string doesnt interpolate %{key} with Puppet 4.0 Yep - just tested with exist? and that appears to behave better - will submit a PR against it now. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1170) Facter shows different value on fact virtual
Title: Message Title Florian Faltermeier updated an issue Facter / FACT-1170 Facter shows different value on fact virtual Change By: Florian Faltermeier Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-354) virt result depends on root authority
Title: Message Title Florian Faltermeier commented on FACT-354 Re: virt result depends on root authority Hello Johan, see also: https://tickets.puppetlabs.com/browse/FACT-1170 Kind regards, Florian Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-484) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title Craig Dunn commented on HI-484 Re: parse_string doesnt interpolate %{key} with Puppet 4.0 Thomas Hallgren submitted, https://github.com/puppetlabs/puppet/pull/4482 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5502) lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml
Title: Message Title Thomas Hallgren commented on PUP-5502 Re: lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml I'm able to reproduce the problem partly, but I don't get (). Instead, the full path of the file is reported correctly. This is a bit odd, given that the file is found and the error stems from the YAML.load_file(@config_path) command. I don't understand how it can find the file and then report that it's unknown. Henrik Lindberg, what does your setup look like? Do you execute the lookup command using CLI? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5502) lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml
Title: Message Title Henrik Lindberg commented on PUP-5502 Re: lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml This is from a user - I did not run this myself. We had the ticket in triage to follow up if this was a problem or not. (I know I should have pasted a link to where this was reported from - now I cannot find it). I did find this though - one occurrence of the problem reported: https://ask.puppetlabs.com/question/16614/error-400-on-server-error-from-databinding-hiera-while-looking-up-puppet_enterprisecertificate_authority_port-unknown-could-not-found-expected-while/ Similar: https://ask.puppetlabs.com/question/11000/does-puppet-provide-a-validationsyntax-checker-for-hiera/ Looks like the is produced in the error message shown when an agent attempts to get a catalog. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5061) Always restore full trusted information from store
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-5061 Always restore full trusted information from store Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1170) Facter shows different value on fact virtual
Title: Message Title Florian Faltermeier commented on FACT-1170 Re: Facter shows different value on fact virtual https://tickets.puppetlabs.com/browse/FACT-354 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5561) Put accurate information about autoloading in spec for puppet functions
Title: Message Title Henrik Lindberg assigned an issue to Nicholas Fagerlund Puppet / PUP-5561 Put accurate information about autoloading in spec for puppet functions Change By: Henrik Lindberg Assignee: Nicholas Fagerlund Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5561) Put accurate information about autoloading in spec for puppet functions
Title: Message Title Henrik Lindberg commented on PUP-5561 Re: Put accurate information about autoloading in spec for puppet functions I made a PR with the changes to the spec: https://github.com/puppetlabs/puppet-specifications/pull/59 - ping Nicholas Fagerlund Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5578) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title Thomas Hallgren moved an issue Puppet / PUP-5578 parse_string doesnt interpolate %{key} with Puppet 4.0 Change By: Thomas Hallgren Key: HI PUP - 484 5578 Project: Hiera Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5578) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title Thomas Hallgren commented on PUP-5578 Re: parse_string doesnt interpolate %{key} with Puppet 4.0 I moved this to Puppet since the error is in the Puppet code base. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5509) No error context when a non-numeric index is used on a string
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5509 No error context when a non-numeric index is used on a string Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5502) lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml
Title: Message Title Henrik Lindberg commented on PUP-5502 Re: lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml Merged to master at: 9ccd4dd (Note that target was 4.3.2, so should have gone to stable). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5511) puppet lookup command rejects `--merge first`
Title: Message Title Sean Griffin assigned an issue to Steve Barlow Puppet / PUP-5511 puppet lookup command rejects `--merge first` Change By: Sean Griffin Assignee: Steve Barlow Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5511) puppet lookup command rejects `--merge first`
Title: Message Title Sean Griffin commented on PUP-5511 Re: puppet lookup command rejects `--merge first` Verified in centos-7-x86_64. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5511) puppet lookup command rejects `--merge first`
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5511 puppet lookup command rejects `--merge first` Change By: Sean Griffin QA Risk Assessment: Medium QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5522) Puppet node does not keep attributes consistent with parameters
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-5522 Puppet node does not keep attributes consistent with parameters Change By: Sean Griffin Assignee: qa Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5522) Puppet node does not keep attributes consistent with parameters
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5522 Puppet node does not keep attributes consistent with parameters Change By: Sean Griffin QA Risk Probability Reason: Already a workaround in place in puppet preview, user won't see this problem. QA Risk Assessment: Low QA Risk Severity Reason: In the unlikely event of failure, puppet preview will error. No system risk. QA Risk Probability: Low QA Risk Severity: Low QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5578) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title Thomas Hallgren commented on PUP-5578 Re: parse_string doesnt interpolate %{key} with Puppet 4.0 Merged to master at 0ba6a33. I will cherry-pick this over to stable as well. Thank you Craig Dunn, for the contribution and effort. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5578) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title Thomas Hallgren commented on PUP-5578 Re: parse_string doesnt interpolate %{key} with Puppet 4.0 Cherry picked to stable at 37848f5. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5522) Puppet node does not keep attributes consistent with parameters
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-5522 Puppet node does not keep attributes consistent with parameters Change By: Sean Griffin Assignee: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5578) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5578 parse_string doesnt interpolate %{key} with Puppet 4.0 Change By: Kylo Ginsberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5578) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5578 parse_string doesnt interpolate %{key} with Puppet 4.0 Change By: Kylo Ginsberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5578) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5578 parse_string doesnt interpolate %{key} with Puppet 4.0 Change By: Kylo Ginsberg Sprint: Language 2015-12-16 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5547) Environment is evicted many times during compile
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-5547 Environment is evicted many times during compile Change By: Sean Griffin Assignee: qa Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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) Direct Puppet Initiative
Title: Message Title J.D. Welch commented on PUP-4889 Re: Direct Puppet Initiative Is there anything specific needed from UX for Burnside Direct Puppet? Messaging, new interaction models, new configuration settings, etc.? I'm happy to review and contribute as needed. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2228) Create "examples repo" and tie that into PDB CLI manpage creation
Title: Message Title J.D. Welch assigned an issue to J.D. Welch PuppetDB / PDB-2228 Create "examples repo" and tie that into PDB CLI manpage creation Change By: J.D. Welch Assignee: J.D. Welch Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5578) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5578 parse_string doesnt interpolate %{key} with Puppet 4.0 Change By: Henrik Lindberg Fix Version/s: PUP 4.3.2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2237) Specify structure and interaction of PDB CLI
Title: Message Title J.D. Welch created an issue PuppetDB / PDB-2237 Specify structure and interaction of PDB CLI Issue Type: Task Assignee: J.D. Welch Components: UX Created: 2015/12/04 10:06 AM Priority: Normal Reporter: J.D. Welch Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
Jira (PUP-5509) No error context when a non-numeric index is used on a string
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5509 No error context when a non-numeric index is used on a string Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5509) No error context when a non-numeric index is used on a string
Title: Message Title Henrik Lindberg commented on PUP-5509 Re: No error context when a non-numeric index is used on a string Merged to 3.x: 71ce7fd Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5509) No error context when a non-numeric index is used on a string
Title: Message Title Henrik Lindberg commented on PUP-5509 Re: No error context when a non-numeric index is used on a string And merged to stable and master. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5502) lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml
Title: Message Title Henrik Lindberg commented on PUP-5502 Re: lookup adapter "lookup_global" produces bad error message for faulty hiera.yaml Now cherry picked to stable. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5561) Put accurate information about autoloading in spec for puppet functions
Title: Message Title Nicholas Fagerlund assigned an issue to Henrik Lindberg Puppet / PUP-5561 Put accurate information about autoloading in spec for puppet functions Change By: Nicholas Fagerlund Assignee: Nicholas Fagerlund Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5561) Put accurate information about autoloading in spec for puppet functions
Title: Message Title Nicholas Fagerlund commented on PUP-5561 Re: Put accurate information about autoloading in spec for puppet functions I commented about what was missing or confusing in the PR. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2238) ERROR: duplicate key value violates unique constraint
Title: Message Title Erik Grinaker created an issue PuppetDB / PDB-2238 ERROR: duplicate key value violates unique constraint Issue Type: Bug Affects Versions: PDB 3.2.2 Assignee: Unassigned Created: 2015/12/04 11:44 AM Environment: Ubuntu 14.04.3 LTS Priority: Major Reporter: Erik Grinaker After upgrading from PuppetDB 2.3.7 to PuppetDB 3.2.2, I see the following errors in the PuppetDB log: {{Dec 4 20:11:32: [5dc7dc96-98ab-4a8b-8598-005f8ed197a7] [store report] puppet v4.3.1 - hydrogen.kvantel.no Dec 4 20:11:52: [204fc471-55e1-4b60-82b7-83a14429d270] [replace catalog] Retrying after attempt 4, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "resource_params_cache_pkey" Detail: Key (resource)=()MA\242\314\277\211e\274"\204\325e'`A\336\202\245\220) already exists. Dec 4 20:11:56: [4d556974-1838-404a-b995-7647aa462d0a] [replace facts] Retrying after attempt 4, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "fact_values_value_hash_key" Detail: Key (value_hash)=(\267\260\213w\013'~\311\004,"- \026u\030\231\3068\005) already exists. Dec 4 20:12:14: [fe8ebca2-8243-41c9-bd05-fd6ee9f5a84b] [replace facts] Retrying after attempt 5, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violat
Jira (PDB-2238) ERROR: duplicate key value violates unique constraint
Title: Message Title Erik Grinaker updated an issue PuppetDB / PDB-2238 ERROR: duplicate key value violates unique constraint Change By: Erik Grinaker After upgrading from PuppetDB 2.3.7 to PuppetDB 3.2.2, I see the following errors in the PuppetDB log:{{Dec 4 20:11:32: [5dc7dc96-98ab-4a8b-8598-005f8ed197a7] [store report] puppet v4.3.1 - hydrogen.kvantel.noDec 4 20:11:52: [204fc471-55e1-4b60-82b7-83a14429d270] [replace catalog] Retrying after attempt 4, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "resource_params_cache_pkey" Detail: Key (resource)=()MA\242\314\277\211e\274"\204\325e'`A\336\202\245\220) already exists.Dec 4 20:11:56: [4d556974-1838-404a-b995-7647aa462d0a] [replace facts] Retrying after attempt 4, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "fact_values_value_hash_key" Detail: Key (value_hash)=(\267\260\213w\013'~\311\004,"- \026u\030\231\3068\005) already exists.Dec 4 20:12:14: [fe8ebca2-8243-41c9-bd05-fd6ee9f5a84b] [replace facts] Retrying after attempt 5, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "fact_values_value_hash_key" Detail: Key (value_hash)=(\267\260\213w\013'~\311\004,"- \026u\030\231\3068\005) already exists.Dec 4 20:12:31: [7fb13f08-55bc-4863-b9a0-9481b0614b79] [replace catalog] Retrying after attempt 5, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "resource_params_cache_pkey" Detail: Key (resource)=()MA\242\314\277\211e\274"\204\325e'`A\336\202\245\220) already exists.Dec 4 20:13:20: [e5c87176-a3ab-46b4-b559-c6a8222173f7] [replace facts] Retrying after attempt 6, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "fact_values_value_hash_key" Detail: Key (value_hash)=(\267\260\213w\013'~\311\004,"- \026u\030\231\3068\005) already exists.Dec 4 20:13:36: [744dd9a5-e202-4218-9039-98bacd18a36f] [replace catalog] Retrying after attempt 6, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "resource_params_cache_pkey" Detail: Key (resource)=()MA\242\314\277\211e\274"\204\325e'`A\336\202\245\220) already exists.Dec 4 20:15:11: [f2a1e995-2045-47c8-b838-f66f6f2b0c29] [replace facts] Retrying after attempt 7, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "fact_values_value_hash_key" Detail: Key (value_hash)=(\267\260\213w\013'~\311\004,"- \026u\030\231\3068\005) already exists.Dec 4 20:15:31: [b504ae16-2958-40ff-aea7-3d5b3e0bb2a3] [replace catalog] Retrying after attempt 7, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "resource_params_cache_pkey" Detail: Key (resource)=()MA\242\314\277\211e\274"\204\325e'`A\336\202\245\220) already exists.}}...and so on. I get this on two separate installations at two different companies. It happens even with an empty database (and queue), but then only on the second Puppet run. It also happens with an empty manifest. PuppetServer does not report any errors. I have tried upgrading from PuppetDB 2 to 3 multiple times over the past few months, with multiple PuppetDB 3 versions, and
Jira (PUP-5444) symbolic_modes tests occasionally fail on OSX
Title: Message Title Eric Thompson assigned an issue to qa Puppet / PUP-5444 symbolic_modes tests occasionally fail on OSX Change By: Eric Thompson Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5479) segfault with augeas type when changes attribute is too long
Title: Message Title David Lutterkort commented on PUP-5479 Re: segfault with augeas type when changes attribute is too long I just tried this on a recent 2015.3 rc, and it works there as expected with an error Error: /Stage[main]/Kerberos/Augeas[krb5.config]: Could not evaluate: Saving failed, see debug The issue is that the path in the command set /files/etc/krb5.conf/libdefaults/realms/default_realm PUPPETLABS.VM is incorrect - it has an extra realms; using the command set /files/etc/krb5.conf/libdefaults/default_realm PUPPETLABS.VM works. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5579) Puppet acceptance tests fail trying to stop puppet service
Title: Message Title Matthaus Owens created an issue Puppet / PUP-5579 Puppet acceptance tests fail trying to stop puppet service Issue Type: Bug Assignee: Unassigned Attachments: jenkins_output_log.txt Created: 2015/12/04 1:53 PM Priority: Normal Reporter: Matthaus Owens The puppet server tests failed in one cell (centos 6 64-bit) this morning (http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppet-server_integration-system_no-conditional_full-2.1.x/22/) with an error stopping the puppet service. I don't know if this has been seen before in puppet's acceptance tests. A portion of the log is below, and the full log is attached. Checking the service on the machine returns the following: [root@j7kl5f3ljm8qwoi ~]# service puppet status puppet dead but subsys locked
Jira (PUP-5520) Exclude unsafe Yocto scripts from service init provider
Title: Message Title Rick Sherman commented on PUP-5520 Re: Exclude unsafe Yocto scripts from service init provider Link to pr https://github.com/puppetlabs/puppet/pull/4480 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2238) ERROR: duplicate key value violates unique constraint
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2238 ERROR: duplicate key value violates unique constraint Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2238) ERROR: duplicate key value violates unique constraint
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2238 ERROR: duplicate key value violates unique constraint Change By: Andrew Roetker Scope Change Category: Adopted Scope Change Reason: Bug in last few releases that breaks pdb Story Points: 1 Sprint: PuppetDB 2015-12-16 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2238) ERROR: duplicate key value violates unique constraint
Title: Message Title Andrew Roetker commented on PDB-2238 Re: ERROR: duplicate key value violates unique constraint Erik Grinaker It looks like the issue comes from PuppetDB expecting the `bytea_output` setting to be 'hex' instead of 'escape'. I expect that if you run `show bytea_output;` in a psql session with your PuppetDB database, it will be set to 'escape'. I'm going to create a ticket and get a fix in, but until we get a release out you'll need to have `bytea_output = 'hex'` in your PostgreSQL configuration to run PuppetDB 3.x. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2238) ERROR: duplicate key value violates unique constraint
Title: Message Title Erik Grinaker commented on PDB-2238 Re: ERROR: duplicate key value violates unique constraint Confirmed, we set bytea_output = 'escape' explicitly, for backwards-compatibility, but this may no longer be necessary. I will try to upgrade again tomorrow with bytea_output = 'hex'. Thanks for the tip! Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2239) Use `decode` and `encode` instead of `trim` and `format` for handling bytea conversions
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2239 Use `decode` and `encode` instead of `trim` and `format` for handling bytea conversions Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2239) Use `decode` and `encode` instead of `trim` and `format` for handling bytea conversions
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2239 Use `decode` and `encode` instead of `trim` and `format` for handling bytea conversions Issue Type: Bug Affects Versions: PDB 3.0.0 Assignee: Unassigned Created: 2015/12/04 3:05 PM Fix Versions: PDB 3.2.x Priority: Normal Reporter: Andrew Roetker Currently we use trim and format functions for handling bytea to string conversions in PostgreSQL. This implicitly relies on the PostgreSQL `bytea` output setting being set to its default value `hex` (vs. `escape`). This causes issues in the storage engine where some hashes don't appear to be in the database when they are (when `bytea_output = 'escape'). We should use the `decode(<...>, 'hex')` and `encode(<...>::bytea, 'hex')` Add Comm
Jira (PUP-5566) Spike node definition and presuite improvements for puppet agent components
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5566 Spike node definition and presuite improvements for puppet agent components Change By: Josh Cooper Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5378) acceptance: backport call all parser functions test to 3.x
Title: Message Title Eric Thompson commented on PUP-5378 Re: acceptance: backport call all parser functions test to 3.x Henrik Lindberg or Thomas Hallgren PR attached here, i pinged you in. i can't get the class include functions to find classes in puppet apply run mode, but only in 3.x i'll take another look on monday... Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5444) symbolic_modes tests occasionally fail on OSX
Title: Message Title Kylo Ginsberg commented on PUP-5444 Re: symbolic_modes tests occasionally fail on OSX This is a CI only change, no verification needed. Moving to RfR. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5444) symbolic_modes tests occasionally fail on OSX
Title: Message Title Kylo Ginsberg assigned an issue to Steve Barlow Puppet / PUP-5444 symbolic_modes tests occasionally fail on OSX Change By: Kylo Ginsberg Assignee: Steve Barlow Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5561) Put accurate information about autoloading in spec for puppet functions
Title: Message Title Henrik Lindberg commented on PUP-5561 Re: Put accurate information about autoloading in spec for puppet functions Thanks Nicholas Fagerlund for the review - I posted some follow up questions and comments on the PR. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-723) Due to prefetching, Yumrepo clobbers any definition that it does not create
Title: Message Title Stefan Lasiewski commented on PUP-723 Re: Due to prefetching, Yumrepo clobbers any definition that it does not create For those of you who find this bug, try Augeas as a workaround: class stefanl::remi ( $ensure = 'latest', $enabled = true, $priority = '80', ) { package { 'remi-release': ensure => $ensure,