Jira (PUP-8443) Hiera3 Lookups fail when agent 5.3.4 is installed
Title: Message Title Jacob Helwig commented on PUP-8443 Re: Hiera3 Lookups fail when agent 5.3.4 is installed Turns out there was a section of code below the snippet that Matthew Gyurgyik included in the ticket that was effectively doing "node.parameters = new_hash". The new hash didn't include an environment key, so the top-scope $environment variable would be nil, which is why we'd see %environment being empty in the hiera config. Before PUP-8225, node.fact_merge would end up re-setting node.parameters['environment'] to the name of node.environment, which is why PUP-8225 broke things here. node.fact_merge stopped setting node.parameters['environment'] because facts aren't supposed to determine the environment a node is in, and fact_merge trying to be smart about re-setting node.parameters['environment'] after letting facts overwrite it was causing a bunch of race-conditions if node.environment hadn't already been populated and needed to be dynamically determined. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3734) Ensure that resource indirection uses existing resource type
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3734 Ensure that resource indirection uses existing resource type Change By: Zachary Kent Fix Version/s: PDB 5.2.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3695) Package GC spends a lot of time when there's probably very little to clean up
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3695 Package GC spends a lot of time when there's probably very little to clean up Change By: Zachary Kent Fix Version/s: PDB 5.2.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3600) PuppetDB should track how long each migration takes
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3600 PuppetDB should track how long each migration takes Change By: Zachary Kent Fix Version/s: PDB 5.2.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3176) PQL does not support query for fact path equality
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3176 PQL does not support query for fact path equality Change By: Zachary Kent Fix Version/s: PDB 5.2.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3833) Merge-up, branch, and create pipelines (PuppetDB 5.2.0)
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-3833 Merge-up, branch, and create pipelines (PuppetDB 5.2.0) Change By: Zachary Kent Assignee: Zachary Kent Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8444) Have "puppet man" default to "--help" when run without arguments
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8444 Have "puppet man" default to "--help" when run without arguments Change By: Eric Delaney Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8444) Have "puppet man" default to "--help" when run without arguments
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8444 Have "puppet man" default to "--help" when run without arguments Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1813) Windows virtual machines on QEMU/KVM servers not detected as virtual
Title: Message Title Branan Riley commented on FACT-1813 Re: Windows virtual machines on QEMU/KVM servers not detected as virtual This may be a duplicate of FACT-1806 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8448) "puppet cert clean" only works if at least one cert has already been signed
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8448 "puppet cert clean" only works if at least one cert has already been signed Change By: Jacob Helwig Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8378) Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages
Title: Message Title Eric Delaney commented on PUP-8378 Re: Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages Tested on master(5.4.0) SHA=26b954ef6f9806161284bc57dcf5b71900889349 SUITE_VERSION=5.3.3.679.g26b954e Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-332) Target objects should store state of the Targets
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-332 Target objects should store state of the Targets Issue Type: New Feature Assignee: Unassigned Created: 2018/02/09 3:42 PM Priority: Normal Reporter: Alex Dreyer Plan authors should be able to store data (called 'vars' for now) on the Target objects and retrieve it during a plan. Changes: Inventory should track all target instances created(at least with get_target) and return the same instance every time get_target is called. There should be a puppet function set_var(Target $target, String $key, Data $value) that sets the value in vars in a way that works even if the Target was created outside get_target Target.vars should return vars as a Hash vars should be settable in the inventory file at the same level as config. When a target is created the merged value of all vars from the inventory file should be included. Questions: What should we call vars? Is the merge strategy for config correct for vars(deep merge hashes choose the first for other values) Add Comment
Jira (PUP-8378) Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8378 Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-330) Users should be able to use wildcards to target nodes in inventory
Title: Message Title
Michael Smith commented on BOLT-330
Re: Users should be able to use wildcards to target nodes in inventory
Mikker Gimenez had an additional request for number matching, such as [0-9] and {5,6,7} . Those can already be accomplished with the shell and don't need knowledge of the inventory to use though. Would uses where you need to mix them come up? One nuance of this is you'd need to quote the node list, otherwise you'll get an error with *.
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-330) Users should be able to use wildcards to target nodes in inventory
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-330
Users should be able to use wildcards to target nodes in inventory
Change By:
Michael Smith
If users have listed nodes in their inventory file they should be able to run against them with wild card statements like:foo-*.example.comQuestions: should users define groups instead perhaps? (probably not) What should the syntax be? {{ x * y -> /^ x .* y $/}} Should users be able to use wildcards with groups? no If a wildcard is present but no nodes match, should we try to use it as a target name (and probably error), error immediately, or return an empty list?
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this
Jira (PUP-8443) Hiera3 Lookups fail when agent 5.3.4 is installed
Title: Message Title Jacob Helwig commented on PUP-8443 Re: Hiera3 Lookups fail when agent 5.3.4 is installed Matthew Gyurgyik, would it be possible for you to directly email me the full content of the file that snippet came from (jacob at puppet dot com)? That snippet looks right, but there might be things going on around it that would be helpful to see. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-330) Users should be able to use wildcards to target nodes in inventory
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-330
Users should be able to use wildcards to target nodes in inventory
Change By:
Michael Smith
If users have listed nodes in their inventory file they should be able to run against them with wild card statements like:foo-*.example.comQuestions: should users define groups instead perhaps? (probably not) What should the syntax be? {{* -> /^.*$/}} Should users be able to use wildcards with groups? no If a wildcard is present but no nodes match, should we try to use it as a target name (and probably error) , error immediately, or return an empty list?
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (BOLT-330) Users should be able to use wildcards to target nodes in inventory
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-330
Users should be able to use wildcards to target nodes in inventory
Change By:
Michael Smith
If users have listed nodes in their inventory file they should be able to run against them with wild card statements like:foo-*.example.comQuestions: should users define groups instead perhaps? (probably not) What should the syntax be? {{* -> /^.*$/}} Should users be able to use wildcards with groups? no If a wildcard is present but no nodes match, should we try to use it as a target name (and probably error) or return an empty list?
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (BOLT-330) Users should be able to use wildcards to target nodes in inventory
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-330
Users should be able to use wildcards to target nodes in inventory
Change By:
Michael Smith
If users have listed nodes in their inventory file they should be able to run against them with wild card statements like:foo-*.example.comQuestions:should users define groups instead perhaps? (probably not)What should the syntax be? {{ * -> / ^ .* $ / }} Should users be able to use wildcards with groups? no
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-331) Script to generate inventory from puppetdb queries
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-331 Script to generate inventory from puppetdb queries Issue Type: New Feature Assignee: Unassigned Created: 2018/02/09 3:27 PM Priority: Normal Reporter: Alex Dreyer We should write a script to generate an inventory file from puppetdb queries. How should this connect to puppetdb The script should shell out to and depend on the puppet-query tool. Where should this script live? git? bolt inventory puppetdb command? What should the input format be? a yaml file similiar to the inventory file syntax but with "queries" instead of nodes. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-330) Users should be able to use wildcards to target nodes in inventory
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-330 Users should be able to use wildcards to target nodes in inventory Issue Type: New Feature Assignee: Unassigned Created: 2018/02/09 3:23 PM Priority: Normal Reporter: Alex Dreyer If users have listed nodes in their inventory file they should be able to run against them with wild card statements like: foo-*.example.com Questions: should users define groups instead perhaps? (probably not) What should the syntax be? * -> /.*/ Should users be able to use wildcards with groups? no Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8443) Hiera3 Lookups fail when agent 5.3.4 is installed
Title: Message Title Matthew Gyurgyik commented on PUP-8443 Re: Hiera3 Lookups fail when agent 5.3.4 is installed We are using an external node classifier that we wrote a while back. I was looking at the code and noticed that we are setting the environment. I don't have a great grasp of what is going on from code/internal to puppet perspective, but perhaps this is the root of the problem? node = Puppet::Node.new(request.key) if request.environment node.environment = request.environment end node.classes = ["nodepatterns"] Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-1916) puppet cert clean cannot remove signing requests
Title: Message Title Eric Delaney commented on PUP-1916 Re: puppet cert clean cannot remove signing requests Ok so the code change works as long as you have a another signed cert, otherwise you can end up the clean failing. We are splitting this out as a separate issue PUP-8448 given where we are in the release. Only people setting up a server for the first time will see the problem and having the more common case working is good. Tested on master(5.4.0) SHA=26b954ef6f9806161284bc57dcf5b71900889349 SUITE_VERSION=5.3.3.679.g26b954e [root@dr8ab7o97efo4ds tmp]# puppet cert list --all "another_try" (SHA256) 34:81:04:AA:B4:27:E8:8A:5F:83:51:B4:00:68:2F:81:62:6E:7A:87:31:CD:22:CB:9C:47:8F:0B:B8:BB:27:8D + "dr8ab7o97efo4ds.delivery.puppetlabs.net" (SHA256) 1C:3A:B6:A2:03:F4:83:48:BD:B6:27:31:8E:A7:50:5A:43:18:AB:C6:08:C3:7E:FB:20:E1:F4:67:80:37:D1:60 (alt names: "DNS:dr8ab7o97efo4ds", "DNS:dr8ab7o97efo4ds.delivery.puppetlabs.net", "DNS:puppet") + "yckqvewedlk0tmo.delivery.puppetlabs.net" (SHA256) BE:27:91:65:5E:06:25:3E:56:47:15:59:3F:71:73:08:C7:D0:9C:31:CA:36:F5:48:B3:90:76:AF:71:3F:E1:65 [root@dr8ab7o97efo4ds tmp]# puppet cert clean another_try Notice: Removing file Puppet::SSL::CertificateRequest another_try at '/etc/puppetlabs/puppet/ssl/ca/requests/another_try.pem' [root@dr8ab7o97efo4ds tmp]#
Jira (PUP-8448) "puppet cert clean" only works if at least one cert has already been signed
Title: Message Title Jacob Helwig created an issue Puppet / PUP-8448 "puppet cert clean" only works if at least one cert has already been signed Issue Type: Bug Assignee: Jacob Helwig Created: 2018/02/09 3:03 PM Fix Versions: PUP 4.10.z, PUP 5.3.z, PUP 5.4.z Priority: Normal Reporter: Jacob Helwig PUP-1916 added the ability to clean certificates that have not yet been signed, without having to manually sign/revoke them first. However, this only works if there is at least one signed certificate in the list of certificate names passed to "puppet cert clean". Add Comment
Jira (PUP-1916) puppet cert clean cannot remove signing requests
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-1916 puppet cert clean cannot remove signing requests Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8418) TypeError no implicit conversion of nil into String in puppet 5.3.4
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8418 TypeError no implicit conversion of nil into String in puppet 5.3.4 Change By: Josh Cooper Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1916) puppet cert clean cannot remove signing requests
Title: Message Title Eric Delaney assigned an issue to Jacob Helwig Puppet / PUP-1916 puppet cert clean cannot remove signing requests Change By: Eric Delaney Assignee: Eric Delaney Jacob Helwig Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7349) resource type tidy does not honor metaparameter noop
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7349 resource type tidy does not honor metaparameter noop Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7349) resource type tidy does not honor metaparameter noop
Title: Message Title
Eric Delaney commented on PUP-7349
Re: resource type tidy does not honor metaparameter noop
Tested on master(5.4.0) SHA=26b954ef6f9806161284bc57dcf5b71900889349 SUITE_VERSION=5.3.3.679.g26b954e
[root@yckqvewedlk0tmo tidy]# ls -Flas
total 12
0 drwxr-xr-x 2 root root 62 Feb 9 22:51 ./
4 drwxrwxrwt. 10 root root 4096 Feb 9 22:50 ../
0 -rw-r--r-- 1 root root0 Feb 9 22:44 keeper
4 -rw-r--r-- 1 root root 13 Feb 9 22:44 keeper.2
4 -rw-r--r-- 1 root root 2752 Feb 9 22:51 vsphere-bootstrap.log
[root@yckqvewedlk0tmo tidy]# cat ../tidy.pp
tidy { '/tmp/tidy':
age => '10s',
size => '1k',
matches => ['*'],
recurse => true,
Jira (PUP-7349) resource type tidy does not honor metaparameter noop
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-7349 resource type tidy does not honor metaparameter noop Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8443) Hiera3 Lookups fail when agent 5.3.4 is installed
Title: Message Title Matthew Gyurgyik commented on PUP-8443 Re: Hiera3 Lookups fail when agent 5.3.4 is installed We have a few places in our puppet code where we make direct use of the `hiera` function, but most of our hiera calls are the result of automatic class parameter lookups. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8442) type parameters do not honor when default is set to false
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8442 type parameters do not honor when default is set to false Change By: Melissa Stone Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8442) type parameters do not honor when default is set to false
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8442 type parameters do not honor when default is set to false Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1916) puppet cert clean cannot remove signing requests
Title: Message Title Eric Delaney commented on PUP-1916 Re: puppet cert clean cannot remove signing requests Jacob Helwig can you try this out on the latest agent, it doesn't appear to be fixed: Tested on master(5.4.0) SHA=26b954ef6f9806161284bc57dcf5b71900889349 SUITE_VERSION=5.3.3.679.g26b954e agent: [root@yckqvewedlk0tmo ssl]# rm */*.pem rm: remove regular file ‘certificate_requests/yckqvewedlk0tmo.delivery.puppetlabs.net.pem’? y rm: remove regular file ‘certs/ca.pem’? y rm: remove regular file ‘private_keys/yckqvewedlk0tmo.delivery.puppetlabs.net.pem’? y rm: remove regular file ‘public_keys/yckqvewedlk0tmo.delivery.puppetlabs.net.pem’? y [root@yckqvewedlk0tmo ssl]# [root@yckqvewedlk0tmo ssl]# puppet agent -t --certname crazy Info: Creating a new SSL key for crazy Info: Caching certificate for ca Info: csr_attributes file loading from /etc/puppetlabs/puppet/csr_attributes.yaml Info: Creating a new SSL certificate request for crazy Info: Certificate Request fingerprint
Jira (PUP-8374) NameService inconsistent with setting the environment in which commands are executed
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8374 NameService inconsistent with setting the environment in which commands are executed Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2868) `puppet config print` confusing for users
Title: Message Title Melissa Stone commented on PUP-2868 Re: `puppet config print` confusing for users Manually verified with 5.3.3.679.g26b954e [root@yx32o85umtg6j0r ~]# puppet config print server Warning: No section specified; defaulting to 'main'. Set the config section by using the `--section` flag. For example, `puppet config --section user print foo`. For more information, see https://puppet.com/docs/puppet/latest/configuration.html Resolving settings from section 'main' in environment 'production' foo [root@yx32o85umtg6j0r ~]# yum info puppet-agent Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Installed Packages Name: puppet-agent Arch: x86_64
Jira (PUP-8418) TypeError no implicit conversion of nil into String in puppet 5.3.4
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8418 TypeError no implicit conversion of nil into String in puppet 5.3.4 Change By: Kenn Hussey Fix Version/s: PUP 5.3.5 Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.4.z Fix Version/s: PUP 5.3.z Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com.
Jira (PUP-8418) TypeError no implicit conversion of nil into String in puppet 5.3.4
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8418 TypeError no implicit conversion of nil into String in puppet 5.3.4 Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2868) `puppet config print` confusing for users
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-2868 `puppet config print` confusing for users Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8114) Service provider 'redhat' does not correctly detect enabled state of 'boot.*' services on SLES 11.
Title: Message Title Jorie Tappa assigned an issue to Jorie Tappa Puppet / PUP-8114 Service provider 'redhat' does not correctly detect enabled state of 'boot.*' services on SLES 11. Change By: Jorie Tappa Assignee: Jorie Tappa Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8443) Hiera3 Lookups fail when agent 5.3.4 is installed
Title: Message Title
Josh Cooper commented on PUP-8443
Re: Hiera3 Lookups fail when agent 5.3.4 is installed
Matthew Gyurgyik I'm having trouble reproducing, I see the environment variable correctly interpolated in the lookup. How are you triggering the lookup, e.g. using the hiera function?
[root@b6ieuqgdfam1rxn ~]# cat /etc/puppetlabs/code/hiera.yaml
---
:backends:
- yaml
:hierarchy:
- "host/%{::fqdn}"
- "role/%{::role}"
- "hostgroup/%{::hostgroup}"
- "team/%{::team}"
- "enclave/%{::enclave}"
- common
:yaml:
Jira (PUP-3020) Add action for deleting settings from puppet config
Title: Message Title Melissa Stone commented on PUP-3020 Re: Add action for deleting settings from puppet config [root@yx32o85umtg6j0r ~]# cat /etc/puppetlabs/puppet/puppet.conf # This file can be used to override the default puppet settings. # See the following links for more details on what settings are available: # - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html # - https://docs.puppetlabs.com/puppet/latest/reference/configuration.html [root@yx32o85umtg6j0r ~]# puppet config set foo bar --section user [root@yx32o85umtg6j0r ~]# cat /etc/puppetlabs/puppet/puppet.conf # This file can be used to override the default puppet settings. # See the following links for more details on what settings are available: # -
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-2868 `puppet config print` confusing for users Change By: Eric Delaney Assignee: Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8378) Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8378 Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages Change By: Eric Delaney Assignee: Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8114) Service provider 'redhat' does not correctly detect enabled state of 'boot.*' services on SLES 11.
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8114 Service provider 'redhat' does not correctly detect enabled state of 'boot.*' services on SLES 11. Change By: Eric Delaney Assignee: Jorie Tappa Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7349) resource type tidy does not honor metaparameter noop
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-7349 resource type tidy does not honor metaparameter noop Change By: Eric Delaney Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8374) NameService inconsistent with setting the environment in which commands are executed
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8374 NameService inconsistent with setting the environment in which commands are executed Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3020) Add action for deleting settings from puppet config
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-3020 Add action for deleting settings from puppet config Change By: Melissa Stone Assignee: Eric Delaney Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1916) puppet cert clean cannot remove signing requests
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-1916 puppet cert clean cannot remove signing requests Change By: Eric Delaney Assignee: Jacob Helwig Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8255) gem package provider broken with Rubygems 2.7.x
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8255 gem package provider broken with Rubygems 2.7.x Change By: Eric Delaney QA Risk Assessment: Needs Assessment Manual Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8255) gem package provider broken with Rubygems 2.7.x
Title: Message Title Eric Delaney commented on PUP-8255 Re: gem package provider broken with Rubygems 2.7.x Tested on master(5.4.0) SHA=26b954ef6f9806161284bc57dcf5b71900889349 SUITE_VERSION=5.3.3.679.g26b954e ✔ ~/work/my_repos/puppet [:327b03a9e|…1⚑ 1] 13:56 $ bx puppet apply gem.pp Notice: Compiled catalog for macbook-pro-2.local in environment production in 0.54 seconds Notice: /Stage[main]/Main/Package[cowspeak]/ensure: created Notice: Applied catalog in 1.93 seconds ✔ ~/work/my_repos/puppet [:327b03a9e|…1⚑ 1] ✔ ~/work/my_repos/puppet [:327b03a9e|…1⚑ 1] 13:57 $ find .bundle -name cowspeak .bundle/ruby/2.4.0/bin/cowspeak .bundle/ruby/2.4.0/gems/cowspeak-0.0.2/bin/cowspeak .bundle/ruby/2.4.0/gems/cowspeak-0.0.2/lib/cowspeak ✔ ~/work/my_repos/puppet [:327b03a9e|…1⚑
Jira (PUP-8231) Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp)
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-8231
Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp)
Change By:
Ethan Brown
Steps to reproduce1. Create Group "TestGroup" with "IIS AppPool\DefaultAppPool" as a member {code} group { 'TestGroup':name=> 'TestGroup',ensure => present,members => ['IIS AppPool\DefaultAppPool'],auth_membership => false,}{code} 2. Add new user "administrator as a member Re-run the same manifest {code} group { 'TestGroup':name=> 'TestGroup',ensure => present,members => ['IIS AppPool\DefaultAppPool' ,'administrator' ],auth_membership => false,}{code} 3. When applying codes in step 2 Once the group exists on the system , it will throw Puppet fails to resolve the virtual account properly and generates an error like: {code}"Could not resolve name: DefaultAppPool"{code}
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8447) "/etc/profile.d/puppet-agent.*" should update MANPATH to include shipped man pages
Title: Message Title Jacob Helwig created an issue Puppet / PUP-8447 "/etc/profile.d/puppet-agent.*" should update MANPATH to include shipped man pages Issue Type: Improvement Assignee: Unassigned Created: 2018/02/09 1:56 PM Fix Versions: PUP 5.y Priority: Normal Reporter: Jacob Helwig /etc/profile.d/puppet-agent.* should update MANPATH (similarly to how is already done for PATH) on platforms where it makes sense to do so, or provide guidance to where Puppet's man pages are likely to be (/opt/puppetlabs/puppet/share/man). Add Comment
Jira (PUP-8446) Remove "puppet man" face application
Title: Message Title Jacob Helwig created an issue Puppet / PUP-8446 Remove "puppet man" face application Issue Type: Task Assignee: Unassigned Created: 2018/02/09 1:53 PM Fix Versions: PUP 6.0.0 Priority: Normal Reporter: Jacob Helwig The "puppet man" application was deprecated, and should be removed. Now is the time to remove it, and any remaining references to it. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8295) Group resource cannot resolve virtual account "NT Service\Servicename"
Title: Message Title Ethan Brown commented on PUP-8295 Re: Group resource cannot resolve virtual account "NT Service\Servicename" I'm closing this as a duplicate of PUP-8231. Thanks for filing this ticket, and apologies for not having seen it earlier. The problem in the screenshot is the same problem as PUP-8231. When the group is first created, Puppet behaves correctly as there is no existing state on the system. On the second run, Puppet retrieves the system state, but internally doesn't fully qualify the account name, which it later uses to resolve to a SID. So when Puppet retrieves the resource it uses the name SQLIaaSExtension even though it should be using the name NT Service\SQLIaaSExtension. The pull request attached to PUP-8231 fixes this problem. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Thomas Hallgren commented on PUP-8002 Re: "Attempt to redefine entity" caused by using a resource collector Ben Ford, I have no explicit knowledge besides what the ticket shows of what's included in the releases that the customer is using. AFAIK, the issue is fixed by the PR that I've submitted. The fact that the ticket PDB-3734 is still in "ready for merge" is alarming but probably an oversight. The associated PR was merge a long time ago. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8445) Deprecate "puppet man"
Title: Message Title Jacob Helwig created an issue Puppet / PUP-8445 Deprecate "puppet man" Issue Type: Task Assignee: Unassigned Created: 2018/02/09 1:51 PM Fix Versions: PUP 5.y Priority: Normal Reporter: Jacob Helwig The "puppet man" face application is being deprecated in favor of "puppet help", and direct usage of the shipped man pages. As such, we need to: Add a deprecation message to "puppet man" and its documentation to alert users to this. Remove references to "puppet man", "puppet man man", "man puppet-man", etc., and update them to point at "puppet help" or "man puppet-" if appropriate. Add mentions of setting MANPATH (and what to set it to include) so that the shipped man pages can be accessed via the man command. Add Comment
Jira (PUP-8231) Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8231 Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp) Change By: Ethan Brown Environment: Reproduce Any version of Windows including 2008R2 and above (virtual accounts were introduced in Win 2012 R2, but should affect most windows platform 2008R2 / 7) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8231) Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8231 Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp) Change By: Ethan Brown Acceptance Criteria: - An existing group that contains virtual accounts should be modifiable with Puppet without error- Fix should not introduce any backwards incompatible changes to existing Windows Group behavior Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8231) Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8231 Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp) Change By: Ethan Brown Sprint: Windows Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8231) Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8231 Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp) Change By: Ethan Brown Fix Version/s: PUP 5.3.5 Fix Version/s: PUP 4.10.11 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8231) Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8231 Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp) Change By: Ethan Brown Affects Version/s: PUP 4.10.10 Affects Version/s: PUP 5.3.4 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8432) Remove gettext-setup as a runtime gem dependency
Title: Message Title Eric Delaney commented on PUP-8432 Re: Remove gettext-setup as a runtime gem dependency Tested on master(5.4.0) SHA=26b954ef6f9806161284bc57dcf5b71900889349 SUITE_VERSION=5.3.3.679.g26b954e [root@u5ldznmi6v6yarc ~]# gem install puppet-5.3.4.777.gem gem list Fetching: facter-2.5.1.gem (100%) Successfully installed facter-2.5.1 Fetching: hiera-3.4.2.gem (100%) Successfully installed hiera-3.4.2 Fetching: fast_gettext-1.1.2.gem (100%) Successfully installed fast_gettext-1.1.2 Fetching: locale-2.1.2.gem (100%) Successfully installed locale-2.1.2 Successfully installed puppet-5.3.4.777 Parsing documentation for facter-2.5.1 Installing ri documentation for facter-2.5.1
Jira (PUP-8432) Remove gettext-setup as a runtime gem dependency
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8432 Remove gettext-setup as a runtime gem dependency Change By: Eric Delaney QA Risk Assessment: Needs Assessment Manual Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8231) Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp)
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-8231 Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp) Change By: Ethan Brown Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8231) Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8231 Managing an existing Windows Group resource may error when any of its members is a virtual account (like IIS AppPool\DefaultAppPool or NT Service\Dhcp) Change By: Ethan Brown Summary: Managing an existing Windows Group resource - unable to add new member if there may error when any of its members is existing a virtual account (like IIS AppPool\ user DefaultAppPool or NT Service\Dhcp) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8444) Have "puppet man" default to "--help" when run without arguments
Title: Message Title Jacob Helwig created an issue Puppet / PUP-8444 Have "puppet man" default to "--help" when run without arguments Issue Type: Task Assignee: Unassigned Created: 2018/02/09 1:43 PM Fix Versions: PUP 5.y Priority: Normal Reporter: Jacob Helwig Currently, puppet man without any arguments generates an error message. % be ./bin/puppet man Error: puppet man man takes 1 argument, but you gave 0 Error: Try 'puppet help man man' for usage This should, instead, show the puppet man --help output. % be ./bin/puppet man --help
Jira (PUP-8255) gem package provider broken with Rubygems 2.7.x
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8255 gem package provider broken with Rubygems 2.7.x Change By: Melissa Stone Assignee: Jorie Tappa Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8441) Error datatype should support to_json
Title: Message Title Alex Dreyer commented on PUP-8441 Re: Error datatype should support to_json This needs to stay open until the underlying problem is solved. We don't think there is much value in returning arbitrary puppet objects from plans. In practice that doesn't work today and we will likely limit plan return values to objects which have clear json representations in the future. So far of these only error fails to implement a to_json method the dataconverter on the other hand only works for that which is already data. Type we expects plans to interact with. Data ResultSet Result Target Error The data converter cannot be used outside of the compiler which means that PAL essentially has a JSON API rather then one where underlying ruby objects can be passed into and out of the compiler. This is very limiting from bolts perspective. Fundamentally I think the PAL API should allow ruby object to be passed into and out of the compiler. The output for the dataconverter is full of pcore cruft we don't want bolt users to have to interact with. If we do use it we will have to walk the result and limit it only to the value. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-307) Standardize success and failure for plans
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-307 Standardize success and failure for plans Change By: Alex Dreyer Release Notes Summary: Errors in run_plan can be caught and handled in a calling plan with the '_catch_errors' options. Bolt will consider any plan that doesn't error a success. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8443) Hiera3 Lookups fail when agent 5.3.4 is installed
Title: Message Title Matthew Gyurgyik commented on PUP-8443 Re: Hiera3 Lookups fail when agent 5.3.4 is installed In IRC, Eric Sorenson asked me to try and revert Pup 8225 bug 5.3.x environment fact overwrites enc value. Reverting the change appears to fix this problem. [puppet2 tmp]$ wget -q https://github.com/puppetlabs/puppet/commit/389953fe6dbc385fbaf7f27c054306bce3f0de75.patch[root@puppet2 ~]# rpm -q puppet-agent puppet-agent-5.3.4-1.el7.x86_64 [root@puppet2 ~]# cd /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet [root@puppet2 puppet]# cat /tmp/389953fe6dbc385fbaf7f27c054306bce3f0de75.patch | patch -R patching file node.rb Hunk #2 succeeded at 85 (offset 1 line). Hunk #3 succeeded at 139 (offset 1 line). Hunk #4 succeeded at 152 (offset 1 line).[root@puppet2 puppet]# systemctl restart puppetserver Note I did not patch the unit tests (the rest of the patch output was trying to patch the non-existent unit tests)
Jira (BOLT-315) Bolt Packages
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-315 Bolt Packages Change By: Lucy Wyman Bolt does not run well under ruby 2.0 which makes it hard for rh-7 users to use bolt. If we release OS packages for bolt that include or depend on ruby 2.3 this shouldn't be a problem.V1 should build packages for the linux platforms puppet-client-tools installs on. - el 7 (/) - el 6 (/) - debian 7 (/) - debian 8 (/) - sles 12 (/) - ubuntu 1404 (/) - ubuntu 1604 (/)V1 should depend on the puppet-agent package (/)V1 includes a pipeline to build the packagesV1 should include a plan with releng for shipping releases. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group
Jira (PUP-8443) Hiera3 Lookups fail when agent 5.3.4 is installed
Title: Message Title David Hollinger updated an issue Puppet / PUP-8443 Hiera3 Lookups fail when agent 5.3.4 is installed Change By: David Hollinger Affects Version/s: PUP 5.3.4 Component/s: Hiera & Lookup Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8443) Hiera3 Lookups fail when agent 5.3.4 is installed
Title: Message Title Eric Sorenson moved an issue Puppet / PUP-8443 Hiera3 Lookups fail when agent 5.3.4 is installed Change By: Eric Sorenson Key: SERVER PUP - 2120 8443 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Andrew Ball commented on PUP-8002 Re: "Attempt to redefine entity" caused by using a resource collector Yes, I can confirm I hit this intermittently but regularly. It seems that after our master does its own run, the problem resolves itself for a while. I was hoping to grab a trace to give more info, but the issue's gone for now. I'll grab one as soon as it fails again. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8258) Cached catalogs settings are ignored if noop is set to true
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8258 Cached catalogs settings are ignored if noop is set to true Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6507) Puppet help: Hide bad subcommands, and sort remainder by usefulness
Title: Message Title Josh Cooper commented on PUP-6507 Re: Puppet help: Hide bad subcommands, and sort remainder by usefulness In order to remove puppet doc we need to complete the work in DOC-3205 to use puppet-strings to generate reference documentation. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8258) Cached catalogs settings are ignored if noop is set to true
Title: Message Title Eric Delaney commented on PUP-8258 Re: Cached catalogs settings are ignored if noop is set to true Tested on master(5.4.0) SHA=26b954ef6f9806161284bc57dcf5b71900889349 SUITE_VERSION=5.3.3.679.g26b954e With the settings: [root@yckqvewedlk0tmo ~]# puppet agent -t --no-noop Info: Using cached catalog from environment 'production' Info: Applying configuration version '1518205746' Notice: Applied catalog in 0.05 seconds [root@yckqvewedlk0tmo ~]# cat /etc/puppetlabs/puppet/puppet.conf # This file can be used to override the default puppet settings. # See the following links for more details on what settings are available: # - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html # - https://docs.puppetlabs.com/puppet/latest/reference/configuration.html [agent]
Jira (PUP-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Ben Ford commented on PUP-8002 Re: "Attempt to redefine entity" caused by using a resource collector I have a customer hitting this error regularly now. Thomas Hallgren is this fixed? Did it get released? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8420) Regression: puppet apply does not decompress response bodies for http file sources
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8420 Regression: puppet apply does not decompress response bodies for http file sources Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8420) Regression: puppet apply does not decompress response bodies for http file sources
Title: Message Title
Eric Delaney commented on PUP-8420
Re: Regression: puppet apply does not decompress response bodies for http file sources
Tested on master(5.4.0) SHA=26b954ef6f9806161284bc57dcf5b71900889349 SUITE_VERSION=5.3.3.679.g26b954e {noformat} [root@dr8ab7o97efo4ds environments]# rm /tmp/foo rm: remove regular file ‘/tmp/foo’? y [root@dr8ab7o97efo4ds environments]# cat foo.pp file { "foo installer": path => '/tmp/foo', ensure => 'present', mode => '0755', source => "https://raw.githubusercontent.com/puppetlabs/puppet/master/COMMITTERS.md", } [root@dr8ab7o97efo4ds environments]# puppet apply foo.pp Notice: Compiled catalog for dr8ab7o97efo4ds.delivery.puppetlabs.net in environment production in 0.02 seconds Notice: /Stage[main]/Main/File[foo installer]/ensure: defined content as '{mtime}2018-02-09 11:44:54 -0800' Notice: Applied catalog in 0.16 seconds [root@dr8ab7o97efo4ds environments]# head /tmp/foo Committing changes to Puppet We would like to make it easier for community members to contribute to Puppet using pull requests, even if it makes the task of reviewing and committing these changes a little harder. Pull requests are only ever based on a single branch, however, we maintain more than one active branch. As a result contributors should target their changes at the master branch. This makes the process of contributing a little easier for the contributor since they don't need to concern themselves with the question, "What branch do I base my changes [root@dr8ab7o97efo4ds environments]# {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are
Jira (PUP-8098) Add 'acltype' to list of supported ZFS properties
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8098 Add 'acltype' to list of supported ZFS properties Change By: Melissa Stone Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8098) Add 'acltype' to list of supported ZFS properties
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8098 Add 'acltype' to list of supported ZFS properties Change By: Melissa Stone QA Risk Assessment: Needs Assessment No Action Release Notes Summary: 'acltype' is now a valid ZFS property Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8419) Agent's node request fails if environment directory doesn't exist locally
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8419 Agent's node request fails if environment directory doesn't exist locally Change By: Eric Delaney QA Risk Assessment: Needs Assessment Manual Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8098) Add 'acltype' to list of supported ZFS properties
Title: Message Title Melissa Stone commented on PUP-8098 Re: Add 'acltype' to list of supported ZFS properties Merged into master at https://github.com/puppetlabs/puppet/commit/d692adeaa557675322aae7cab090656ccb6b5d01 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8419) Agent's node request fails if environment directory doesn't exist locally
Title: Message Title Eric Delaney commented on PUP-8419 Re: Agent's node request fails if environment directory doesn't exist locally Tested: Without ENC We are happy, when the server has the enviroment, but we don't have one on the agent: $ bundle exec puppet agent -t --environment var --server dr8ab7o97efo4ds.delivery.puppetlabs.net Info: Using configured environment 'var' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Caching catalog for macbook-pro-2.local Info: Applying configuration version '1518204454' Notice: Applied catalog in 0.01 seconds $ With ENC SERVER: [root@dr8ab7o97efo4ds environments]# tail -2 /etc/puppetlabs/puppet/puppet.conf node_terminus = exec
Jira (BOLT-318) I want to refer to inventory groups as targets
Title: Message Title Michael Smith assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-318 I want to refer to inventory groups as targets Change By: Michael Smith Assignee: Michael Smith Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-327) Document Error handling in plans
Title: Message Title Kate Lopresti commented on BOLT-327 Re: Document Error handling in plans Alex Dreyer Draft copy of plans topics for Bolt help available: https://docs.google.com/document/d/13sc9rHERPH_ohymaxuTcRqTWqgWBMkL_3JfboYgaDRE/edit?usp=sharing Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8427) Prepare release announcement (Puppet Platform 5.4.0)
Title: Message Title Molly Waggett assigned an issue to Garrett Guillotte Puppet / PUP-8427 Prepare release announcement (Puppet Platform 5.4.0) Change By: Molly Waggett Assignee: Eric Sorenson Garrett Guillotte Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8267) Rewrite acceptance rake tasks to leverage beaker subcommand support
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8267 Rewrite acceptance rake tasks to leverage beaker subcommand support Change By: Josh Cooper Fix Version/s: PUP 5.3.5 Fix Version/s: PUP 5.3.z Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8409) Puppet config print lists invalid value for environment_timeout when set to unlimited
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8409 Puppet config print lists invalid value for environment_timeout when set to unlimited Change By: Josh Cooper Fix Version/s: PUP 5.3.z Fix Version/s: PUP 5.4.z Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8409) Puppet config print lists invalid value for environment_timeout when set to unlimited
Title: Message Title Kris Bosland commented on PUP-8409 Re: Puppet config print lists invalid value for environment_timeout when set to unlimited Kenn Hussey, we have decided to retarget this, I'm not sure if the correct new version is available in JIRA yet. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8409) Puppet config print lists invalid value for environment_timeout when set to unlimited
Title: Message Title Kris Bosland updated an issue Puppet / PUP-8409 Puppet config print lists invalid value for environment_timeout when set to unlimited Change By: Kris Bosland Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.3.z Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8409) Puppet config print lists invalid value for environment_timeout when set to unlimited
Title: Message Title Kenn Hussey commented on PUP-8409 Re: Puppet config print lists invalid value for environment_timeout when set to unlimited Kris Bosland are we still trying to get this into 5.3.5 / 5.4.0 or should it be retargeted at this point? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8418) TypeError no implicit conversion of nil into String in puppet 5.3.4
Title: Message Title Kenn Hussey commented on PUP-8418 Re: TypeError no implicit conversion of nil into String in puppet 5.3.4 Josh Cooper are we still trying to get this into 5.3.5 / 5.4.0 or should it be retargeted at this point? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1817) Facter: Custom Fact failures due to Facter.add inside if statement.
Title: Message Title Jeff Sparrow commented on FACT-1817 Re: Facter: Custom Fact failures due to Facter.add inside if statement. This can be closed. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1817) Facter: Custom Fact failures due to Facter.add inside if statement.
Title: Message Title Jeff Sparrow commented on FACT-1817 Re: Facter: Custom Fact failures due to Facter.add inside if statement. Oo. I was just debugging through it as I was replying to you, and I see it now. By moving the Facter.add outside of the if statement, I am effectively also moving it outside the requirement of if (kernel == 'windows') and (phys_virt != 'physical') thus, it will actually set Facter.add regardless (and correctly). I really need to get someone to rewrite these things Thanks!!! Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8436) puppet should only ignore pot files when syncing locales
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8436 puppet should only ignore pot files when syncing locales Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8114) Service provider 'redhat' does not correctly detect enabled state of 'boot.*' services on SLES 11.
Title: Message Title Jorie Tappa assigned an issue to Jorie Tappa Puppet / PUP-8114 Service provider 'redhat' does not correctly detect enabled state of 'boot.*' services on SLES 11. Change By: Jorie Tappa Assignee: Jacob Helwig Jorie Tappa Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8436) puppet should only ignore pot files when syncing locales
Title: Message Title Josh Cooper commented on PUP-8436 Re: puppet should only ignore pot files when syncing locales Merged to master in https://github.com/puppetlabs/puppet/commit/9a02831110b279adaca46f0602ef2e0b504047c0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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.
