Jira (PUP-6989) Acceptance testing using TYPE=git and preserved hosts is broken
Title: Message Title Thomas Hallgren commented on PUP-6989 Re: Acceptance testing using TYPE=git and preserved hosts is broken Sounds great. My primary concern is stated in acceptance criteria. I don't want to be the one to blame when Jenkins goes red 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-1537) Facter 3.5.0 tarball is broken
Title: Message Title Geoff Nichols commented on FACT-1537 Re: Facter 3.5.0 tarball is broken Confirmed Facter tarball created from facter checkout 3.5.0-26-g6a48928 using workflow (`rake package:bootstrap; rake package:tar`) contains the `locales` directory. 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-6739) If no matching local $environment folder on agent, error when running any 'puppet config' command
Title: Message Title Jeremy Adams updated an issue Puppet / PUP-6739 If no matching local $environment folder on agent, error when running any 'puppet config' command Change By: Jeremy Adams Comment: [~paul.anderson] You're correct about 'produciton' being special. I'll amend the description. 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-6739) If no matching local $environment folder on agent, error when running any 'puppet config' command
Title: Message Title Jeremy Adams commented on PUP-6739 Re: If no matching local $environment folder on agent, error when running any 'puppet config' command The really use case that raised this is the fact that we wanted to set certname, server, and environment in puppet.conf on install. So you can't do this [root@pup-vra7-0444 ~]# puppet config set environment dev [root@pup-vra7-0444 ~]# puppet config set certname foobar /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:29:in `push_application_context' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:337:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /usr/local/bin/puppet:5:in `'
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' command
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6739 If no matching local $environment folder on agent, error when running any 'puppet config' command Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' command
Title: Message Title Jeremy Adams commented on PUP-6739 Re: If no matching local $environment folder on agent, error when running any 'puppet config' command SIMPLE REPRO: [root@pup-vra7-0443 ~]# puppet config set environment foo [root@pup-vra7-0443 ~]# puppet config set environment production /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'foo' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:29:in `push_application_context' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:337:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /usr/local/bin/puppet:5:in `' [root@pup-vra7-0443 ~]# puppet config print
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' command
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6739
If no matching local $environment folder on agent, error when running any 'puppet config' command
Change By:
Jeremy Adams
If no matching local $environment folder on agent, error when running any 'puppet config' command.See REPRO in comment below.For example, if you have an environment called 'dev' on the master, and you want to set an agent's $environment from the default of 'production' to 'dev', you might issue a {{puppet config set environment dev}} comand. When run, {{puppet config}} will look up the current environment ('production' at this point) and ensure there is a corresponding 'production' folder in the environments path. Assume this succeeds because a 'production' folder exists locally on the agent, by default, but NO OTHER environment folders exist locally on the agent (and shouldn't need to exist in my view ).Now the environment is set to 'dev'.If a user issues any {{puppet config}} command at this point, the current environment ('dev' at this point) will NOT have a corresponding environment folder, so we get an error like:{code}Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist?{code}{code}[root@pup-vra7-0403 ~]# puppet config set environment production/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:29:in `push_application_context' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:337:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /usr/local/bin/puppet:5:in `'{code}This means we're stuck and cannot issue any {{puppet config print}} or {{puppet config set}} commands even to get us back to an environment setting of 'production'!
Add Comment
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' command
Title: Message Title Jeremy Adams assigned an issue to Unassigned Puppet / PUP-6739 If no matching local $environment folder on agent, error when running any 'puppet config' command Change By: Jeremy Adams Assignee: 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 (PDB-3207) Backport HUP/ezbake reload and size-based logback logging for PE 2016.4.3 release
Title: Message Title Jeremy Barlow commented on PDB-3207 Re: Backport HUP/ezbake reload and size-based logback logging for PE 2016.4.3 release Merged to puppetdb#4.2.3.x at 98b93a. 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-6976) Scope effort to externalize Puppet report strings for translation
Title: Message Title Maggie Dreyer commented on PUP-6976 Re: Scope effort to externalize Puppet report strings for translation It looks like we may be able to use this Ruby AST parser/rewriter to automate wrapping translatable strings in Puppet: https://github.com/whitequark/parser. I wrote a script using it that seems to work on an example test case: https://github.com/magisus/rxstrings. This seems more robust than attempting to just treat the files as text, though doubtless there are many more special cases and exceptions that would need to be added as we try it on more complicated files. We will also need to better define what counts as a "translatable string", so we can add more heuristics. 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-1550) Puppet Agent Not Working with Dynamic CPU Allocations on AIX
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1550 Puppet Agent Not Working with Dynamic CPU Allocations on AIX Change By: Geoff Nichols 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 (FACT-1441) Add "cloud" fact that identifies Azure
Title: Message Title
Michael Smith commented on FACT-1441
Re: Add "cloud" fact that identifies Azure
This discussion seems to have arrived at adding a new top-level structured fact cloud, such that the following would be present on an Azure host
"cloud": {
"provider": "azure"
}
I'm treating this as the conclusion, as we're close to merging it.
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
Jira (FACT-1550) Puppet Agent Not Working with Dynamic CPU Allocations on AIX
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1550 Puppet Agent Not Working with Dynamic CPU Allocations 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 (PDB-3222) stop testing multiple hosts/cell in PDB acceptance tests
Title: Message Title John Duarte commented on PDB-3222 Re: stop testing multiple hosts/cell in PDB acceptance tests Wyatt Alt, sorry I do not have insight into the vmpooler capacity available to accommodate the pdb matrix. If you can provide a total for the number of hosts needed by OS then QE should be able to make that assessment. cc. James Wagner 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-6989) Acceptance testing using TYPE=git and preserved hosts is broken
Title: Message Title Josh Cooper commented on PUP-6989 Re: Acceptance testing using TYPE=git and preserved hosts is broken I'm working on a PR to fix the semantic_puppet part of this ticket, make it so we can install puppet from a git checkout, but use bundler to install the rest of its dependencies (so we don't need to list them in options.rb or have to worry about the install.rb silliness). 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-3222) stop testing multiple hosts/cell in PDB acceptance tests
Title: Message Title Wyatt Alt commented on PDB-3222 Re: stop testing multiple hosts/cell in PDB acceptance tests John Duarte Wayne Warren do either of you have a sense of whether this would allow us to move to vmpooler without reducing our matrix? 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-3222) stop testing multiple hosts/cell in PDB acceptance tests
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3222 stop testing multiple hosts/cell in PDB acceptance tests Issue Type: Improvement Assignee: Unassigned Created: 2016/12/08 1:47 PM Priority: Normal Reporter: Wyatt Alt Most of our tests are mda + a. We've got one mda + da for the terminus failover, and an additional mda + a + a. I don't think we're getting any real benefit from testing alongside. We should probably keep one mda + a and the terminus, but everything else should be switch to mda only. This would nearly halve our capacity requirements/costs. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3222) stop testing multiple hosts/cell in PDB acceptance tests
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3222 stop testing multiple hosts/cell in PDB acceptance tests Change By: Wyatt Alt Most of our tests are mda + a. We've got one mda + da for the terminus failover, and an additional mda + a + a. I don't think we're getting any real benefit from testing alongside. We should probably keep one mda + a and the terminus failover , but everything else should be switch to mda only.This would nearly halve our capacity requirements/costs. 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-3222) stop testing multiple hosts/cell in PDB acceptance tests
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3222 stop testing multiple hosts/cell in PDB acceptance tests Change By: Wyatt Alt Most of our tests are mda + a. We've got one mda + da for the terminus failover, and an additional mda + a + a. I don't think we're getting any real benefit from testing alongside. We should probably keep one mda + a and the terminus failover, but everything else should be switch switched to mda only.This would nearly halve our capacity requirements/costs. 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-6989) Acceptance testing using TYPE=git and preserved hosts is broken
Title: Message Title Eric Thompson commented on PUP-6989 Re: Acceptance testing using TYPE=git and preserved hosts is broken good question Thomas Hallgren. i put a lot of work into that PR last year, but no one was all that interested but something that came out of that was rototiller, which we've just released in QA. i've been waiting on that to reboot efforts in fixing up the Rakefiles and unifying tasks across projects. We need a better beaker_task in ... beaker and i have a ticket to create that using rototiller. so the answer is... real soon now. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6989) Acceptance testing using TYPE=git and preserved hosts is broken
Title: Message Title Thomas Hallgren commented on PUP-6989 Re: Acceptance testing using TYPE=git and preserved hosts is broken That pull request seems to be stalled. Not merged and no action since May. The ticket was reopened in February. Eric Thompson, PA-139 is assigned to you. Do you have any plans to continue the work? 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Charlie Sharpsteen commented on PUP-6986 Re: Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Since pe -ef output can contain whatever arbitrary bytes that other processes happen to feel like adding to their command lines, submitted a quick patch that just does the regex matching in a binary ASCII-8BIT encoding. 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-3221) `three-node-end-to-end` test failed with ConnectionException
Title: Message Title Jeremy Barlow updated an issue PuppetDB / PDB-3221 `three-node-end-to-end` test failed with ConnectionException Change By: Jeremy Barlow Summary: `three-node-end-to-end` test failed with ConnectionException 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-6991) Puppet Agent Not Working with Dynamic CPU Allocations on AIX
Title: Message Title Eric Sorenson commented on PUP-6991 Re: Puppet Agent Not Working with Dynamic CPU Allocations on AIX More detail: > facter -p | grep POWER 2016-12-07 10:39:44.535942 WARN puppetlabs.facter - Could not get a value from lsattr -El proc0 -a type As you can see facter is assuming that proc0 is always existing . But this is not the case: >lsattr -El proc0 -a type lsattr: 0514-519 The following device was not found in the customized device configuration database: proc0 >lsdev
Jira (FACT-1550) Puppet Agent Not Working with Dynamic CPU Allocations on AIX
Title: Message Title Eric Sorenson moved an issue Facter / FACT-1550 Puppet Agent Not Working with Dynamic CPU Allocations on AIX Change By: Eric Sorenson Key: PUP FACT - 6991 1550 Project: Puppet Facter 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-1550) Puppet Agent Not Working with Dynamic CPU Allocations on AIX
Title: Message Title Eric Sorenson updated an issue Facter / FACT-1550 Puppet Agent Not Working with Dynamic CPU Allocations on AIX Change By: Eric Sorenson Fix Version/s: FACT 3.y 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-6991) Puppet Agent Not Working with Dynamic CPU Allocations on AIX
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-6991 Puppet Agent Not Working with Dynamic CPU Allocations on AIX Change By: Eric Sorenson Comment: From the customer who reported it:> The issue seems to be around mcollective, not specifically the puppet agent itself. What would be an easy fix to include is to pipe output from mcollective to /dev/null. 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-6991) Puppet Agent Not Working with Dynamic CPU Allocations on AIX
Title: Message Title Eric Sorenson moved an issue Puppet / PUP-6991 Puppet Agent Not Working with Dynamic CPU Allocations on AIX Change By: Eric Sorenson Key: ENTERPRISE PUP - 498 6991 Project: Puppet Enterprise 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-6990) Unable to specify RPM with architecture in tag
Title: Message Title
Jesse Hanley created an issue
Puppet / PUP-6990
Unable to specify RPM with architecture in tag
Issue Type:
Bug
Affects Versions:
PUP 4.8.1, PUP 4.8.0, PUP 4.7.0, PUP 4.6.2, PUP 4.6.1, PUP 4.6.0, PUP 4.5.3, PUP 4.5.2, PUP 4.5.1, PUP 4.5.0
Assignee:
Unassigned
Created:
2016/12/08 11:58 AM
Environment:
{{# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.2 (Maipo)
puppet --version 4.6.2}}
Priority:
Normal
Reporter:
Jesse Hanley
While attempting to install a specific version of a package using the package resource, we encountered an issue introduced in commit 3a548510ee10e58a37b66b75ebd73a24d2e2d713.
The RPM has 'x86_64' as part of the release tag. Attempting to install this with {{ ensure => "version" }} syntax now fails.
Jira (PDB-3220) resource_events_resource_type_idx should be removed because it's unused and duplicates resource_events_resource_timestamp
Title: Message Title Wyatt Alt commented on PDB-3220 Re: resource_events_resource_type_idx should be removed because it's unused and duplicates resource_events_resource_timestamp I'm +1 on this. This index is not used in any of the summary dumps I've seen. 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-3220) resource_events_resource_type_idx should be removed because it's unused and duplicates resource_events_resource_timestamp
Title: Message Title Nick Walker created an issue PuppetDB / PDB-3220 resource_events_resource_type_idx should be removed because it's unused and duplicates resource_events_resource_timestamp Issue Type: Improvement Assignee: Unassigned Created: 2016/12/08 11:49 AM Labels: tcse Priority: Normal Reporter: Nick Walker The Problem \d+ resource_events ... Indexes: ...
Jira (PDB-3219) Deleting from reports spends most of the time enforcing a constraint on certnames
Title: Message Title Nick Walker commented on PDB-3219 Re: Deleting from reports spends most of the time enforcing a constraint on certnames Wyatt Alt Looks like creating the index on lastest_report_id takes the delete from 2-3 minutes to 15-20 seconds. We have the open PR for making the index on PDB-3053 based on the issue documented there. Are you +1 to merge that PR into whatever version of PDB is in PE 2016.4.2 and then up to 2016.5 as well? 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-6989) Acceptance testing using TYPE=git and preserved hosts is broken
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6989 Acceptance testing using TYPE=git and preserved hosts is broken Change By: Josh Cooper Labels: 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 (PUP-6989) Acceptance testing using TYPE=git and preserved hosts is broken
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6989 Acceptance testing using TYPE=git and preserved hosts is broken The issue with the rake commands should be fixed in PA-139, see https://github.com/puppetlabs/puppet/pull/4570. Change By: Josh Cooper Labels: 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 (PUP-6983) File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.
Title: Message Title Ethan Brown commented on PUP-6983 Re: File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0. Sean Griffin be careful not to confuse the current locale settings (that apply to the terminal output for instance) and Puppets handling of encodings internally. Puppet reads manifests as UTF-8 always, and should create files with UTF-8 names as you've specified in the manifest. However, due to terminal behavior and the configured locale, it may not display the characters properly (this can often be a problem on Windows). This may also be the source of the particular error if the filename is being translated to Rubys Encoding.default_external, which would be ISO-8859-1 based on your test. If there is no conversion of the UTF-8 characters in the manifest to the current locale, you will see weird console output. In many cases there will be no way to convert A couple of things worth testing: Pipe the results of the run directly to a file, and see if the log is expressed in UTF-8 properly Change the LANG / LC_ALL environment variables on Ubuntu to UTF-8 and re-run your tests - see if the console output / file look differently or contain different bytes 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
Jira (PUP-6983) File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.
Title: Message Title Sean Griffin commented on PUP-6983 Re: File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0. Josh Cooper I tried it again on new ubuntu 1604 VM (because the other was recycled) configured with Beaker the same way. When I did what you did I still get the same error. Could you confirm again? vxenytopw048him.delivery.puppetlabs.net The failure seems to be when the file is getting backed up, the title is translated to a different character set. In the ubuntu16 case this is ISO-8859-1. On Windows it is translating to IBM437. Both are 1-byte per character, and therefore have very few characters compared to UTF-8. Choosing a different character that is in both of those target character sets (e.g., Ñ instead of €) results in no errors and correct behavior. I don't think we can claim utf-8 support if it only works for so few utf-8 characters. 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-6983) File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6983 File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0. 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6983) File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6983 File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0. Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6979) Puppet Module List fails in code page 65001 on ja-JP windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6979 Puppet Module List fails in code page 65001 on ja-JP windows Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1491) Failed to get IP Address
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1491 Failed to get IP Address Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1491) Failed to get IP Address
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1491 Failed to get IP Address Change By: Geoff Nichols Labels: 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 (FACT-1491) Failed to get IP Address
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1491 Failed to get IP Address Change By: Geoff Nichols 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 (PUP-6616) Acceptance: Catalog concurrency test consistently fails on Cisco XR
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6616 Acceptance: Catalog concurrency test consistently fails on Cisco XR Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6616) Acceptance: Catalog concurrency test consistently fails on Cisco XR
Title: Message Title Geoff Nichols assigned an issue to Stan Duffy Puppet / PUP-6616 Acceptance: Catalog concurrency test consistently fails on Cisco XR Change By: Geoff Nichols Assignee: Stan Duffy 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-1539) facter 3.5.0 (and 3.5.1) fail to build
Title: Message Title Maggie Dreyer commented on FACT-1539 Re: facter 3.5.0 (and 3.5.1) fail to build Through CI at https://jenkins.puppetlabs.com/view/puppet-agent/view/stable/view/puppet-agent/job/platform_puppet-agent_intn-van-sys_suite-daily-facter-stable/205/ 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-3219) Deleting from reports spends most of the time enforcing a constraint on certnames
Title: Message Title Nick Walker commented on PDB-3219 Re: Deleting from reports spends most of the time enforcing a constraint on certnames This is most likely so slow because of PDB-3053 We need the index on latest_report_id if we're going to have a FK on it. 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-6945) acceptance: lookup rich data values
Title: Message Title Eric Thompson commented on PUP-6945 Re: acceptance: lookup rich data values remove the colon from the hiera config [root@idosxnpkpepttls some_mod]# puppet lookup --explain --environment lookup_rich_values_6xdoz5jm environment_key Searching for "lookup_options" Data Binding "hiera" No such key: "lookup_options" Environment Data Provider (hiera configuration version 5) Using configuration "/etc/puppetlabs/code/environments/lookup_rich_values_6xdoz5jm/hiera.yaml" Hierarchy entry "Test" Syntax error at 'options' at /etc/puppetlabs/code/environments/lookup_rich_values_6xdoz5jm/modules/some_mod/functions/rich_data_test.pp:1:35 in Syntax error at 'options' at /etc/puppetlabs/code/environments/lookup_rich_values_6xdoz5jm/modules/some_mod/functions/rich_data_test.pp:1:35
Jira (PUP-6945) acceptance: lookup rich data values
Title: Message Title Eric Thompson commented on PUP-6945 Re: acceptance: lookup rich data values due to the above, i tried moving the function into a module, but it's raising a ruby error: [root@idosxnpkpepttls some_mod]# puppet lookup --explain --environment lookup_rich_values_6xdoz5jm environment_key /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:49: warning: Insecure world writable dir /tmp/lookup_rich_values_6xdoz5jm/modules in PATH, mode 040777 Warning: Config file /etc/puppetlabs/puppet/hiera.yaml not found, using Hiera defaults Error: Could not run: undefined method `load_typed' for nil:NilClass [root@idosxnpkpepttls lookup_rich_values_6xdoz5jm]# cat hiera.yaml --- version: 5 hierarchy: - name: Test
Jira (PUP-6945) acceptance: lookup rich data values
Title: Message Title Eric Thompson commented on PUP-6945 Re: acceptance: lookup rich data values Henrik Lindberg, Thomas Hallgren helped me discover that it appears puppet functions are not getting loaded from and environment's /functions dir using using hiera v5 data_hash. interestingly, this worked in hiera v4 using the environment function data provider. 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-6989) Acceptance testing using TYPE=git and preserved hosts is broken
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-6989 Acceptance testing using TYPE=git and preserved hosts is broken Issue Type: Bug Assignee: Unassigned Created: 2016/12/08 8:00 AM Priority: Normal Reporter: Thomas Hallgren I tried to use the acceptance tests with TYPE=git today and ran into several problems. All tests using the latest master fails on missing semantic_puppet. This is because it is missing from the config/git/options.rb and also from the install.rb. Adding semantic_puppet to install.rb doesn't work because it lacks an install.rb of its own. The Rake command ci:list_preserved is broken. It looks for files directly under the log directory. The files however, resides one level down, under log/. Once I got ci:list_preserved working, I found that the ci:test_against_preserved_hosts is also broken. It does not propagate preserved hosts correctly (a variable named config is assumed to be present at line 123, but it isn't and instead a method is called that picks a host seemingly at random). I used the temporary fix of setting config = final_options[:hosts_file] to get around this but then it breaks with other commands. Without this functionality working, it's very hard to assert that changes made to the code will not break once the
Jira (PDB-3219) Deleting from reports spends most of the time enforcing a constraint on certnames
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3219 Deleting from reports spends most of the time enforcing a constraint on certnames Change By: Ryan Senior Team: Systems Engineering 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-3219) Deleting from reports spends most of the time enforcing a constraint on certnames
Title: Message Title Nick Walker created an issue PuppetDB / PDB-3219 Deleting from reports spends most of the time enforcing a constraint on certnames Issue Type: Bug Assignee: Unassigned Created: 2016/12/08 7:28 AM Labels: tcse Priority: Normal Reporter: Nick Walker The Problem https://explain.depesz.com/s/Ve5S QUERY PLAN -- Delete on reports (cost=2112.19..255114.61 rows=77903 width=6) (actual time=9879.603..9879.603 rows=0
Jira (PUP-6984) alias on Package/Exec resources produces misleading warning
Title: Message Title Henrik Lindberg commented on PUP-6984 Re: alias on Package/Exec resources produces misleading warning we should at least update the message to indicate that reference to title should be used - something like "change to using title if this was via alias". 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-6984) alias on Package/Exec resources produces misleading warning
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6984 alias on Package/Exec resources produces misleading warning I think I would prefer that we decide to not allow relationships to be formed based on aliases and require that the name/identity is specified in the title of the resource. Change By: Henrik Lindberg Sprint: PDS 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-6984) alias on Package/Exec resources produces misleading warning
Title: Message Title
Henrik Lindberg commented on PUP-6984
Re: alias on Package/Exec resources produces misleading warning
I think it is preferred to give the resource its identity/name in the title and instead set the command (or equivalent depending on resource) attribute.
exec { 'something' :
command => '/usr/bin/false'
}
notify {'depends on exec':
require => [Exec['something']]
}
There is history here:
PUP-5855
(the checks as such),
PUP-5839
(background), PUP-5659 (about missing validation). Given those tickets, I am not so sure this is a simple case of "also check aliases" as that leads to the problems the other tickets are about.
Jira (PUP-6988) Variable Scope of defined Types in Puppet4 changed (undocumented)
Title: Message Title Robert Heinzmann commented on PUP-6988 Re: Variable Scope of defined Types in Puppet4 changed (undocumented) Ok, thanks, Overseen 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-6988) Variable Scope of defined Types in Puppet4 changed (undocumented)
Title: Message Title R.I.Pienaar commented on PUP-6988 Re: Variable Scope of defined Types in Puppet4 changed (undocumented) this is documented, its a change in templates not defined types https://docs.puppet.com/puppet/latest/lang_updating_manifests.html#dynamic-scoping-in-erb 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.
