Jira (PUP-7480) gettext-setup isn't stubbed enough
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7480 gettext-setup isn't stubbed enough Issue Type: Bug Affects Versions: PUP 4.10.0 Assignee: Unassigned Created: 2017/04/27 10:57 PM Priority: Major Reporter: Thomas Hallgren In PUP-7116 , the gettext-setup is made optional by trapping a failed require 'gettext-setup' and stubbing the _() method. That is however not enough since the method n_() is referenced in several places in the code-base. Add Comment
Jira (PUP-7479) ENC-enforced environment makes `puppet lookup` environment simulation difficult
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7479 ENC-enforced environment makes `puppet lookup` environment simulation difficult Change By: Eric Thompson QA Risk Assessment Reason: could be automated in an integration test in rspec Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7479) ENC-enforced environment makes `puppet lookup` environment simulation difficult
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7479 ENC-enforced environment makes `puppet lookup` environment simulation difficult Change By: Eric Thompson QA Risk Assessment: Needs Assessment Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7475) A regex literal for matching backslashes causes a lexer error
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7475 A regex literal for matching backslashes causes a lexer error Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7473) remove dead code in Puppet::Type::instances
Title: Message Title Ethan Brown commented on PUP-7473 Re: remove dead code in Puppet::Type::instances Merged to master in https://github.com/puppetlabs/puppet/commit/6c5b7043896977e51587df815bd8c9dbb071ace3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7472) unable to have puppet master listen on both IPv4 and IPv6
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7472 unable to have puppet master listen on both IPv4 and IPv6 Change By: Moses Mendoza Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7472) unable to have puppet master listen on both IPv4 and IPv6
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7472 unable to have puppet master listen on both IPv4 and IPv6 Change By: Moses Mendoza Sprint: Agent Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7472) unable to have puppet master listen on both IPv4 and IPv6
Title: Message Title Moses Mendoza commented on PUP-7472 Re: unable to have puppet master listen on both IPv4 and IPv6 thanks Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7479) ENC-enforced environment makes `puppet lookup` environment simulation difficult
Title: Message Title Thomas Kishel commented on PUP-7479 Re: ENC-enforced environment makes `puppet lookup` environment simulation difficult I was about to submit a similar ticket, and I'd hate to waste formatted text ... The puppet lookup environment parameter does not override the server-specified node environment unless the node is in the 'Agent-specified environment' node group. This matches the behavior of puppet agent on a node, but is not documented (in the command help, and in the explain output} and is possibly unexpected when using puppet lookup. [root@pe-201711-master ~]# puppet lookup --node pe-201711-agent test --environment development --explain Searching for "lookup_options" Searching for "test" Global Data Provider (hiera configuration version 5) Using configuration "/etc/puppetlabs/puppet/hiera.yaml" Hierarchy entry "v5 global common heiradata" Path "/etc/puppetlabs/puppet/hieradata/common.yaml" Original path: "common.yaml" Path not found
Jira (PUP-6872) allow global hiera and lookup in different environments
Title: Message Title Gary Larizza commented on PUP-6872 Re: allow global hiera and lookup in different environments You can only pass the environment if the ENC is not enforcing an environment (or the ENC is allowing agent-specified environments). See the ticket I opened this morning: https://tickets.puppetlabs.com/browse/PUP-7479 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-67) Issue with markdown rendering of code using ~~~
Title: Message Title Jean Bond commented on PDOC-67 Re: Issue with markdown rendering of code using ~~~ It does, Henrik Lindberg! Language highlighting was added last year, and I love it a lot. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-346) Remove Windows platform specific gems win32console / win32-dir from Gemfile
Title: Message Title Moses Mendoza commented on HI-346 Re: Remove Windows platform specific gems win32console / win32-dir from Gemfile merged to stable at https://github.com/puppetlabs/hiera/commit/7dd570e3877830943a4ca6a94733013bb36837ea Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7475) A regex literal for matching backslashes causes a lexer error
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7475 A regex literal for matching backslashes causes a lexer error Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3171) query compilation is very slow for queries with giant arrays
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3171 query compilation is very slow for queries with giant arrays Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7472) unable to have puppet master listen on both IPv4 and IPv6
Title: Message Title Florian Klink commented on PUP-7472 Re: unable to have puppet master listen on both IPv4 and IPv6 Yes, the debian puppet-master package. The puppet-master-passenger package is not installed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7479) ENC-enforced environment makes `puppet lookup` environment simulation difficult
Title: Message Title
Gary Larizza updated an issue
Puppet / PUP-7479
ENC-enforced environment makes `puppet lookup` environment simulation difficult
Change By:
Gary Larizza
The use case here is that we're trying to move people away from using the {{hiera}} binary to simulate/debug lookups to using {{puppet lookup}}. With {{hiera}} you could pass environment variables that matched whatever "variables" were in hiera.yaml to simulate what Puppet would provide, so doing: {{hiera testkey environment=test}} would allow us to simulate this lookup in the test environment.When we tried doing that with: {{puppet lookup testkey - -environment test}} we found that we were still getting values from the production environment. This is because {{puppet lookup}} (even without using {{--compile}}) will pull down a node object for whatever node is being targeted, and that means it's going through paths of indirection and ultimately the ENC. If the ENC is enforcing an environment, then {{puppet lookup}} is bound to that environment. In our case above (using the Console), setting the node to a nodegroup enforcing "Agent-specified environment" allowed us to simulate a lookup in another environment properly.I'm marking this as an "Improvement" instead of a bug, but the reality is that it's a pretty major use-ability issue because being able to simulate lookups decoupled from the ENC is a pretty common exercise for people debugging Hiera data.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the
Jira (PUP-7479) ENC-enforced environment makes `puppet lookup` environment simulation difficult
Title: Message Title
Gary Larizza updated an issue
Puppet / PUP-7479
ENC-enforced environment makes `puppet lookup` environment simulation difficult
Change By:
Gary Larizza
The use case here is that we're trying to move people away from using the {{hiera}} binary to simulate/debug lookups to using {{puppet lookup}}. With {{hiera}} you could pass environment variables that matched whatever "variables" were in hiera.yaml to simulate what Puppet would provide, so doing: {{hiera testkey environment=test}} would allow us to simulate this lookup in the test environment.When we tried doing that with: {{ puppet lookup testkey - - environment test }} we found that we were still getting values from the production environment. This is because {{puppet lookup}} (even without using {{- -compile}}) will pull down a node object for whatever node is being targeted, and that means it's going through paths of indirection and ultimately the ENC. If the ENC is enforcing an environment, then {{puppet lookup}} is bound to that environment. In our case above (using the Console), setting the node to a nodegroup enforcing "Agent-specified environment" allowed us to simulate a lookup in another environment properly.I'm marking this as an "Improvement" instead of a bug, but the reality is that it's a pretty major use-ability issue because being able to simulate lookups decoupled from the ENC is a pretty common exercise for people debugging Hiera data.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to
Jira (PUP-7479) ENC-enforced environment makes `puppet lookup` environment simulation difficult
Title: Message Title
Gary Larizza updated an issue
Puppet / PUP-7479
ENC-enforced environment makes `puppet lookup` environment simulation difficult
Change By:
Gary Larizza
The use case here is that we're trying to move people away from using the {{hiera}} binary to simulate/debug lookups to using {{puppet lookup}}. With ` {{ hiera ` }} you could pass environment variables that matched whatever "variables" were in hiera.yaml to simulate what Puppet would provide, so doing: ` {{ hiera testkey environment=test ` }} would allow us to simulate this lookup in the test environment.When we tried doing that with: puppet lookup testkey --environment test we found that we were still getting values from the production environment. This is because ` {{ puppet lookup ` }} (even without using ` {{ --compile ` }} ) will pull down a node object for whatever node is being targeted, and that means it's going through paths of indirection and ultimately the ENC. If the ENC is enforcing an environment, then ` {{ puppet lookup ` }} is bound to that environment. In our case above (using the Console), setting the node to a nodegroup enforcing "Agent-specified environment" allowed us to simulate a lookup in another environment properly.I'm marking this as an "Improvement" instead of a bug, but the reality is that it's a pretty major use-ability issue because being able to simulate lookups decoupled from the ENC is a pretty common exercise for people debugging Hiera data.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this
Jira (FACT-1615) move and update 2 regression acceptance tests into the custom_facts directory and update the loading libfacter into ruby test
Title: Message Title Eric Delaney updated an issue Facter / FACT-1615 move and update 2 regression acceptance tests into the custom_facts directory and update the loading libfacter into ruby test Change By: Eric Delaney Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7479) ENC-enforced environment makes `puppet lookup` environment simulation difficult
Title: Message Title
Gary Larizza updated an issue
Puppet / PUP-7479
ENC-enforced environment makes `puppet lookup` environment simulation difficult
Change By:
Gary Larizza
The use case here is that we're trying to move people away from using the {{hiera}} binary to simulate/debug lookups to using {{puppet lookup}}. With {{hiera}} you could pass environment variables that matched whatever "variables" were in hiera.yaml to simulate what Puppet would provide, so doing: {{hiera testkey environment=test}} would allow us to simulate this lookup in the test environment.When we tried doing that with: puppet lookup testkey --environment test we found that we were still getting values from the production environment. This is because {{puppet lookup}} (even without using {{--compile}}) will pull down a node object for whatever node is being targeted, and that means it's going through paths of indirection and ultimately the ENC. If the ENC is enforcing an environment, then {{puppet lookup}} is bound to that environment. In our case above (using the Console), setting the node to a nodegroup enforcing "Agent-specified environment" allowed us to simulate a lookup in another environment properly.I'm marking this as an "Improvement" instead of a bug, but the reality is that it's a pretty major use-ability issue because being able to simulate lookups decoupled from the ENC is a pretty common exercise for people debugging Hiera data.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google
Jira (FACT-1616) Updated OS specific fact tests
Title: Message Title Eric Delaney updated an issue Facter / FACT-1616 Updated OS specific fact tests Change By: Eric Delaney Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7479) ENC-enforced environment makes `puppet lookup` environment simulation difficult
Title: Message Title
Gary Larizza updated an issue
Puppet / PUP-7479
ENC-enforced environment makes `puppet lookup` environment simulation difficult
Change By:
Gary Larizza
The use case here is that we're trying to move people away from using the {{hiera}} binary to simulate/debug lookups to using {{puppet lookup}}. With {{hiera}} you could pass environment variables that matched whatever "variables" were in hiera.yaml to simulate what Puppet would provide, so doing: {{hiera testkey environment=test}} would allow us to simulate this lookup in the test environment.When we tried doing that with: {{puppet lookup testkey --environment test}} we found that we were still getting values from the production environment. This is because {{puppet lookup}} (even without using {{--compile}}) will pull down a node object for whatever node is being targeted, and that means it's going through paths of indirection and ultimately the ENC. If the ENC is enforcing an environment, then {{puppet lookup}} is bound to that environment. In our case above (using the Console), setting the node to a nodegroup enforcing "Agent-specified environment" allowed us to simulate a lookup in another environment properly.I'm marking this as an "Improvement" instead of a bug, but the reality is that it's a pretty major use-ability issue because being able to simulate lookups decoupled from the ENC is a pretty common exercise for people debugging Hiera data.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google
Jira (PDOC-67) Issue with markdown rendering of code using ~~~
Title: Message Title Henrik Lindberg commented on PDOC-67 Re: Issue with markdown rendering of code using ~~~ Jean Bond thanks - sounds good. Does it work to use ```puppet or ```ruby etc to tell the renderer about language/syntax coloring ? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1614) move and update verify fact tests into fact directory
Title: Message Title Eric Delaney updated an issue Facter / FACT-1614 move and update verify fact tests into fact directory Change By: Eric Delaney Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7479) ENC-enforced environment makes `puppet lookup` environment simulation difficult
Title: Message Title
Gary Larizza updated an issue
Puppet / PUP-7479
ENC-enforced environment makes `puppet lookup` environment simulation difficult
Change By:
Gary Larizza
The use case here is that we're trying to move people away from using the ` {{ hiera ` }} binary to simulate/debug lookups to using ` {{ puppet lookup ` }} . With `hiera` you could pass environment variables that matched whatever "variables" were in hiera.yaml to simulate what Puppet would provide, so doing: `hiera testkey environment=test` would allow us to simulate this lookup in the test environment.When we tried doing that with: ` puppet lookup testkey --environment test ` we found that we were still getting values from the production environment. This is because `puppet lookup` (even without using `--compile`) will pull down a node object for whatever node is being targeted, and that means it's going through paths of indirection and ultimately the ENC. If the ENC is enforcing an environment, then `puppet lookup` is bound to that environment. In our case above (using the Console), setting the node to a nodegroup enforcing "Agent-specified environment" allowed us to simulate a lookup in another environment properly.I'm marking this as an "Improvement" instead of a bug, but the reality is that it's a pretty major use-ability issue because being able to simulate lookups decoupled from the ENC is a pretty common exercise for people debugging Hiera data.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to
Jira (PUP-7479) ENC-enforced environment makes `puppet lookup` environment simulation difficult
Title: Message Title Gary Larizza created an issue Puppet / PUP-7479 ENC-enforced environment makes `puppet lookup` environment simulation difficult Issue Type: Improvement Affects Versions: PUP 4.9.4 Assignee: Henrik Lindberg Components: CLI Created: 2017/04/27 11:28 AM Priority: Normal Reporter: Gary Larizza The use case here is that we're trying to move people away from using the `hiera` binary to simulate/debug lookups to using `puppet lookup`. With `hiera` you could pass environment variables that matched whatever "variables" were in hiera.yaml to simulate what Puppet would provide, so doing: `hiera testkey environment=test` would allow us to simulate this lookup in the test environment. When we tried doing that with: `puppet lookup testkey - environment test` we found that we were still getting values from the production environment. This is because `puppet lookup` (even without using ` -compile`) will pull down a node object for whatever node is being targeted, and that means it's going through paths of indirection and ultimately the ENC. If the ENC is enforcing an environment, then `puppet lookup` is bound to that environment. In our case above (using the Console), setting the node to a nodegroup
Jira (PDB-3486) Update HakariCP to a more modern version than 2.4.3
Title: Message Title Nick Walker created an issue PuppetDB / PDB-3486 Update HakariCP to a more modern version than 2.4.3 Issue Type: Improvement Assignee: Unassigned Created: 2017/04/27 10:57 AM Priority: Normal Reporter: Nick Walker The Problem We're running a version of HakariCP from December 2015. The Solution Upgrade to a newer version https://github.com/brettwooldridge/HikariCP/releases Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7478) improve debug message when failing to load a feature
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7478 improve debug message when failing to load a feature Change By: Josh Cooper Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7478) improve debug message when failing to load a feature
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7478 improve debug message when failing to load a feature Change By: Josh Cooper Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7478) improve debug message when failing to load a feature
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7478 improve debug message when failing to load a feature Change By: Josh Cooper Release Notes Summary: Provide additional information when a feature is not suitable on a given platform Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6872) allow global hiera and lookup in different environments
Title: Message Title Eric Thompson commented on PUP-6872 Re: allow global hiera and lookup in different environments hi Stefan Pijnappels. you can specify an environment to the lookup subcommand similar to most other puppet subcommands like this: puppet lookup --environment new_environment if the customer is not aware, one can receive an explanation of where values are found (or not) via the --explain option to the same subcommand. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7475) A regex literal for matching backslashes causes a lexer error
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-7475
A regex literal for matching backslashes causes a lexer error
Change By:
Charlie Sharpsteen
Attempting to declare a regex literal for matching a single backslash results in a lexer error when the manifest is parsed.h2. Reproduction CaseApply the following manifest which multiplies backslashes within a windows path:{code:puppet}$win_path = "c:\\some\\path"$backslash = /\\/$escaped_path = regsubst($win_path, $backslash, '\ 1 \ 1 \\ ', 'G')notice("Escaped path is: ${escaped_path}"){code}h3. OutcomeApplying the manifest results in a parser error coming from the lexer code.{noformat}# puppet apply regex_test.pp --traceError: Could not parse for environment production: no implicit conversion of nil into String on node pe-201643-master.puppetdebug.vlan/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/parser/lexer2.rb:380:in `+'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/parser/lexer2.rb:380:in `block in initialize'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/parser/lexer2.rb:710:in `call'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/parser/lexer2.rb:710:in `scan'/opt/puppetlabs/puppet/lib/ruby/2.1.0/racc/parser.rb:319:in `_racc_yyparse_c'/opt/puppetlabs/puppet/lib/ruby/2.1.0/racc/parser.rb:319:in `yyparse'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/parser/parser_support.rb:240:in `_parse'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/parser/parser_support.rb:84:in `parse_file'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/parser/evaluating_parser.rb:41:in `parse_file'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/e4_parser_adapter.rb:31:in `parse'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/node/environment.rb:512:in `perform_initial_import'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/node/environment.rb:236:in `known_resource_types'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/compiler.rb:762:in `block in initvars'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:241:in `override'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/compiler.rb:760:in `initvars'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/compiler.rb:422:in `initialize'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/compiler.rb:33:in `new'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/compiler.rb:33:in `compile'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:266:in `block (2 levels) in compile'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in `profile'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in `profile'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:264:in `block in compile'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:223:in `block in benchmark'/opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:222:in `benchmark'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:262:in
Jira (PDB-3485) Maint/master/speed up include total
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3485 Maint/master/speed up include total Issue Type: Bug Assignee: Unassigned Created: 2017/04/27 9:59 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-7472) unable to have puppet master listen on both IPv4 and IPv6
Title: Message Title Moses Mendoza commented on PUP-7472 Re: unable to have puppet master listen on both IPv4 and IPv6 Oh interesting so this is the debian puppet-master package running? Do you also have the puppetmaster-passenger package installed? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7467) Puppet removes non-managed entries from crontabs if non-ascii character found
Title: Message Title Larsen commented on PUP-7467 Re: Puppet removes non-managed entries from crontabs if non-ascii character found Hi Moses. For trying this, I would have to setup a testing environment first which would take some time. As you might imagine, even if this was fixed in 4.10, migrating all servers to Puppet 4 would not be an easy task (although I have already started work on that), therefore a solution for the Debian version would be more useful. Though, I have mitigated the problem (for now) by removing the umlaut characters and now need to pay attention to either not insert any umlauts or use "reset_system_locale=false" with salt. Long story short: There is no real need for me to get this fixed, so if you think this might have been fixed in 4.10, it might probably be best to close the bug. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6694) The Puppet Data type should be limited to JSON types.
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-6694 The Puppet Data type should be limited to JSON types. Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7472) unable to have puppet master listen on both IPv4 and IPv6
Title: Message Title Florian Klink commented on PUP-7472 Re: unable to have puppet master listen on both IPv4 and IPv6 This was done on a Debian Stretch, by using the packages provided there. It seems like /lib/systemd/system/puppet-master.service starts /usr/bin/puppet master, which looks like bin/puppet the git repository. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7467) Puppet removes non-managed entries from crontabs if non-ascii character found
Title: Message Title Moses Mendoza commented on PUP-7467 Re: Puppet removes non-managed entries from crontabs if non-ascii character found Larsen I think there's a good chance this has been fixed in a recent version of Puppet. Can you try installing Puppet 4.10 from the puppetlabs repos and seeing if this issue persists for you? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7467) Puppet removes non-managed entries from crontabs if non-ascii character found
Title: Message Title Moses Mendoza commented on PUP-7467 Re: Puppet removes non-managed entries from crontabs if non-ascii character found thanks for filing Larsen Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7472) unable to have puppet master listen on both IPv4 and IPv6
Title: Message Title Moses Mendoza commented on PUP-7472 Re: unable to have puppet master listen on both IPv4 and IPv6 thanks for Filing Florian Klink. Is your puppet master running via Puppet Server? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7476) Unable to Install Puppetserver on RHEL 7
Title: Message Title Moses Mendoza commented on PUP-7476 Re: Unable to Install Puppetserver on RHEL 7 Hi Ashok Rajendran - it looks like you're trying to install Puppet Enterprise. Are you a current Puppet Enterprise customer? If so, are you able to open a ticket at our support portal, support.puppet.com? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7478) improve debug message when failing to load a feature
Title: Message Title David Schmitt created an issue Puppet / PUP-7478 improve debug message when failing to load a feature Issue Type: Improvement Assignee: Unassigned Created: 2017/04/27 7:10 AM Priority: Normal Reporter: David Schmitt When the provider feature feature can't load a gem, the error message is swallowed, making tracing the issue unnecessarily harder. Ref: https://github.com/DavidS/puppet/blob/87eac2d16be8993af33842f7ce83cfa04b1d2694/lib/puppet/util/feature.rb#L90 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7477) puppet agent -t -noop runs puppet agent rather than error out
Title: Message Title Pat Riehecky updated an issue Puppet / PUP-7477 puppet agent -t -noop runs puppet agent rather than error out Change By: Pat Riehecky Affects Version/s: PUP 4.9.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7477) puppet agent -t -noop runs puppet agent rather than error out
Title: Message Title Pat Riehecky assigned an issue to Pat Riehecky Puppet / PUP-7477 puppet agent -t -noop runs puppet agent rather than error out Change By: Pat Riehecky Assignee: Pat Riehecky Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7477) puppet agent -t -noop runs puppet agent rather than error out
Title: Message Title Pat Riehecky created an issue Puppet / PUP-7477 puppet agent -t -noop runs puppet agent rather than error out Issue Type: Improvement Affects Versions: PUP 4.9.4 Assignee: Unassigned Components: CLI Created: 2017/04/27 6:50 AM Environment: Command line testing of changes (with a typo) Priority: Normal Reporter: Pat Riehecky When testing puppet changes via the command line, a silly typo results in an agent run being executed. puppet agent -t -noop The correct command is puppet agent -t --noop. Can puppet agent error out if unrecognized arguments are presented on the command line? Unexpected runs of the agent can cause serious outages. Additionally puppet agent -disable does not produce an error which may leave folks believing puppet has been disabled when it has not.
Jira (PUP-6639) Yumrepo can't work with files using spaces in their INI format
Title: Message Title Benjamin Merot commented on PUP-6639 Re: Yumrepo can't work with files using spaces in their INI format Since no one touched this ticket, I had a look at the code. There is an inline command in the inifile.rb util which mentions this situation: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/inifile.rb#L179 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7476) Unable to Install Puppetserver on RHEL 7
Title: Message Title
Ashok Rajendran updated an issue
Puppet / PUP-7476
Unable to Install Puppetserver on RHEL 7
Change By:
Ashok Rajendran
Hi,I have problem installing Puppet server on RHEL 7 using web console. Please find the below installation Log . Can someone please help me on this issue. Resolving Dependencies--> Running transaction check---> Package facter.x86_64 1:1.7.6-2.1.el7sat will be obsoleted---> Package hiera.noarch 0:1.3.1-2.el7 will be obsoleted---> Package pe-installer.x86_64 0:2017.1.2-1.el7 will be installed---> Package pe-modules.x86_64 0:2017.1.1-1.el7 will be installed---> Package puppet.noarch 0:3.8.7-1.el7 will be obsoleted--> Processing Dependency: puppet < 4.0.0 for package: puppetserver-1.2.0-1.el7.noarch--> Processing Dependency: puppet = 3.8.7-1.el7 for package: puppet-server-3.8.7-1.el7.noarch---> Package puppet-agent.x86_64 0:1.9.3-1.el7 will be obsoleting--> Finished Dependency Resolution{color:#d04437}*Error: Package: puppetserver-1.2.0-1.el7.noarch (@puppetlabs-products) Requires: puppet < 4.0.0*{color} Removing: puppet-3.8.7-1.el7.noarch (@puppetlabs-products) puppet = 3.8.7-1.el7 Obsoleted By: puppet-agent-1.9.3-1.el7.x86_64 (puppet_enterprise) puppet >= 4.0.0-1.el7 Available: puppet-3.5.1-1.el7.noarch (puppetlabs-products) puppet = 3.5.1-1.el7 Available: puppet-3.6.0-1.el7.noarch (puppetlabs-products) puppet = 3.6.0-1.el7 Available: puppet-3.6.1-1.el7.noarch (puppetlabs-products) puppet = 3.6.1-1.el7 Available: puppet-3.6.2-1.el7.noarch (puppetlabs-products) puppet = 3.6.2-1.el7 Available: puppet-3.6.2-1.el7sat.noarch (rhui-REGION-rhel-server-rh-common) puppet = 3.6.2-1.el7sat Available: puppet-3.7.0-1.el7.noarch (puppetlabs-products) puppet = 3.7.0-1.el7 Available: puppet-3.7.1-1.el7.noarch (puppetlabs-products) puppet = 3.7.1-1.el7 Available: puppet-3.7.2-1.el7.noarch (puppetlabs-products) puppet = 3.7.2-1.el7 Available: puppet-3.7.3-1.el7.noarch (puppetlabs-products) puppet = 3.7.3-1.el7 Available: puppet-3.7.4-1.el7.noarch (puppetlabs-products) puppet = 3.7.4-1.el7 Available: puppet-3.7.5-1.el7.noarch (puppetlabs-products) puppet = 3.7.5-1.el7 Available: puppet-3.8.1-1.el7.noarch (puppetlabs-products) puppet = 3.8.1-1.el7 Available: puppet-3.8.2-1.el7.noarch (puppetlabs-products) puppet = 3.8.2-1.el7 Available: puppet-3.8.3-1.el7.noarch (puppetlabs-products) puppet = 3.8.3-1.el7 Available: puppet-3.8.4-1.el7.noarch (puppetlabs-products) puppet = 3.8.4-1.el7 Available: puppet-3.8.5-1.el7.noarch (puppetlabs-products) puppet = 3.8.5-1.el7 Available: puppet-3.8.6-1.el7.noarch (puppetlabs-products) puppet = 3.8.6-1.el7Error: Package: puppet-server-3.8.7-1.el7.noarch (@puppetlabs-products) Requires: puppet = 3.8.7-1.el7 Removing: puppet-3.8.7-1.el7.noarch (@puppetlabs-products) puppet = 3.8.7-1.el7 Obsoleted By:
Jira (PUP-7476) Unable to Install Puppetserver on RHEL 7
Title: Message Title Ashok Rajendran created an issue Puppet / PUP-7476 Unable to Install Puppetserver on RHEL 7 Issue Type: Bug Assignee: Unassigned Components: PE Created: 2017/04/27 5:59 AM Priority: Normal Reporter: Ashok Rajendran Hi, I have problem installing Puppet server on RHEL 7 using web console. Please find the below installation Log Resolving Dependencies --> Running transaction check ---> Package facter.x86_64 1:1.7.6-2.1.el7sat will be obsoleted ---> Package hiera.noarch 0:1.3.1-2.el7 will be obsoleted ---> Package pe-installer.x86_64 0:2017.1.2-1.el7 will be installed ---> Package pe-modules.x86_64 0:2017.1.1-1.el7 will be installed ---> Package puppet.noarch 0:3.8.7-1.el7 will be obsoleted --> Processing Dependency: puppet < 4.0.0 for package: puppetserver-1.2.0-1.el7.noarch --> Processing Dependency: puppet = 3.8.7-1.el7 for package: puppet-server-3.8.7-1.el7.noarch ---> Package puppet-agent.x86_64 0:1.9.3-1.el7 will be obsoleting --> Finished Dependency Resolution *Error: Package: puppetserver-1.2.0-1.el7.noarch (@puppetlabs-products) Requires: puppet < 4.0.0* Removing: puppet-3.8.7-1.el7.noarch (@puppetlabs-products) puppet = 3.8.7-1.el7 Obsoleted By: puppet-agent-1.9.3-1.el7.x86_64 (puppet_enterprise) puppet >= 4.0.0-1.el7 Available: puppet-3.5.1-1.el7.noarch (puppetlabs-products) puppet = 3.5.1-1.el7 Available: puppet-3.6.0-1.el7.noarch (puppetlabs-products) puppet = 3.6.0-1.el7 Available: puppet-3.6.1-1.el7.noarch (puppetlabs-products) puppet = 3.6.1-1.el7 Available: puppet-3.6.2-1.el7.noarch (puppetlabs-products) puppet = 3.6.2-1.el7 Available:
Jira (PUP-25) Resource defaults aren't completely evaluated by the compiler
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-25
Resource defaults aren't completely evaluated by the compiler
Change By:
Henrik Lindberg
Release Notes Summary:
Puppet has since the beginning evaluated collections before applying default values defined via resource type defaults, thereby making it impossible to use such values when performing collection. This is now changed and an example like below now works as expected:{code}File { tag => 'sc_test' }File { '/tmp/test': ensure => present }File <<| tag == 'sc_test' |>>{code} This change will affect existing logic where it was assumed that default values were set via resource type defaults were *not* present at the time of collection.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-25) Resource defaults aren't completely evaluated by the compiler
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-25
Resource defaults aren't completely evaluated by the compiler
Change By:
Henrik Lindberg
Release Notes Summary:
Puppet has since the beginning evaluated collections before applying default values defined via resource type defaults, thereby making it impossible to use such values when performing collection. This is now changed and an example like below now works as expected:{code}File { tag => 'sc_test' }File { '/tmp/test': ensure => present }File <<| tag == 'sc_test' |>>{code}
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Henrik Lindberg assigned an issue to Moses Mendoza Puppet / PUP-7431 Upgrade vendored version of SemanticPuppet Change By: Henrik Lindberg Assignee: Moses Mendoza Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6872) allow global hiera and lookup in different environments
Title: Message Title Stefan Pijnappels commented on PUP-6872 Re: allow global hiera and lookup in different environments Henrik Lindberg I have a related question from a customer who highlighted that during a migration, it was difficult to test that the expected values were returned when data was stored in an environment's data store using the environment's hiera.yaml to define the hierarchy. This is due to the fact that it is not possible to pass an environment to the `puppet lookup` tool. This means that the only way to ensure that the correct value is being returned for a key lookup when the environment makes a difference is to run the puppet lookup tool against a node that is known to be in the environment in question. As we can use facts to override values passed to the lookup, would it not be useful to also be able to pass an environment? If this requires an additional ticket, please let me know and I'll raise one. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-570) lookups within hiera data values break %{literal('%')}
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-570
lookups within hiera data values break %{literal('%')}
Needs to be tested on Puppet 4.10 with hiera 3 and 5. If confirmed to still be a problem, this ticket should transition to a PUP ticket.
Change By:
Henrik Lindberg
Team:
Puppet Developer Experience
Sprint:
PDE Triage
Component/s:
CLI
Component/s:
PE
Component/s:
Community
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (HI-570) lookups within hiera data values break %{literal('%')}
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-570
lookups within hiera data values break %{literal('%')}
Change By:
Henrik Lindberg
consider the hiera data fragment: {code} ---some_text: "%{alias('label_format')}"label_format: "%{literal('%')}{vpc}_pub%{literal('%')}{az}" {code} ---When you lookup the value 'label_format' you correctly obtain the string {code} "%{vpc}_pub%{az}" {code} as the value. However, if you lookup the value 'some_text' then the result depends on whether {code} %{vpc} {code} and {code} %{az} {code} have valid substitutions. Without facts or variables, the current result from the lookup is the string "_pub" Until this bug is fixed, the utility of the %{literal('%')} function is limited to being used in values that are only directly requested.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7475) A regex literal for matching backslashes causes a lexer error
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7475 A regex literal for matching backslashes causes a lexer error Change By: Henrik Lindberg Story Points: 1 Release Notes Summary: A literal regex for matching a backslash would cause a lexer error. This is now fixed. Sprint: PDE 2017-05-03 Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options,
Jira (PUP-7475) A regex literal for matching backslashes causes a lexer error
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7475 A regex literal for matching backslashes causes a lexer error Change By: Henrik Lindberg Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 4.10.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
