Jira (PUP-3043) Recursive File resources operating on large directory trees are inefficient
Title: Message Title Elyse Salberg commented on PUP-3043 Re: Recursive File resources operating on large directory trees are inefficient For people watching this ticket - take a look at PUP-1208 - it looks related and/or helpful: https://tickets.puppetlabs.com/browse/PUP-1208 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4497) Yum package provider: ensure => latest fails when obseleted packages are present
Title: Message Title Eli Young commented on PUP-4497 Re: Yum package provider: ensure => latest fails when obseleted packages are present The simple fix to this issue would be to stop processing once we read 'Obsoleting Packages', if it happens. That being said, it might be worth parsing that as well, in case the package we're trying to update is listed, and notifying the user if so. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title
Wyatt Alt commented on PDB-1448
Re: 'replace facts' failing due to foreign key constraint issue
Simon Oxwell
Thanks, those results are informative. We haven't reproduced your exact error on a running PDB yet (although we can make it happen under manufactured circumstances), but I think I have a sense of where things may be going wrong. This may be more detail than your interested in, but if you think of a structured fact as a tree, then conceptually the way we store it is as a set of key-value pairs where the values are the leaves and the keys are strings that describes a "path" from the root of the tree to the leaf. We do this to allow these paths and values to be shared among multiple facts, to reduce storage space. In the case of arrays, the index is incorporated into the path, so if your structured fact is
foo: ["a","b", {"c": "d"}]
then you can think of the data we store as looking like this (#~ is an arbitrary delimiter):
{"foo#~1": "a"
"foo#~2": "b"
"foo#~3#~c": "d"}
The downside of handling arrays this way is that an insertion or deletion at the front of an array causes an index shift for all subsequent elements as well as their children. In your case, I can see that one of those facts has at least 586 top-level array elements, each with a "collection" key and a "profiles" key that also contains some number of array elements. My guess (supported by your facter output) is that values are being inserted or deleted from that structured fact and causing the recomputation of thousands of paths with each puppet run. This will cause the replace facts command to take longer than it normally does, and consequently will widen the window for other database transactions to conflict with the update and
Jira (PUP-4497) Yum package provider: ensure => latest fails when obseleted packages are present
Title: Message Title
Eli Young updated an issue
Puppet / PUP-4497
Yum package provider: ensure => latest fails when obseleted packages are present
Change By:
Eli Young
When the yum provider has packages marked as obsoleted, the yum provider fails to ensure => latest on a package. {noformat} [root@localhost provider]# puppet apply -e "package{'puppet-agent': ensure => 'latest'}"Notice: Compiled catalog for centos-70-x64.ineu.us in environment production in 0.79 secondsError: Could not get latest version: undefined method `[]' for nil:NilClassError: /Stage[main]/Main/Package[puppet-agent]/ensure: change from 1.0.1-1.el7 to latest failed: Could not get latest version: undefined method `[]' for nil:NilClassNotice: Applied catalog in 0.38 seconds {noformat} To duplicate, bring up a CentOS7.0 VM, install puppet-agent 1.0.1
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1253) systemd service provider should support masking
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1253 systemd service provider should support masking Change By: Eric Thompson systemd knows three states for a service: enabled, disabled and masked. So far, the latter state doesn't seem to be supported by puppet's systemd service provider.The difference of disabling and masking a service is as follows: a disabled service can be started as a dependency of another service or be started manually by a user. A masked service can neither.Masking is done the same way as enabling or disabling:systemctl enable|disable|mask So kindly implement either enable => mask(ed), ensure => masked (not sure what seems more logical) or mask(ed) => true|false in the systemd service provider.Note: there's also a "unmask" command to systemctl. I figure ensure => enabled|disabled should always unmask the service additionally to enable|disable it.Manpage:http://0pointer.de/public/systemd-man/systemctl.htmlh3. QArisk: mediumprobability: medium severity: low (can use exec, etc, to work around)test level: unit Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Eric Thompson commented on PUP-4462 Re: Single backslash before $ blocks interpolation in heredoc with no escapes enabled needs more validation against 3.x, and windows Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-4462 Single backslash before $ blocks interpolation in heredoc with no escapes enabled Change By: Eric Thompson Status: Resolved Ready for Test Resolution: Fixed Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-965) facter doesn't run under jruby
Title: Message Title Kylo Ginsberg commented on FACT-965 Re: facter doesn't run under jruby Re the "hook" idea: weighing the tradeoffs, I like the generality of making facter available under jruby generally, so I'm +1 on not re-using the hook approach here. This may be something we want to remember as we swap out other libraries within puppet for native implementations. Re the long-term goal of removing facter dependencies in general, I agree that that will largely go away as we move away from the settings catalog and re-work the t/p design s.t. the master doesn't load providers. I'd suggest we take a mental note and revisit use of facter on puppetserver, once those two efforts land. But not in this ticket Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1253) systemd service provider should support masking
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1253 systemd service provider should support masking Change By: Eric Thompson systemd knows three states for a service: enabled, disabled and masked. So far, the latter state doesn't seem to be supported by puppet's systemd service provider.The difference of disabling and masking a service is as follows: a disabled service can be started as a dependency of another service or be started manually by a user. A masked service can neither.Masking is done the same way as enabling or disabling:systemctl enable|disable|mask So kindly implement either enable => mask(ed), ensure => masked (not sure what seems more logical) or mask(ed) => true|false in the systemd service provider.Note: there's also a "unmask" command to systemctl. I figure ensure => enabled|disabled should always unmask the service additionally to enable|disable it.Manpage:http://0pointer.de/public/systemd-man/systemctl.html h3. QArisk: mediumprobability: medium severity: low (can use exec, etc, to work around)test level: Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4452) Support passenger packages
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4452 Support passenger packages Change By: Steve Barlow Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4342) add acceptance to call all parser functions
Title: Message Title
Kurt Wall updated an issue
Puppet / PUP-4342
add acceptance to call all parser functions
Change By:
Kurt Wall
summarizing a conversation between myself and [~henrik.lindberg]{quote}function unit tests are faking loadingacceptance tests should ensure:"it is possible to call all built-in 3x functions""it is possible to call all built-in 4x functions"{quote}my addition: can call custom functions from modules (look in existing tests)also:review integration tests for functions to assert that a) each function is tested, and b) the integration test is not cheating.ticket spec/integration improvements as necessary. h3. QA Risk AnalysisN/A for testing tickets.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4342) add acceptance to call all parser functions
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4342 add acceptance to call all parser functions Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4419) create acceptance to ensure client does not overwrite server-set variables
Title: Message Title
Kurt Wall updated an issue
Puppet / PUP-4419
create acceptance to ensure client does not overwrite server-set variables
Change By:
Kurt Wall
from the parent (quoting [~henrik.lindberg]):{quote}After discussion with Eric Soerenson, we decided that it was best to make this an opt-in and that we are not adding a function - this for the sake of consistency between $facts, $trusted_facts, and $server_facts. This means:* At the same place where we currently set $trusted_facts we should also set $server_facts if users have opted in* The values set in $server_facts are the @server_facts set in the node by the compiler indirection + the current environment name* The user opts in by using the setting :trusted_server_facts* The setting is false by default* We issue a warning if any node parameter is overwritten{quote} h3. QA Risk AnalysisN/A for testing tickets
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4198) Add install_options feature to pip provider
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4198 Add install_options feature to pip provider Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4466) add acceptance: ensure functions can be written/execute in puppet language
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4466 add acceptance: ensure functions can be written/execute in puppet language Change By: Kurt Wall h2. QA Risk AnalysisN/A for testing tickets Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4198) Add install_options feature to pip provider
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4198 Add install_options feature to pip provider Change By: Eric Thompson Currently there is no way to submit additional options to the pip install. Using the install_options feature, we can allow additional options to be passed to pip.I have found this useful since at work we maintain a custom pypi repository that we want to hit, so passing --find-links is a requirement.h3. QArisk: mediumprobability: low (pip)severity: high (no work arounds to managing packages that require certain install/uninstall options)test level: unit -integration Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4193) Add pattern matching to the Puppet DSL
Title: Message Title
Kurt Wall updated an issue
Puppet / PUP-4193
Add pattern matching to the Puppet DSL
Change By:
Kurt Wall
UPDATE---The original request was for multiple things, and those have been broken up into :* PUP-4277 - deep matching in case options* PUP-2894 - splat assignment* this ticket (PUP-4193) - handle complex casesThis ticket adds the ability to use a lambda as a case option (more than one lambda can be used in an options list). Matching of a lambda is done by splatting the test _expression_ as arguments in a call to the lambda. The option is selected unless the result is {{false}} or {{undef}}.Example{code}notice case [2,1] { |$x, $y| { $x == $y } : { 'equal' } |$x, $y| { $x < $y } : { 'ascending' } |$x, $y| { $x > $y } : { 'descending' }}{code}This example will notice {{descending}}.The intended use case is when a case should match based on a combination of test values.ORIGINAL---ML-like languages have a language feature called 'pattern matching' (which has nothing to do with regular expressions) - they provide a very powerful control structure to make decisions based on multiple criteria; at their simplest they are a convenient shorthand for nested switch statements. They can also be used to make decisions based on the shape of data structures, and to pull values out of them, though I am not sure how much of that would be useful for Puppet.A lot of Puppet code does exactly that: nest a switch statement on one variable inside the branches of a switch statement on another variable, and a shorthand for this could simplify quite a few Puppet manifests.As an example, I attach a version of [apt::params|https://github.com/puppetlabs/puppetlabs-apt/blob/master/manifests/params.pp] from the {{puppetlabs/apt}} module that shows what this construct would look like. It cuts the size of params.pp almost in half, and more importantly makes it much clearer what values decisions are based on, and what variables get set because of those decisions.I'll also add some links to what pattern matching in other languages can do, to give a better idea of what this is all about. h2. QA Risk Analysis risk: medium (validate only) probability: medium (new feature, but similar to other langs)severity: medium (other syntax, workarounds)test layer: unit/integration
Add Comment
Jira (PUP-4198) Add install_options feature to pip provider
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4198 Add install_options feature to pip provider Change By: Eric Thompson Currently there is no way to submit additional options to the pip install. Using the install_options feature, we can allow additional options to be passed to pip.I have found this useful since at work we maintain a custom pypi repository that we want to hit, so passing --find-links is a requirement. h3. QArisk: mediumprobability: low (pip)severity: high (no work arounds to managing packages that require certain install/uninstall options)test level: unit-integration Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4418) create acceptance to ensure client does not overwrite server-set variables
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4418 create acceptance to ensure client does not overwrite server-set variables Change By: Kurt Wall h2. QA Risk AnalysisN/A for testing tickets. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4418) create acceptance to ensure client does not overwrite server-set variables
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4418 create acceptance to ensure client does not overwrite server-set variables Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4497) Yum package provider: ensure => latest fails when obseleted packages are present
Title: Message Title
Justin Lambert created an issue
Puppet / PUP-4497
Yum package provider: ensure => latest fails when obseleted packages are present
Issue Type:
Bug
Affects Versions:
PUP 4.0.0
Assignee:
Unassigned
Created:
2015/04/29 3:46 PM
Priority:
Normal
Reporter:
Justin Lambert
When the yum provider has packages marked as obsoleted, the yum provider fails to ensure => latest on a package.
[root@localhost provider]# puppet apply -e "package {'puppet-agent': ensure => 'latest'}
" Notice: Compiled catalog for centos-70-x64.ineu.us in environment production in 0.79 seconds Error: Could not get latest version: undefined method `[]' for nil:NilClass Error: /Stage[main]/Main/Package[puppet-agent]/ensure: change from 1.0.1-1.el7 to latest failed: Could not get latest version: undefined method `[]' for nil:NilClass Notice: Applied catalog in 0.38 seconds
To duplicate, bring up a CentOS7.0 VM, install puppet-agent 1.0.1
Add Comment
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Henrik Lindberg commented on PUP-4462 Re: Single backslash before $ blocks interpolation in heredoc with no escapes enabled Yes, that is covered by those examples. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3921) Craft 404 error message that includes verbiage about Puppet 4 URL changes
Title: Message Title Erik Dasher updated an issue Puppet / PUP-3921 Craft 404 error message that includes verbiage about Puppet 4 URL changes Change By: Erik Dasher QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title
Eric Thompson commented on PUP-4462
Re: Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Henrik Lindberg i had hoped that was the case, that you needed to escape the ... escaping backslash in the heredoc. but it's matching on double backslash in the output, i think. but maybe that part is escaped as well?
the ticket was mostly just about the single backslash case. eg:
$thing = "hi there"
notice(@("END INTERP"))
Variable with single backslash enjambed: \${thing}
END INTERP
so if you are saying that's covered by:
it "parses interpolated heredoc _expression_ containing escapes" do
src = "">
@("END")
Hello \\$name
Jira (PUP-3851) Remove v2.0 endpoints
Title: Message Title Erik Dasher updated an issue Puppet / PUP-3851 Remove v2.0 endpoints Change By: Erik Dasher QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4496) Initial Doc Set
Title: Message Title Steve Barlow created an issue Puppet / PUP-4496 Initial Doc Set Issue Type: Epic Assignee: Unassigned Created: 2015/04/29 3:19 PM Priority: Normal Reporter: Steve Barlow Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1253) systemd service provider should support masking
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-1253 systemd service provider should support masking Change By: Kurt Wall Assignee: QA Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-4462 Single backslash before $ blocks interpolation in heredoc with no escapes enabled Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3814) Duplicated error output
Title: Message Title Eric Thompson commented on PUP-3814 Re: Duplicated error output validated on windows2012r2-rubyx64 at SHA: 8964241 Administrator@irzmc77aybd4u9s /opt/puppet-git-repos/puppet $ cmd /c puppet apply double_trouble.pp Notice: Compiled catalog for irzmc77aybd4u9s.delivery.puppetlabs.net in environment production in 0.67 seconds Error: Parameter path failed on File[/tmp/content_file_test.Q634Dlmtime]: File paths must be fully qualified, not '/tmp/content_file_test.Q634Dlmtime' at C:/cygwin64/opt/puppet-git-repos/puppet/double_trouble.pp:1 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Kurt Wall commented on PUP-4462 Re: Single backslash before $ blocks interpolation in heredoc with no escapes enabled Validated in stable at SHA=17b75e2104c4e5615af559ed2d231dc7047f9dc3 on Windows 2012r2: C:\Program Files\Puppet Labs\Puppet\bin>puppet apply x.pp --verbose --parser fut ure Notice: Scope(Class[main]): Variable standing apart: hi there Variable enjambed: heyhi there Variable with single backslash enjambed: \hi there Variable with double backslash enjambed: \\hi there Notice: Compiled catalog for irzmc77aybd4u9s.delivery.puppetlabs.net in environm ent production in 0.56 seconds Info: Applying configuration version '1430344943'
Jira (PUP-3814) Duplicated error output
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3814 Duplicated error output Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4493) passenger packages use a buggy gem that caches environment variables
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4493 passenger packages use a buggy gem that caches environment variables Change By: Josh Cooper Summary: AIO agent CSR extension not working with passenger packages use a buggy gem that caches environment variables Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Henrik Lindberg commented on PUP-4462 Re: Single backslash before $ blocks interpolation in heredoc with no escapes enabled Reading the spec tests (and writing them) is tricky due to the multiple layers of string mangling, a double backslash may be needed to get once backslash char in the result. It took me several rounds of verification in irb before I got them right - too easy to believe testing one thing when actually testing another. I think I got it right. It may lack combinations - was that what you meant? The problem that we faced only had to do with interpolation - the interpolation logic needs to also handle finding the end of a string sequence - the added tests are specific to that. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-4374 Splatting attributes into an amended attribute block isn't supported Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title Eric Thompson commented on PUP-4374 Re: Splatting attributes into an amended attribute block isn't supported validated on windows2012r2-rubyx64 at master SHA: 8964241 Administrator@irzmc77aybd4u9s ~ $ cmd /c puppet apply splat_attrs.pp Notice: Compiled catalog for irzmc77aybd4u9s.delivery.puppetlabs.net in environment production in 0.52 seconds Notice: from a reference attribute block Notice: /Stage[main]/Main/Notify[first]/message: defined 'message' as 'from a reference attribute block' Notice: from a reference attribute block Notice: /Stage[main]/Main/Notify[extra]/message: defined 'message' as 'from a reference attribute block' Notice: Applied catalog in 0.03 seconds
Jira (PUP-4493) AIO agent CSR extension not working with passenger
Title: Message Title Josh Cooper commented on PUP-4493 Re: AIO agent CSR extension not working with passenger The issue turns out to be passenger 5.0.6, in that it caches some environment variables across requests. See https://github.com/phusion/passenger/issues/1479, which was marked as a dup of https://github.com/phusion/passenger/issues/1472. The test fails because we start a master with autosigning enabled, start a new agent, and submit a CSR. Passenger forwards several environment variables to our rack handler, HTTP_X_CLIENT_DN, HTTP_X_CLIENT_VERIFY and SSL_CLIENT_CERT. The first time passenger handles a request, HTTP_X_CLIENT_DN is not set and SSL_CLIENT_CERT is empty (since the client doesn't yet have a cert). HTTP_X_CLIENT_DN=(null) SSL_CLIENT_CERT= The master signs the cert, the agent retrieves it, and issues a catalog request using its client cert. Passenger passes in the following environment variables: HTTP_X_CLIENT_DN=/CN=a6 HTTP_X_CLIENT_VERIFY=SUCCESS SSL_CLIENT_CERT= Note the first two environment variables are correct, but the third one is empty. So puppet thinks the agent has been authenticated, but doesn't have a cert, and issues the warning (you have to bump up the log level to see it):
Jira (PUP-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4374 Splatting attributes into an amended attribute block isn't supported Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4463
split with just Regexp (unparameterized type) splits on whitespace
Change By:
Henrik Lindberg
Since 4.0.0 it is possible to give a Regexp type to split to specify the pattern to split on. Since a Regexp without a paramter parameter (pattern) has an undef/nil pattern, and this is given directly to the Ruby String#split method, it is taken to mean "split on whitepsace whitespace ".This is different that if the patter pattern is set to the an empty string, or to an empty regular _expression_ where the split is made on "nothing" - i.e. between every character.The most reasonable would be if {{Regexp}} and {{Regexp\['']}} results in the same regular _expression_ while as types they are different since Regexp accepts any other Regexp, while Regexp[''] only accepts that specific regexp.h2. QA Risk Analysis| Probability | Medium (how frequently do people splti split with {{Regexp}}?) || Impact | Low (unexpected results but no data loss) || Risk Level | Medium || Test Level | Spec |
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4462 Single backslash before $ blocks interpolation in heredoc with no escapes enabled Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes
Title: Message Title Kurt Wall commented on PUP-4385 Re: Can't write WOMANS HAT emoji with \u unicode escapes Covered in spec: spec/unit/pops/parser/lexer2_spec.rb Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes
Title: Message Title
Kurt Wall commented on PUP-4385
Re: Can't write WOMANS HAT emoji with \u unicode escapes
Verified in master at SHA=8964241dc3890af9d48335f93a015d7566193e08.
# bundle exec puppet apply -e 'notice("\u1f452 hat")'
Notice: Scope(Class[main]): ὅ2 hat
Notice: Compiled catalog for ge06qva4qg9btuu.delivery.puppetlabs.net in environment production in 0.42 seconds
Notice: Applied catalog in 0.01 seconds
# git log -1
commit 8964241dc3890af9d48335f93a015d7566193e08
Merge: 867e24c 3e2007d
Author: Henrik Lindberg
Date: Tue Apr 28 17:31:43 2015 +0200
Jira (FACT-949) Update AIO acceptance setup to skip puppetlabs-release
Title: Message Title William Hopper assigned an issue to William Hopper Facter / FACT-949 Update AIO acceptance setup to skip puppetlabs-release Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4495) Puppet 3.5.0 introduced a regression in tag filtering for catalog runs
Title: Message Title Charlie Sharpsteen commented on PUP-4495 Re: Puppet 3.5.0 introduced a regression in tag filtering for catalog runs This showed up in commit 0412515 which optimized how tags were computed and stored. The first release containing this patch was Puppet 3.5.0. Normally, when a tag foo::bar is added to a resource, the tag is recursively split by namespace to generate a list of tags:: "foo::bar", "foo", "bar". However, the refactoring missed an override in the Transaction class that short-circuited the splitting behavior for catalog applications: def handle_qualified_tags( qualified ) # The default behavior of Puppet::Util::Tagging is # to split qualified tags into parts. That would cause # qualified tags to match too broadly here. return end This override was removed in Puppet 4 as it appeared to be dead code. Add Comment
Jira (PUP-4495) Puppet 3.5.0 introduced a regression in tag filtering for catalog runs
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-4495 Puppet 3.5.0 introduced a regression in tag filtering for catalog runs Issue Type: Bug Affects Versions: PUP 4.0.0, PUP 3.7.5, PUP 3.6.2, PUP 3.5.1, PUP 3.8.0 Assignee: Kylo Ginsberg Components: Catalog Application, Client Created: 2015/04/29 2:07 PM Labels: customer support Priority: Normal Reporter: Charlie Sharpsteen Puppet 3.5.0 introduced a regression to agent tag filtering where a single tag, --tag foo::bar would be split on the namespace separator :: and expanded to a set of ['foo::bar', 'foo', 'bar']. This causes the agent to sync more resources than the user intended when tag filtering is in effect. Reproduction Case Apply the following test manifest with a tag filter of --tag test::step1:
Jira (PUP-4494) Puppet Parser does not catch issues
Title: Message Title Thomas Foster updated an issue Puppet / PUP-4494 Puppet Parser does not catch issues Change By: Thomas Foster Affects Version/s: PUP 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4494) Puppet Parser does not catch issues
Title: Message Title Thomas Foster updated an issue Puppet / PUP-4494 Puppet Parser does not catch issues Change By: Thomas Foster Summary: Puppet Parser does not catch issues with class Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4494) Puppet Parser does not catch issues with class
Title: Message Title
Thomas Foster updated an issue
Puppet / PUP-4494
Puppet Parser does not catch issues with class
Change By:
Thomas Foster
I have a class that when I run puppet parser validate on this class I do not get an error for the Package resource. I would think that puppet parser validate would give an error if this was seen. class cis_at::install inherits cis_at { ackage { 'at':ensure => $at_ensure,name => $at_package_name, }} I have also tried the following and puppet parser validate passes (The 'e' is missing for enable):class cis_at::service inherits cis_at { if ! ($service_ensure in [ 'running', 'stopped' ]){fail('service_ensure parameter must be running or stopped') } if $service_manage == true {service { 'at': ensure => $service_ensure, nable => $service_enable, name => $service_name, hastatus => true, harestart => true,} }}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4494) Puppet Parser does not catch issues with class
Title: Message Title Thomas Foster updated an issue Puppet / PUP-4494 Puppet Parser does not catch issues with class Change By: Thomas Foster Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-400) Manage hidden windows packages
Title: Message Title Ryan Gard updated an issue Puppet / PUP-400 Manage hidden windows packages Change By: Ryan Gard Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4494) Puppet Parser does not catch issues with class
Title: Message Title
Thomas Foster created an issue
Puppet / PUP-4494
Puppet Parser does not catch issues with class
Issue Type:
Bug
Affects Versions:
PUP 3.7.5, PUP 3.7.4
Assignee:
Unassigned
Created:
2015/04/29 1:31 PM
Priority:
Normal
Reporter:
Thomas Foster
I have a class that when I run puppet parser validate on this class I do not get an error for the Package resource. I would think that puppet parser validate would give an error if this was seen.
class cis_at::install inherits cis_at {
ackage { 'at': ensure => $at_ensure, name => $at_package_name, }
}
Add Comment
Jira (HI-347) spec edge cases to ensure hiera lookup doesn't contain values from outside of hierarchy
Title: Message Title Eric Thompson updated an issue Hiera / HI-347 spec edge cases to ensure hiera lookup doesn't contain values from outside of hierarchy Change By: Eric Thompson Sprint: Language 2015-05- 13 27 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3539) add additional spec tests to cover globbing ACL matches in fileserver.conf
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3539 add additional spec tests to cover globbing ACL matches in fileserver.conf Change By: Eric Thompson Sprint: Language 2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4463 split with just Regexp (unparameterized type) splits on whitespace Change By: Steve Barlow Scope Change Reason: Found by Nick Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4458) Refactor validation of 4.x parameter signatures
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4458 Refactor validation of 4.x parameter signatures Change By: Steve Barlow Scope Change Reason: Came out of improving error messages ticket - broke it into multiple tickets Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4438) Add required_repeated_param to 4.x function API
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4438 Add required_repeated_param to 4.x function API Change By: Steve Barlow Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4461) manifest changes are ignored when using hiera_include
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4461 manifest changes are ignored when using hiera_include Change By: Steve Barlow Sprint: Language 2015-04-29 , Language 2015-05-13 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4462 Single backslash before $ blocks interpolation in heredoc with no escapes enabled Change By: Steve Barlow Sprint: Language 2015-04-29 , Language 2015-05-13 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4385 Can't write WOMANS HAT emoji with \u unicode escapes Change By: Steve Barlow Sprint: Language 2015-04-29 , Language 2015-05-13 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2315) function call error message about mis-matched arguments is hard to understand
Title: Message Title Steve Barlow updated an issue Puppet / PUP-2315 function call error message about mis-matched arguments is hard to understand Change By: Steve Barlow Sprint: Language 2015-03-04, Language 2015-03-18, Language 2015-04-29 , Language 2015-05-13 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4458) Refactor validation of 4.x parameter signatures
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4458 Refactor validation of 4.x parameter signatures Change By: Steve Barlow Sprint: Language 2015-04-29 , Language 2015-05-13 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2080) Support functions written in pp
Title: Message Title Steve Barlow updated an issue Puppet / PUP-2080 Support functions written in pp Change By: Steve Barlow Sprint: Week 2014-4-02 to 2014-4-09, Week 2014-4-09 to 2014-4-16, Language 2015-04-29 , Language 2015-05-13 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4374 Splatting attributes into an amended attribute block isn't supported Change By: Steve Barlow Sprint: Language 2015-04-29 , Language 2015-05-13 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4463 split with just Regexp (unparameterized type) splits on whitespace Change By: Steve Barlow Sprint: Language 2015-04-29 , Language 2015-05-13 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3814) Duplicated error output
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3814 Duplicated error output Change By: Steve Barlow Sprint: Language 2015-04-29 , Language 2015-05-13 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4193) Add pattern matching to the Puppet DSL
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4193 Add pattern matching to the Puppet DSL Change By: Steve Barlow Sprint: Language 2015-04-29 , Language 2015-05-13 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title Steve Barlow updated an issue Puppet / PUP-2630 Server-set global variables like $::environment get overwritten by client facts Change By: Steve Barlow Sprint: Language 2015-04-29 , Language 2015-05-13 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4193) Add pattern matching to the Puppet DSL
Title: Message Title Steve Barlow assigned an issue to Eric Sorenson Puppet / PUP-4193 Add pattern matching to the Puppet DSL Change By: Steve Barlow Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4475) Add explain-ability to the lookup and data provider APIs
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4475 Add explain-ability to the lookup and data provider APIs Change By: Steve Barlow Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4385 Can't write WOMANS HAT emoji with \u unicode escapes Change By: Kurt Wall Assignee: QA Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-4463 split with just Regexp (unparameterized type) splits on whitespace Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title
Kurt Wall updated an issue
Puppet / PUP-4463
split with just Regexp (unparameterized type) splits on whitespace
Change By:
Kurt Wall
Since 4.0.0 it is possible to give a Regexp type to split () to specify the pattern on which to split on . Since a Regexp without a parameter paramter (pattern) has an undef/nil pattern, and this is given directly to the Ruby String#split method, it is taken to mean "split on whitespace whitepsace ".This is different that if the pattern patter is set to the an empty string, or to an empty regular _expression_ where the split is made on "nothing" - i.e. between every character.The most reasonable behavior would be if {{Regexp}} and {{Regexp\['']}} results in the same regular _expression_ while as types they are different since Regexp accepts any other Regexp, while Regexp[''] only accepts that specific regexp. h2. QA Risk Analysis| Probability | Medium (how frequently do people splti with {{Regexp}}?) || Impact | Low (unexpected results but no data loss) || Risk Level | Medium || Test Level | Spec |
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module A basic module pipeline is up here (with Ruby 1.8). I will enable it (and iterate on it) once dev is ready to go! Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4463 split with just Regexp (unparameterized type) splits on whitespace Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4463
split with just Regexp (unparameterized type) splits on whitespace
Change By:
Eric Thompson
Since 4.0.0 it is possible to give a Regexp type to split () to specify the pattern on which to split on . Since a Regexp without a paramter parameter (pattern) has an undef/nil pattern, and this is given directly to the Ruby String#split method, it is taken to mean "split on whitepsace whitespace ".This is different that if the patter pattern is set to the an empty string, or to an empty regular _expression_ where the split is made on "nothing" - i.e. between every character.The most reasonable behavior would be if {{Regexp}} and {{Regexp\['']}} results in the same regular _expression_ while as types they are different since Regexp accepts any other Regexp, while Regexp[''] only accepts that specific regexp.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4463 split with just Regexp (unparameterized type) splits on whitespace Change By: Kurt Wall QA Contact: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4463 split with just Regexp (unparameterized type) splits on whitespace Change By: Kurt Wall Assignee: Eric Thompson Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-587) Add API support for CORS
Title: Message Title Bruce Lysik commented on PDB-587 Re: Add API support for CORS Blocker bug is closed. Is it possible for this to be added now? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4463 split with just Regexp (unparameterized type) splits on whitespace Change By: Eric Thompson Assignee: QA Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-4462 Single backslash before $ blocks interpolation in heredoc with no escapes enabled Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Eric Thompson commented on PUP-4462 Re: Single backslash before $ blocks interpolation in heredoc with no escapes enabled validated on ubuntu14.04 at master SHA: 8964241 [root@fv1nemlp2jj6fpm puppet]# puppet apply interp_heredoc.pp Notice: Scope(Class[main]): Variable standing apart: hi there Variable enjambed: heyhi there Variable with single backslash enjambed: \hi there Variable with double backslash enjambed: \\hi there Notice: Compiled catalog for fv1nemlp2jj6fpm.delivery.puppetlabs.net in environment production in 0.40 seconds Notice: Applied catalog in 0.02 seconds [root@fv1nemlp2jj6fpm puppet]# cat interp_heredoc.pp $thing = "hi there"
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4462 Single backslash before $ blocks interpolation in heredoc with no escapes enabled Change By: Eric Thompson QA Contact: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4462 Single backslash before $ blocks interpolation in heredoc with no escapes enabled Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Eric Thompson commented on PUP-4462 Re: Single backslash before $ blocks interpolation in heredoc with no escapes enabled Henrik Lindberg it looks like the spec tests for the PR for this is testing the escaped backslash case (two ) but not the single escaping of the interpolation (since with @END escapes are turned off)? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4462
Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Change By:
Eric Thompson
Ran:{code}$thing = "hi there"notice(@("END INTERP"))This string should be able to interpolate variables, and all backslashes shouldbe interpreted as plain old literal backslashes.Variable standing apart: ${thing}Variable enjambed: hey${thing}Variable with single backslash enjambed: \${thing}Variable with double backslash enjambed: \\${thing}END INTERP{code}The single backslash before the $ causes a problem. I'm pretty sure this is against [the specification of heredocs|https://github.com/puppetlabs/puppet-specifications/blob/master/language/heredoc.md].Actual result:{code}Notice: Scope(Class[main]): This string should be able to interpolate variables, and all backslashes shouldbe interpreted as plain old literal backslashes.Variable standing apart: hi thereVariable enjambed: heyhi thereVariable with single backslash enjambed: \${thing}Variable with double backslash enjambed: \\hi there{code}Expected result: {code}Notice: Scope(Class[main]): This string should be able to interpolate variables, and all backslashes shouldbe interpreted as plain old literal backslashes.Variable standing apart: hi thereVariable enjambed: heyhi thereVariable with single backslash enjambed: \hi thereVariable with double backslash enjambed: \\hi there{code}3.7.5 and 4.0.0 behave identically. In addition, if any escape (other than '$' escapes) are turned on, it also turns on escaping of '$'. This is caused by the same faulty logic.h3. QArisk: medium (validate only)probability: low (single backslash directly before interpolation in pp heredoc)severity: medium (obvious issue, workarounds)test level: unit
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4462
Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Change By:
Eric Thompson
Ran:{code}$thing = "hi there"notice(@("END INTERP"))This string should be able to interpolate variables, and all backslashes shouldbe interpreted as plain old literal backslashes.Variable standing apart: ${thing}Variable enjambed: hey${thing}Variable with single backslash enjambed: \${thing}Variable with double backslash enjambed: \\${thing}END INTERP{code}The single backslash before the $ causes a problem. I'm pretty sure this is against [the specification of heredocs|https://github.com/puppetlabs/puppet-specifications/blob/master/language/heredoc.md].Actual result:{code}Notice: Scope(Class[main]): This string should be able to interpolate variables, and all backslashes shouldbe interpreted as plain old literal backslashes.Variable standing apart: hi thereVariable enjambed: heyhi thereVariable with single backslash enjambed: \${thing}Variable with double backslash enjambed: \\hi there{code}Expected result: {code}Notice: Scope(Class[main]): This string should be able to interpolate variables, and all backslashes shouldbe interpreted as plain old literal backslashes.Variable standing apart: hi thereVariable enjambed: heyhi thereVariable with single backslash enjambed: \hi thereVariable with double backslash enjambed: \\hi there{code}3.7.5 and 4.0.0 behave identically. In addition, if any escape (other than '$' escapes) are turned on, it also turns on escaping of '$'. This is caused by the same faulty logic. h3. QArisk: medium (validate only)probability: low (single backslash directly before interpolation in pp heredoc)severity: medium (obvious issue, workarounds)test level:
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4462 Single backslash before $ blocks interpolation in heredoc with no escapes enabled Change By: Eric Thompson Assignee: QA Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4461) manifest changes are ignored when using hiera_include
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-4461 manifest changes are ignored when using hiera_include Change By: Eric Thompson Assignee: Eric Thompson QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4461) manifest changes are ignored when using hiera_include
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4461 manifest changes are ignored when using hiera_include Change By: Eric Thompson QA Contact: Erik Dasher Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4461) manifest changes are ignored when using hiera_include
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4461 manifest changes are ignored when using hiera_include Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4461) manifest changes are ignored when using hiera_include
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4461 manifest changes are ignored when using hiera_include Change By: Eric Thompson I'm experimenting with puppetserver 2 / puppet-agent 1 and I'm running into an issue where changes to manifests don't get picked up by the server.When I'm making changes to a manifest after starting puppetserver it is working for the first 2 or 3 changes I make.After that new changes don't get picked up anymore until I restart puppetserver.I can reproduce that behavior. For an example session see: https://gist.github.com/roman-mueller/cf776fd180a085a551c2I'm running:CentOS 7.0.1406 (but also reproduced it on CentOS 7.1.1503)puppetserver-2.0.0-1.el7.noarchpuppet-agent-1.0.0-1.el7.x86_64I've set "environment_timeout = 0" in the "production/environment.conf" - which also should be the default.Everything else is kept on default settings too.I've committed my experimental Vagrant environment here:https://github.com/roman-mueller/puppet4-sandboxNote that this is using vboxsf but I get the same behavior with local files. When I'm running strace on the puppetserver PID I can see for the first 2 puppet agent runs that global/manifests/init.pp gets accessed.After that it is not getting read anymore.I've also waited 45 minutes, but still the change was not picked up.Only a restart of the puppetserver fixes it at that point.h3. QArisk: medium ( manual validate only for now )probability: medium (hiera_include picking up manifest changes downstream only)severity: medium (changes not picked up, confusing but possibly not blocking)test level: acceptance (we should update existing acceptance to ensure an altered manifest is picked up) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4461) manifest changes are ignored when using hiera_include
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4461 manifest changes are ignored when using hiera_include Change By: Eric Thompson I'm experimenting with puppetserver 2 / puppet-agent 1 and I'm running into an issue where changes to manifests don't get picked up by the server.When I'm making changes to a manifest after starting puppetserver it is working for the first 2 or 3 changes I make.After that new changes don't get picked up anymore until I restart puppetserver.I can reproduce that behavior. For an example session see: https://gist.github.com/roman-mueller/cf776fd180a085a551c2I'm running:CentOS 7.0.1406 (but also reproduced it on CentOS 7.1.1503)puppetserver-2.0.0-1.el7.noarchpuppet-agent-1.0.0-1.el7.x86_64I've set "environment_timeout = 0" in the "production/environment.conf" - which also should be the default.Everything else is kept on default settings too.I've committed my experimental Vagrant environment here:https://github.com/roman-mueller/puppet4-sandboxNote that this is using vboxsf but I get the same behavior with local files. When I'm running strace on the puppetserver PID I can see for the first 2 puppet agent runs that global/manifests/init.pp gets accessed.After that it is not getting read anymore.I've also waited 45 minutes, but still the change was not picked up.Only a restart of the puppetserver fixes it at that point. h3. QArisk: medium (validate)probability: medium (hiera_include picking up manifest changes downstream only)severity: medium (changes not picked up, confusing but possibly not blocking)test level: Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4461) manifest changes are ignored when using hiera_include
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4461 manifest changes are ignored when using hiera_include Change By: Eric Thompson Assignee: QA Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3814) Duplicated error output
Title: Message Title
Eric Thompson commented on PUP-3814
Re: Duplicated error output
validated follow-up commit on ubuntu14.04 at SHA: 8964241
[root@fv1nemlp2jj6fpm ~]# puppet apply double_error.pp
Notice: Compiled catalog for fv1nemlp2jj6fpm.delivery.puppetlabs.net in environment production in 0.46 seconds
Error: Validation of File[/tmp/content_file_test.Q634Dlmtime] failed: You cannot specify content when using checksum 'mtime' at /root/double_error.pp:1
[root@fv1nemlp2jj6fpm ~]# cat double_error.pp
file { '/tmp/content_file_test.Q634Dlmtime': content => 'This is the test file content', ensure => present, checksum => mtime }
Add Comment
This message was sent by Atlassian JIR
Jira (PUP-3814) Duplicated error output
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-3814 Duplicated error output Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3814) Duplicated error output
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3814 Duplicated error output Change By: Eric Thompson Assignee: QA Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-4385 Can't write WOMANS HAT emoji with \u unicode escapes Change By: Eric Thompson Assignee: Eric Thompson QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4385 Can't write WOMANS HAT emoji with \u unicode escapes Change By: Eric Thompson Assignee: QA Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-4374 Splatting attributes into an amended attribute block isn't supported Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title
Eric Thompson commented on PUP-4374
Re: Splatting attributes into an amended attribute block isn't supported
validated on ubuntu14.04 at master SHA:
[root@fv1nemlp2jj6fpm ~]# puppet apply splat_attrs.pp
Notice: Compiled catalog for fv1nemlp2jj6fpm.delivery.puppetlabs.net in environment production in 0.38 seconds
Notice: from a reference attribute block
Notice: /Stage[main]/Main/Notify[first]/message: defined 'message' as 'from a reference attribute block'
Notice: from a reference attribute block
Notice: /Stage[main]/Main/Notify[extra]/message: defined 'message' as 'from a reference attribute block'
Notice: Applied catalog in 0.01 seconds
[root@fv1nemlp2jj6fpm ~]# cat splat_attrs.pp
notify {'first':}
$myattrs = {"message" => "from a re
Jira (PUP-4493) AIO agent CSR extension not working with passenger
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-4493 AIO agent CSR extension not working with passenger Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
