Jira (PUP-7289) PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Title: Message Title
Sean Griffin commented on PUP-7289
Re: PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Verify the state of the hiera_config.rb fix. Apply the attached meta-manifest, generating /tmp/manifest. Apply /tmp/manifest. Then run puppet lookup.
Top of the hierarchy is the certname-dependent hiera data cache, identified by the interpolation of %{::$trusted.certname} in /etc/puppetlabs/puppet/hiera.yaml.
The desired output of 'puppet lookup mykey' is 'Global certname.yaml value'.
Verify:
meta3_manifest100% 2076 2.0KB/s 00:00
meta5_manifest100% 1809 1.8KB/s 00:00
PuppetLabs382:hiera_setup sgriffin$ psh tcr7pm8z09facvx
ssh -t r...@tcr7pm8z09facvx.delivery.puppetlabs.net
X11 forwarding request failed on channel 0
Last login: Sat Mar 4 03:35:19 2017 from 10.32.128.185
[root@tcr7pm8z09facvx ~]# puppet --version
4.9.3
Jira (PUP-7289) PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Title: Message Title Sean Griffin updated an issue Puppet / PUP-7289 PUP 4.9.3 interpolation in hiera.yaml datadir stopped working I can't reproduce (what I think is) the complaint. I have a hiera data dir with three key-value stores: one based on trusted.certname, another on OS and a common. Each has an entry for 'mykey', with a distinguishing value indicating its source. The trusted.certname store is at the top of the hiera hierarchy. In all cases 'puppet lookup mykey' returns the trusted.certname value. Comparing puppet-agent build sha (before fix): 690aa2c0b6cac5edd22850eea860171b23d9a003 (1.9.2.17.g690aa2c) with (after fix): 9726e61e50e948b8ba531ebda6b4f4607e66486c (1.9.2.30.g9726e61) I find that both versions correctly iterpolate the trusted.certname fact correctly and produce the desired value for "mykey". I tried using both hiera3 and hiera5 style config files (hiera.yaml) Attached are two meta-manifests, one each for hiera3 and hiera5. Applying a meta-manifest generates a manifest file in /tmp/manifest. Applying /tmp/manifests creates a hiera config file and hiera_data directory consistent with the hiera config. The hiera config file defines three values for the key: mykey, one for each of 3 layers of the hiearchy: trusted.certname, OS, and common, with trusted.certname at the top. With both versions (before-fix, and after-fix) and both hiera configs (hiera versions 3, and 5), 'puppet lookup mykey' always returns the trusted.certname value, as desired. Attached are both meta-manifests. Henrik Lindberg Thomas Hallgren: Am I doing this right? Change By: Sean Griffin Attachment: meta3_manifest Attachment: meta5_manifest Add Comment
Jira (PUP-7300) Some acceptance tests delete global hiera.yaml
Title: Message Title John Duarte commented on PUP-7300 Re: Some acceptance tests delete global hiera.yaml https://github.com/puppetlabs/puppet/pull/5685 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-7300) Some acceptance tests delete global hiera.yaml
Title: Message Title Maggie Dreyer assigned an issue to John Duarte Puppet / PUP-7300 Some acceptance tests delete global hiera.yaml Change By: Maggie Dreyer Assignee: John Duarte 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-7300) Some acceptance tests delete global hiera.yaml
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7300 Some acceptance tests delete global hiera.yaml Change By: Maggie Dreyer Story Points: 1 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-7300) Some acceptance tests delete global hiera.yaml
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7300 Some acceptance tests delete global hiera.yaml Change By: Maggie Dreyer Sprint: AP 2017-03-08 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-7300) Some acceptance tests delete global hiera.yaml
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7300 Some acceptance tests delete global hiera.yaml Change By: Maggie Dreyer Team: Agent & Platform 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-559) Danish UTF-8 chars kills Puppet Server in v2.7.2 (not in 2.5.0)
Title: Message Title Jeremy Barlow moved an issue Hiera / HI-559 Danish UTF-8 chars kills Puppet Server in v2.7.2 (not in 2.5.0) Change By: Jeremy Barlow Affects Version/s: SERVER 2.7.2 Affects Version/s: HI 3.2.0 Key: SERVER HI - 1724 559 Project: Puppet Server 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 (PUP-7203) puppetlabs_spec_helper `spec_prep` target does not work when run from a path with a space in the name
Title: Message Title Josh Samuelson commented on PUP-7203 Re: puppetlabs_spec_helper `spec_prep` target does not work when run from a path with a space in the name I just ran into this, reverting to puppetlabs_spec_helper 1.2.2 is also a functional workaround. 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-7144) Review error string marking and externalization
Title: Message Title Maggie Dreyer commented on PUP-7144 Re: Review error string marking and externalization With some additional verification from the modules team, we figured out that interpolation doesn't work like we hoped. These PRs will need more work before they can be merged. 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-6123) remove ruby code that backs resource_type endpoint
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-6123 remove ruby code that backs resource_type endpoint Change By: Jeremy Barlow 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-7042) Mark non-debug messages for externalization
Title: Message Title Maggie Dreyer commented on PUP-7042 Re: Mark non-debug messages for externalization We just discovered that interpolation doesn't work like we hoped it did. These PRs will need more work before they can be merged. 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-7042) Mark non-debug messages for externalization
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7042 Mark non-debug messages for externalization Change By: Maggie Dreyer Sprint: AP 2017-01-11, AP 2017-01-25, AP 2017-02-08, AP Ready for Engineering 2017-03-08 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-7300) Some acceptance tests delete global hiera.yaml
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-7300 Some acceptance tests delete global hiera.yaml Issue Type: Bug Assignee: Unassigned Created: 2017/03/03 3:00 PM Priority: Normal Reporter: Maggie Dreyer The lookup/v3_config_and_data and lookup/v4_hieradata_with_v5_configs Puppet acceptance tests both overwrite the global heira.yaml, which is laid down by the infrastructure and relied upon by other tests. We need to update both these tests to restore the default hiera.yaml when they're done. See the work done for PUP-7245 . Add Comment This message was sent by Atlassian
Jira (PUP-7291) no hiera class parameter lookup debug information
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7291 no hiera class parameter lookup debug information Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-7291) no hiera class parameter lookup debug information
Title: Message Title Thomas Hallgren commented on PUP-7291 Re: no hiera class parameter lookup debug information Right, what I meant was that there was on output from the "lookup explainer" (there should have been). The current debug output doesn't explain much. It doesn't even tell you that the parameter wasn't found. The correct output (which I'm add now) should look exactly like it does when you call the lookup function. 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-7259) Ensure JSON is preferred serialization format in various termini/serializers
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-7259 Ensure JSON is preferred serialization format in various termini/serializers Change By: Josh Cooper Assignee: Josh Cooper 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-7291) no hiera class parameter lookup debug information
Title: Message Title
Reinhard Vicinus commented on PUP-7291
Re: no hiera class parameter lookup debug information
What i'm missing with puppet 4.9.x is the following output for every class parameter, which is available with puppet 4.8.3. The example shows a lookup of the class parameter postgresql::globals::postgis_version which is not found:
Debug: Performing a hiera indirector lookup of postgresql::globals::postgis_version with options {:variables=>Scope(Class[Postgresql::Globals]), :merge=>#>, @value_type=#]>>>]>, @options={}>}
Debug: hiera(): Using Hiera 1.x backend API to access instance of class Hiera::Backend::Eyaml_backend. Lookup recursion will not be detected
Debug: hiera(): [eyaml_backend]: Set option: datadir = /data/user-environments/rv4/modules/hieradata
Debug: hiera(): [eyaml_backend]: Set option: extension = yaml
Debug: hiera(): [eyaml_backend]: Set option: pkcs7_private_key = /etc/puppetlabs/eyaml/private_key.pkcs7.pem
Debug: hiera(): [eyaml_backend]: Set option: pkcs7_public_key = /etc/puppetlabs/eyaml/public_key.pkcs7.pem
Debug: hiera(): [eyaml_backend]: Looking up postgresql::globals::postgis_version in eYAML backend
Debug: hiera(): [eyaml_backend]: Looking for data source nodes/dash
Jira (PUP-7291) no hiera class parameter lookup debug information
Title: Message Title
Thomas Hallgren commented on PUP-7291
Re: no hiera class parameter lookup debug information
There was no output from the explainer for lookups of class parameters 4.8.x, so this is not a regression. There was some limited debug output though, such as:
Debug: hiera(): Hiera YAML backend starting
Debug: hiera(): Looking up lookup_options in YAML backend
Debug: hiera(): Looking for data source common
Debug: hiera(): Looking for data source other
Debug: Performing a hiera indirector lookup of foo::a with options {...}
Debug: hiera(): Looking up foo::a in YAML backend
This output is now gone without being replaced by the explainer output.
Add Comment
Jira (PUP-7291) no hiera class parameter lookup debug information
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7291 no hiera class parameter lookup debug information Change By: Thomas Hallgren Story Points: 1 Sprint: PDE 2017-03-08 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-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-3058 Report not being stored in PuppetDB due to Unicode Error Change By: Susan McNerney Labels: davis-triage maintenance 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-3321) Missing comma from example
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3321 Missing comma from example Issue Type: Bug Assignee: Unassigned Created: 2017/03/03 1:37 PM Priority: Normal Reporter: gepetto-bot Re-opening PR 2184 under Stable branch. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title
Charlie Sharpsteen commented on PDB-3058
Re: Report not being stored in PuppetDB due to Unicode Error
Also looks like this can happen when setting registry values on windows, as the default value for some is a null byte.
For example the legal notice that can be set on Windows:
# The default value on 2012R2 is a null byte so this resource will produce a failing report.
registry_value { 'HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\legalnoticetext':
ensure => present,
data ="" "test string",
type => 'string',
}
# Using a unicode escape to re-set the default value will succeed, but also produces a failing report.
registry_value { 'HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\legalnoticetext':
Jira (PUP-7299) Backport PUP-7191 to 2016.4.x LTS - error on non-existent svc on AIX
Title: Message Title Geoff Nichols commented on PUP-7299 Re: Backport PUP-7191 to 2016.4.x LTS - error on non-existent svc on AIX cc Eric Sorenson 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-1578) Facter incorrectly converts integers causing negative values to be stored in PDB
Title: Message Title Branan Riley commented on FACT-1578 Re: Facter incorrectly converts integers causing negative values to be stored in PDB This is a super easy fix as soon as we prioritize it. We're just using the wrong function to convert integers from C++ to Ruby. It'll mean a leatherman bump to add the new function we need to the Ruby bindings. We should also double-check that we're doing it right when we go the other way. 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 we'll be looking at this in a week or so at LTS triage - please let me know if approval is more urgent than that (the LTS Z is targeted for early May). 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-7291) no hiera class parameter lookup debug information
Title: Message Title Henrik Lindberg commented on PUP-7291 Re: no hiera class parameter lookup debug information Added this ticket to 4.9.4 if there is time to fix this. 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-7291) no hiera class parameter lookup debug information
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7291 no hiera class parameter lookup debug information Change By: Henrik Lindberg Fix Version/s: PUP 4.9.4 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-7291) no hiera class parameter lookup debug information
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-7291 no hiera class parameter lookup debug information Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-7297) puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7297 puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb Change By: Kenn Hussey Release Notes: Not Needed 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-7299) Backport PUP-7191 to 2016.4.x LTS - error on non-existent svc on AIX
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7299 Backport PUP-7191 to 2016.4.x LTS - error on non-existent svc on AIX Change By: Geoff Nichols Sprint: AP 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 (PUP-7299) Backport PUP-7191 to 2016.4.x LTS - error on non-existent svc on AIX
Title: Message Title
Susan McNerney updated an issue
Puppet / PUP-7299
Backport PUP-7191 to 2016.4.x LTS - error on non-existent svc on AIX
Change By:
Susan McNerney
This ticket proposes backporting this fix to the LTS line (2016.4.x). *Info from PUP-7191 ticket:*When managing a non-existent service on AIX, get something like:{code}Error: /Stage[main]/Main/Service[nothere]: Could not evaluate: Cannot get status of nothere, error was: Execution of '/usr/bin/lssrc -s nothere' returned 1: 0513-085 The nothere Subsystem is not on file.Wrapped exception:Execution of '/usr/bin/lssrc -s nothere' returned 1: 0513-085 The nothere Subsystem is not on file.{code}The behavior of puppet with respect to managing non-existent services is non-standard across various OSes.On Ubuntu (systemd), a non-existent service raises no error, and does not even report its non-existence via ral:{code}☂ : puppet apply -e " service { 'foo' : ensure => stopped } "Notice: Compiled catalog for ubuntu16.localdomain in environment production in 0.06 secondsNotice: Applied catalog in 0.05 seconds☂ : puppet resource service foobar ensure=stoppedservice { 'foobar': ensure => 'stopped',}{code}On OSX (launchctl), it reports an error:{code}☂ : be puppet apply -e " service { 'foo' : ensure => stopped } "Notice: Compiled catalog for macbook-pro-2.local in environment production in 0.34 secondsError: Unable to find launchd plist for job: fooError: /Stage[main]/Main/Service[foo]/ensure: change from absent to stopped failed: Unable to find launchd plist for job: fooNotice: Applied catalog in 2.14 seconds☂ : be puppet resource service foo ensure=stoppedError: Unable to find launchd plist for job: fooError: /Service[foo]/ensure: change from absent to stopped failed: Unable to find launchd plist for job: fooservice { 'foo': ensure => 'absent',}{code}On Centos 7 (also systemd), same as ubuntu - no errors:{code}[root@centos7 ~]# puppet apply -e " service { 'foo' : ensure => stopped } "Notice: Compiled catalog for centos7.localdomain in environment production in 0.07 secondsNotice: Applied catalog in 0.35 seconds[root@centos7 ~]# puppet resource service foo ensure=stoppedservice { 'foo': ensure => 'stopped',}{code}Since AIX is primarily an RPM based system, it seems to make sense to go the route of not erroring when a service is not present (perhaps issuing a debug message if this is the case).
Add Comment
Jira (PUP-7299) Backport PUP-7191 to 2016.4.x LTS - error on non-existent svc on AIX
Title: Message Title Susan McNerney commented on PUP-7299 Re: Backport PUP-7191 to 2016.4.x LTS - error on non-existent svc on AIX Kenn Hussey Geoff Nichols Tiffany Longworth Here is the backport ticket for 7191; this is what we'll be evaluating at LTS 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 (PUP-7299) Backport PUP-7191 to 2016.4.x LTS - error on non-existent svc on AIX
Title: Message Title Susan McNerney updated an issue Puppet / PUP-7299 Backport PUP-7191 to 2016.4.x LTS - error on non-existent svc on AIX Change By: Susan McNerney Priority: Normal Major 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-7299) Backport PUP-7191 to 2016.4.x LTS - error on non-existent svc on AIX
Title: Message Title Susan McNerney updated an issue Puppet / PUP-7299 Backport PUP-7191 to 2016.4.x LTS - error on non-existent svc on AIX Change By: Susan McNerney Summary: Backport PUP-7191 to 2016.4.x LTS - error on non-existent svc on AIX 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-7299) Backport PUP-7191 to 2016.4.x LTS
Title: Message Title Susan McNerney created an issue Puppet / PUP-7299 Backport PUP-7191 to 2016.4.x LTS Issue Type: Bug Assignee: Susan McNerney Created: 2017/03/03 11:03 AM Labels: davis-triage Priority: Normal Reporter: Susan McNerney 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"
Jira (PUP-7191) Puppet errors when managing non-existent service on AIX
Title: Message Title Susan McNerney updated an issue Puppet / PUP-7191 Puppet errors when managing non-existent service on AIX Change By: Susan McNerney Labels: davis-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 (PUP-7215) Problem with puppet-agent 1.9.x and hiera eyaml backend
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7215 Problem with puppet-agent 1.9.x and hiera eyaml backend Change By: Eric Thompson QA Risk Assessment Reason: not fully covered by unit tests. eyaml backwards compat with hiera3 config, will cover in test against related 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 (PUP-7215) Problem with puppet-agent 1.9.x and hiera eyaml backend
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7215 Problem with puppet-agent 1.9.x and hiera eyaml backend Change By: Eric Thompson QA Risk Assessment: Needs Assessment Automate 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-7289) PUP 4.9.3 interpolation in hiera.yaml datadir stopped working
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7289 PUP 4.9.3 interpolation in hiera.yaml datadir stopped working Change By: Eric Thompson QA Risk Assessment: Needs Assessment Automate 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-7216) hiera_hash doesn't use deeper merge
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7216 hiera_hash doesn't use deeper merge Change By: Eric Thompson QA Risk Assessment Reason: high risk; not fully covered by coverage in unit tests , but regression. acceptance me 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-3320) Error in example
Title: Message Title Jessykah Bird created an issue PuppetDB / PDB-3320 Error in example Issue Type: Bug Assignee: Unassigned Components: DOCS Created: 2017/03/03 10:17 AM Priority: Normal Reporter: Jessykah Bird View PR: https://github.com/puppetlabs/puppetdb/pull/2184 Filing the Jira ticket under PuppetDB since the documentation is in the puppetdb repo. Add Comment
Jira (PUP-7216) hiera_hash doesn't use deeper merge
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7216 hiera_hash doesn't use deeper merge Change By: Eric Thompson QA Risk Assessment Reason: high risk; not fully covered by unit tests 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-7216) hiera_hash doesn't use deeper merge
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7216 hiera_hash doesn't use deeper merge Change By: Eric Thompson QA Risk Assessment: Needs Assessment Automate 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-3319) Missing comma from example
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3319 Missing comma from example Issue Type: Bug Assignee: Unassigned Created: 2017/03/03 10:15 AM Priority: Normal Reporter: gepetto-bot When trying to use the example on line 58, puppet parser errors due to the lack of comma after nodes, and is unable to do a successful query. Adding the comma makes puppet happy. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3318) Change the node-purge-ttl default from 0 ( don't delete deactivated nodes) to the same as report-ttl ( defaults to 14 days )
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-3318 Change the node-purge-ttl default from 0 ( don't delete deactivated nodes) to the same as report-ttl ( defaults to 14 days ) Change By: Nick Walker h1. The problemWhen you create and destroy nodes in your puppet infrastructure you build up a lot of deactivated nodes in your PuppetDB database that serve no real purpose but do slow down the performance of the database and cause it to grow. h1. Suggested Solution node-purge-ttl should be enabled by default and set equal to or higher than report-ttl. It should generally be set to an interval longer than report-ttl to avoid needing the node purge process to also delete reports. h1. ConsiderationsIt could be that we need to add a migration step that will delete old nodes during an upgrade so that post-upgrade the service isn't churning through deleting nodes but not processing catalogs or facts. Upon further thought, it would probably be better to implement PDB-3173 and have the default be that node-purge-ttl will only delete up to 100 nodes whenever it runs. Then when this setting is enabled it shouldn't suddenly cause too much churn if you have 1000s of deactivated nodes. 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
Jira (PUP-7297) puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb
Title: Message Title John Duarte commented on PUP-7297 Re: puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb Test update merged into stable at https://github.com/puppetlabs/puppet/commit/d264b739a770c34029808b6b6f0e9411f5c2f5db 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-7297) puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7297 puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb Change By: Kenn Hussey Fix Version/s: PUP 4.9.z Fix Version/s: PUP 4.9.4 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-7298) SUGGESTION: Add return code to error message on file resources
Title: Message Title
Thomas Mashos created an issue
Puppet / PUP-7298
SUGGESTION: Add return code to error message on file resources
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/03/03 9:22 AM
Priority:
Normal
Reporter:
Thomas Mashos
Using a file resource with the source set to a link. If there is an error from the server (eg. a 500 error in my case) it should print that to the terminal in the error message. Currently the return code is only available when running puppet with the -d flag
What does happen Puppet run returns the following in the event of an error "Could not evaluate: Could not retrieve information from environment ipam_fix source(s) "
What should happen Puppet run returns the following in the event of an error "Could not evaluate: Could not retrieve information from environment ipam_fix source(s) . Return code "
Steps to reproduce Create a test.pp with the following puppet code
file { '/tmp/foo.html':
ensure => present,
Jira (HI-544) Hiera should error if it finds a v4 hiera.yaml
Title: Message Title Maggie Dreyer commented on HI-544 Re: Hiera should error if it finds a v4 hiera.yaml Here is the PR with the commit reapplied: https://github.com/puppetlabs/hiera/pull/391 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-7284) hiera-eyaml option 'extension' is ignored
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-7284 hiera-eyaml option 'extension' is ignored Change By: John Duarte Status: Ready for CI Test Assignee: qa 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-7297) puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7297 puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb The test that fails is no longer valid and should be removed. Change By: Thomas Hallgren Story Points: 1 Sprint: PDE 2017-03-08 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-7297) puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7297 puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-7297) puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7297 puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb Change By: Geoff Nichols Team: Puppet Developer Experience 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-7297) puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7297 puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb Change By: Kenn Hussey Fix Version/s: PUP 4.9.z 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-7270) Create 4.10.x branch and CI jobs
Title: Message Title Ethan Brown commented on PUP-7270 Re: Create 4.10.x branch and CI jobs Original proposal for how to split up the content is at https://gist.github.com/Iristyle/8a3236d04e246a7a1159c188fb4ca133#file-proposal-md Maggie Dreyer sent out an email about the work she did, archived at https://groups.google.com/a/puppet.com/forum/#!topic/org-product-and-engineering/RtfIx9Z-RDI Contents: Hello everyone, Since we are not shipping Puppet 5 in PE 2017.2 (Glisan), but rather along side it, we have created a new 4.10.x branch in puppet, as well as a corresponding 1.10.x branch in puppet-agent, to be the target of work intended to land in Glisan. This release is going to primarily feature the i18n and UTF-8 work in Puppet for our Japan launch. So to summarize, the branches in Puppet and Puppet Agent are now as follows: Stable = Puppet 4.9 -> Agent 1.9 -> PE 2017.1 (Flanders) 4.10.x = Puppet 4.10.x -> Agent 1.10.x -> PE 2017.2 (Glisan)
Jira (PUP-7297) puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-7297 puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-7297) puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb
Title: Message Title Geoff Nichols created an issue Puppet / PUP-7297 puppet#stable CI failure in acceptance/tests/lookup/v3_config_and_data.rb Issue Type: CI Blocker Assignee: Unassigned Created: 2017/03/03 7:06 AM Priority: Normal Reporter: Geoff Nichols Latest build of puppet-agent with puppet#stable @ b958d3b038e416dec9c8dfd2e4c121635a64af1a failed in acceptance/tests/lookup/v3_config_and_data.rb: 04:58:36 Test Case tests/lookup/v3_config_and_data.rb reported: # 04:58:36 Expected /"jsonval" => "4",\n\s+"val" => 4/m to match "Searching for \"lookup_options\"\n Global Data Provider (hiera configuration version 3)\nUsing configuration \"/etc/puppetlabs/puppet/hiera.yaml\"\nMerge strategy hash\n Hierarchy entry \"yaml\"\nMerge strategy hash\n Path \"/etc/puppetlabs/code/environments/v3_config_and_data_uote7iwn/hieradata/somesuch.yaml\"\nOriginal path: \"somesuch\"\nNo such key: \"lookup_options\"\n Path \"/etc/puppetlabs/code/environments/v3_config_and_data_uote7iwn/hieradata/common.yaml\"\nOriginal path: \"common\"\nPath not found\n Hierarchy entry \"json\"\nMerge strategy hash\n Path \"/etc/puppetlabs/code/environments/v3_config_and_data_uote7iwn/hieradata/somesuch.json\"\n
Jira (HI-544) Hiera should error if it finds a v4 hiera.yaml
Title: Message Title Kenn Hussey assigned an issue to Maggie Dreyer Hiera / HI-544 Hiera should error if it finds a v4 hiera.yaml Change By: Kenn Hussey Assignee: Maggie Dreyer Team: Puppet Developer Experience Agent & Platform 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-7180) Document SSL requirements for `reporturl` option and `http` report processor
Title: Message Title Geoff Nichols assigned an issue to Jorie Tappa Puppet / PUP-7180 Document SSL requirements for `reporturl` option and `http` report processor Change By: Geoff Nichols Assignee: Nicholas Fagerlund Jorie Tappa 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-7180) Document SSL requirements for `reporturl` option and `http` report processor
Title: Message Title Geoff Nichols commented on PUP-7180 Re: Document SSL requirements for `reporturl` option and `http` report processor cc Jorie Tappa 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-7180) Document SSL requirements for `reporturl` option and `http` report processor
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7180 Document SSL requirements for `reporturl` option and `http` report processor Change By: Geoff Nichols Sprint: AP Grooming On-Deck 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-544) Hiera should error if it finds a v4 hiera.yaml
Title: Message Title Geoff Nichols commented on HI-544 Re: Hiera should error if it finds a v4 hiera.yaml Maggie Dreyer, when you have a chance, could you please take a look at this? (See also https://github.com/puppetlabs/hiera/pull/390 for HI-519.) /cc Josh Cooper 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-7273) Hiera 5: error unless data_hash is defined
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7273 Hiera 5: error unless data_hash is defined Moving this to 4.10.0 to see if there is something simple we can do to improve the error message. 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-7273) Hiera 5: error unless data_hash is defined
Title: Message Title Henrik Lindberg commented on PUP-7273 Re: Hiera 5: error unless data_hash is defined Agree - we need to design that well (a general mechanism for some kind of "on-error/usage" behavior for functions) and I think that is out of scope for 4.9.z. If there is something we can do with the heuristics for type-mismatch that would improve this particular case, then I am for doing that. For instance if the function expects a Struct with one entry and that entry is missing, it could mention the key instead of the more generic expected 1 key and got 0. Suspect that it is not that simple though. 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-7273) Hiera 5: error unless data_hash is defined
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7273 Hiera 5: error unless data_hash is defined Change By: Henrik Lindberg Fix Version/s: PUP 4.9.z Fix Version/s: PUP 4.10.0 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-6862) Lookup doesn't interpolate values into top level (hash) keys
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6862
Lookup doesn't interpolate values into top level (hash) keys
Change By:
Henrik Lindberg
It appears that lookup doesn't interpolate values into the keys of hashes whereas it works with hiera. For example:{code}testhash: "%{osfamily}":subkey: "%{osfamily}""%{osfamily}": "value"{code}With lookup, I get:{code}# puppet lookup --environment=gitlab_runner_lookup --node --explain testhashMerge strategy first Data Binding "hiera"No such key: "testhash" Data Provider "Hiera Data Provider, version 4"ConfigurationPath "/etc/puppetlabs/code/environments/gitlab_runner_lookup/hiera.yaml"Data Provider "Nodes" Path "/etc/puppetlabs/code/environments/gitlab_runner_lookup/hieradata/nodes/.yaml"Original path: "nodes/%{trusted.certname}"Interpolation on "%{osfamily}" Global ScopeFound key: "osfamily" value: "Debian"Found key: "testhash" value: { "%{osfamily}" => {"subkey" => "Debian","%{osfamily}" => "value" }} Merged result: {"%{osfamily}" => { "subkey" => "Debian", "%{osfamily}" => "value"} }{code}And with environment data disabled, hiera returns:{code}# puppet lookup --environment=gitlab_runner_lookup --node --explain testhashData Binding "hiera" Found key: "testhash" value: {"Debian" => { "subkey" => "Debian", "Debian" => "value"} }{code} UPDATE This is per design - it does not make sense to interpolate into the top level keys. It is considered a bug in the hiera interpolation - it was never intended to work.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7296) The eyaml lookup_key function does not evaluate interpolated hash keys
Title: Message Title Henrik Lindberg commented on PUP-7296 Re: The eyaml lookup_key function does not evaluate interpolated hash keys merged to stable, 4.10.x and master 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-7296) The eyaml lookup_key function does not evaluate interpolated hash keys
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7296 The eyaml lookup_key function does not evaluate interpolated hash keys Change By: Henrik Lindberg Release Notes Summary: A regression in hiera 5's support for eyaml caused interpolation in looked up hash values to stop working. This is now fixed and for looked up hashes both keys and values are now interpolated. 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 (PUP-6862) Lookup doesn't interpolate values into top level (hash) keys
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6862 Lookup doesn't interpolate values into top level (hash) keys Change By: Henrik Lindberg Summary: Lookup doesn't interpolate values into top level ( hash ) keys 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.
