Jira (BOLT-427) Create bolt-runtime project
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-427 Create bolt-runtime project Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-429) Create standalone Linux packages
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-429 Create standalone Linux packages Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-428) Create bolt-runtime build pipeline
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-428 Create bolt-runtime build pipeline Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8614) Add ruby 2.5.0 to travis and appveyor test matrices for puppet
Title: Message Title Sean McDonald assigned an issue to Sean McDonald Puppet / PUP-8614 Add ruby 2.5.0 to travis and appveyor test matrices for puppet Change By: Sean McDonald Assignee: Sean McDonald Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-456) Plans should restrict return types to expected values
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-456 Plans should restrict return types to expected values Change By: Alex Dreyer Labels: docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8638) Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc...
Title: Message Title Eric Sorenson commented on PUP-8638 Re: Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc... Isn't this a dup of PUP-1434? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-439) Allow nested subgroups in inventory files
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-439 Allow nested subgroups in inventory files Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-454) Plans should return undef without an explicit return
Title: Message Title Michael Smith assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-454 Plans should return undef without an explicit return Change By: Michael Smith Assignee: Michael Smith Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-429) Create standalone Linux packages
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-429
Create standalone Linux packages
Change By:
Michael Smith
Consume bolt-runtime in bolt-vanagon to produce standalone packages on current platforms we ship (Debian, Ubuntu, EL, SLES).Add paths.d config for {{/opt/puppetlabs/ bolt/ bin}}. Don't add Add Bolt to {{/opt/puppetlabs/bin}}.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8562) File performance nearly twice as slow after update
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-8562 File performance nearly twice as slow after update Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8562) File performance nearly twice as slow after update
Title: Message Title Josh Cooper commented on PUP-8562 Re: File performance nearly twice as slow after update Verified 5.3.5 with 200 empty file resources takes 19.33 seconds: $ time bx puppet agent -t --server orcdhca1u7lulpb.delivery.puppetlabs.net Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Info: Caching catalog for chara.corp.puppetlabs.net Info: Applying configuration version '1523049920' Notice: Applied catalog in 19.33 seconds bundle exec puppet agent -t --server orcdhca1u7lulpb.delivery.puppetlabs.net 19.24s user 1.59s system 83% cpu 24.880 total While it only takes 2.94 seconds in commit c87cb14a1f2ce1729fea68381f15a0b9f381f7fd $ time bx puppet agent -t --server orcdhca1u7lulpb.delivery.puppetlabs.net Info: Using configured
Jira (PUP-8638) Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc...
Title: Message Title Henrik Lindberg commented on PUP-8638 Re: Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc... It can be done as part of validation - an autoloaded piece of code should only contain the expected definition (or possibly multiple definitions). Other problems in the same category is defining the wrong name (a foo::myclass) inside of another module's class bar::someohterclass. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8639) need seamless way to replace expiring CA certificate
Title: Message Title James Ralston commented on PUP-8639 Re: need seamless way to replace expiring CA certificate Correction: someone asserted that puppet certregen is a face that the puppetlabs-certregen modules adds. But per the module dependencies, the module doesn't work with Puppet 5, and doesn't seem to be under active development. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-427) Create bolt-runtime project
Title: Message Title Michael Smith commented on BOLT-427 Re: Create bolt-runtime project Dropped having runtime rely on bolt-vanagon based on PA-1833. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-427) Create bolt-runtime project
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-427
Create bolt-runtime project
Change By:
Michael Smith
Update [bolt-vanagon|https://github.com/puppetlabs/bolt-vanagon] to declare install locations (that will initially be unused). Create a bolt Vanagon project in [puppet-runtime|https://github.com/puppetlabs/puppet-runtime] to generate an archive containing: ruby-2.4.3, rubygem-ffi, puppet-ca-bundle, runtime-pdk (which could be generalized to a basic ruby runtime, minus libstdc++ because it's not needed). Install to {{/opt/puppetlabs/bolt}}.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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
Jira (BOLT-427) Create bolt-runtime project
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-427
Create bolt-runtime project
Change By:
Michael Smith
Update [bolt-vanagon|https://github.com/puppetlabs/bolt-vanagon] to declare install locations (that will initially be unused).Create a bolt Vanagon project in [puppet-runtime|https://github.com/puppetlabs/puppet-runtime] to generate an archive containing: ruby-2.4.3, rubygem-ffi, puppet-ca-bundle, runtime-pdk (which could be generalized to a basic ruby runtime, minus libstdc++ because it's not needed). Install to {{/opt/puppetlabs/bolt}}.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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
Jira (PUP-8468) Failed to show puppet classes: 500 Api Request
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-8468 Failed to show puppet classes: 500 Api Request Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8468) Failed to show puppet classes: 500 Api Request
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8468 Failed to show puppet classes: 500 Api Request Change By: Henrik Lindberg Fix Version/s: PUP 5.5.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8562) File performance nearly twice as slow after update
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8562 File performance nearly twice as slow after update Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-440) Publish bolt orchestrator shim to the Puppet Forge
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-440 Publish bolt orchestrator shim to the Puppet Forge Change By: Michael Smith Assignee: Kate Lopresti Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8638) Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc...
Title: Message Title Nick Walker updated an issue Puppet / PUP-8638 Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc... Change By: Nick Walker CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8639) need seamless way to replace expiring CA certificate
Title: Message Title James Ralston created an issue Puppet / PUP-8639 need seamless way to replace expiring CA certificate Issue Type: New Feature Assignee: Unassigned Created: 2018/04/06 1:30 PM Priority: Normal Reporter: James Ralston What realistic option does a Puppet open source site have if the expiration on the CA master certificate is approaching, and one wants to smoothly transition to a new CA master certificate? The only official documentation I can find that comes close to this is the following: https://puppet.com/docs/puppet/5.5/ssl_regenerate_certificates.html But that procedure is describing an apocalypse-level security event where all certificates must be treated as untrustworthy and discarded. There is this: https://forge.puppet.com/puppetlabs/certregen …but that module hasn't been updated in almost a year, and is incompatible with Puppet 5, because Puppet 5 removed puppet certregen and replaced it with… nothing, as far as I can tell. The only potential solution I can see is this: https://blog.flyingcircus.io/2017/09/01/how-to-renew-puppet-ca-and-server-certificates-in-place/ Perhaps PE already has a smooth way to do this, but there needs to be a smooth way to do this for Puppet open source as well, without sending sites running open source scurrying to random third-party blog posts. I realize this is both a very unsexy and very challenging issue to solve, but for the sites that need to solve it… it's a DEFCON 1 event.
Jira (PUP-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts
Title: Message Title Jonathan Morris updated an issue Puppet / PUP-7326 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts Change By: Jonathan Morris Fix Version/s: PUP 4.10.11 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8468) Failed to show puppet classes: 500 Api Request
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8468 Failed to show puppet classes: 500 Api Request Change By: Josh Cooper Fix Version/s: PUP 5.3.6 Fix Version/s: PUP 5.3.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8638) Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc...
Title: Message Title Nick Walker updated an issue Puppet / PUP-8638 Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc... Change By: Nick Walker Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8638) Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc...
Title: Message Title Nick Walker commented on PUP-8638 Re: Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc... Henrik Lindberg I spoke with Josh Cooper about this issue and he thought you might have ideas on how this could be implemented. I'm hoping we can agree that the side-effects of unknowingly applying puppet code to your entire infrastructure because we don't have a way to fail compilation under this scenario is a serious problem that requires consideration. cc Reid Vandewiele Charlie Sharpsteen Jarret Lavallee Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1761) Infiniband's mac (hardware) address not provided
Title: Message Title Branan Riley updated an issue Facter / FACT-1761 Infiniband's mac (hardware) address not provided Change By: Branan Riley Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1761) Infiniband's mac (hardware) address not provided
Title: Message Title Branan Riley updated an issue Facter / FACT-1761 Infiniband's mac (hardware) address not provided Change By: Branan Riley Release Notes Summary: Fix reporting of MAC addresses to handle infiniband Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1765) Facter should not output a warning for a missing dmidecode component on Power Linux machines
Title: Message Title Branan Riley updated an issue Facter / FACT-1765 Facter should not output a warning for a missing dmidecode component on Power Linux machines Change By: Branan Riley Release Notes Summary: No longer report a warning on POWER Linux machines about missing dmidecode Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1765) Facter should not output a warning for a missing dmidecode component on Power Linux machines
Title: Message Title Branan Riley updated an issue Facter / FACT-1765 Facter should not output a warning for a missing dmidecode component on Power Linux machines Change By: Branan Riley Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-427) Create bolt-runtime project
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-427 Create bolt-runtime project Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-456) Plans should restrict return types to expected values
Title: Message Title Michael Smith assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-456 Plans should restrict return types to expected values Change By: Michael Smith Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8638) Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc...
Title: Message Title
Nick Walker updated an issue
Puppet / PUP-8638
Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc...
Change By:
Nick Walker
h1. The Problem You should not be able to accidentally include a class, resource, etc... on all nodes because of an incorrectly coded puppet module. *Actual Behavior:*Writing an init.pp for the module testmod that looks like the following: {code}class testmod { notify { 'hello_world':message => 'I am supposed to be here.' }}include testmod{code}Will cause testmod to be classified on all nodes as soon as testmod is parsed for any reason. h1. Suggested SolutionWe have a setting called [freeze_main|https://puppet.com/docs/puppet/5.5/configuration.html#freezemain] which sounds like it's supposed to provide a way to prevent this sort of behavior and it does for the simplest case but it seems to have an issue with our file resource default that sets backup => false in site.pp and with custom data types. I believe we should have a setting like freeze_main that allows the customer to enable the compiler to fail out if code is included outside of a class definition, defined type, etc...We should have a way to add resource defaults either in site.pp or some other way since the most common reason I can think of to have code outside of a class definition is for resource defaults in site.pp. h1. Customer ImpactThe issue may seem small but the result on user's systems is extremely severe. You apply puppet code to a node that isn't expecting it and it may be next to impossible to reverse those changes completely. If you apply certain firewall, security settings, or other low level settings you may actually take a node out of commission. h1. Related tickets https://tickets.puppetlabs.com/browse/PUP-8536https://tickets.puppetlabs.com/browse/PUP-2973https://tickets.puppetlabs.com/browse/PE-893 https://tickets.puppetlabs.com/browse/PUP-8637
Add Comment
Jira (PUP-8638) Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc...
Title: Message Title
Nick Walker created an issue
Puppet / PUP-8638
Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc...
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2018/04/06 1:08 PM
Priority:
Normal
Reporter:
Nick Walker
The Problem You should not be able to accidentally include a class, resource, etc... on all nodes because of an incorrectly coded puppet module. Actual Behavior: Writing an init.pp for the module testmod that looks like the following:
class testmod {
notify { 'hello_world':
message => 'I am supposed to be here.'
}
}
Jira (PUP-2973) Get rid of freeze_main
Title: Message Title
Nick Walker commented on PUP-2973
Re: Get rid of freeze_main
What freeze_main can prevent is code like the following in the definition for my_module from compiling and adding my_module to every node in an infrastructure.
class my_module {
notify { "this is my_module" :}
}
include my_module
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-2973) Get rid of freeze_main
Title: Message Title
Josh Cooper commented on PUP-2973
Re: Get rid of freeze_main
I may have spoken too soon. It does appear that setting freeze_main prevents you from doing the following in init.pp in a module:
class mymodule {
}
include mymodule
When running with freeze_main=true, it fails with:
Error: Evaluation Error: Error while evaluating a Function Call, Cannot have code outside of a class/node/define because 'freeze_main' is enabled (file: /Users/josh/.puppetlabs/etc/code/environments/production/manifests/site.pp, line: 1, column: 1) on node localhost
Error: Evaluation Error: Error while evaluating a Function Call, Cannot have code outside of a class/node/define because 'freeze_main' is enabled (file: /Users/josh/.puppetlabs/etc/code/environments/production/manifests/site.pp, line: 1, column: 1) on node localhost
Error: Server Error: Evaluation Error: Error while evaluating a Function Call, Cannot have code outside of a class/node/define because 'freeze_main' is enabled (file: /Users/josh/.puppetlabs/etc/code/environments/production/manifests/site.pp, line: 1, column: 1) on node localhost
/Users/josh/work/puppet/lib/puppet/util/errors.rb:157:in `fail'
/Users/josh/work/puppet/lib/puppet/resource/type.rb:192:in `merge'
Jira (PUP-8637) freeze_main setting breaks when used with type aliases
Title: Message Title
Reid Vandewiele created an issue
Puppet / PUP-8637
freeze_main setting breaks when used with type aliases
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/04/06 11:56 AM
Priority:
Normal
Reporter:
Reid Vandewiele
The freeze_main setting throws an error when used with code containing type aliases. Reproduction:
mkdir -p test/modules test/manifests
puppet module install --modulepath test/modules puppetlabs-stdlib
puppet module install --modulepath test/modules puppetlabs-haproxy
echo 'include haproxy; notify { "test": }' > test/manifests/site.pp
puppet apply --modulepath test/modules --freeze_main test/manifests/site.pp --noop
This error will be thrown:
Jira (FACT-1814) Mountpoints Fact available space does not accurately reflect disk usage
Title: Message Title Trevor Vaughan commented on FACT-1814 Re: Mountpoints Fact available space does not accurately reflect disk usage Charlie Sharpsteen Thanks! Is there a whitelist mode or do I need to implement my own custom fact to just get the "usual suspects" without running off the rails into insanity? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1814) Mountpoints Fact available space does not accurately reflect disk usage
Title: Message Title Charlie Sharpsteen commented on FACT-1814 Re: Mountpoints Fact available space does not accurately reflect disk usage Trevor Vaughan Check out FACT-718 which implemented the ability to block facts from collection — mountpoints were a pain point specifically targeted. Docs: https://puppet.com/docs/facter/3.10/configuring_facter.html#facts Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1814) Mountpoints Fact available space does not accurately reflect disk usage
Title: Message Title Trevor Vaughan commented on FACT-1814 Re: Mountpoints Fact available space does not accurately reflect disk usage Since you're messing around with mountpoints...there needs to be some way to exclude mountpoints from fact gathering. Some sites with large storage needs may have 1024+ LUNs and the facter run querying all of them is not a good thing. On the point at hand, why not report both? Add a new fact that reports 'unprivileged space' or something. That way, it's backwards compatible and you don't break things for people that run facter as a non-root user (please don't break things for non-root users). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-456) Plans should restrict return types to expected values
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-456
Plans should restrict return types to expected values
Change By:
Alex Dreyer
Currently plans can return pcore objects that cannot be handled outside the compiler. To avoid errors around this we should limit the acceptable return values of plan to the {{Data}} and the datatypes we expect plans to generate, {{Error}}, {{Result}}, {{ResultSet}}, and {{Target}}. As the plan language matures we may broaden this setIf a plan does not return an expected value run_plan should raise a Bolt::InvalidPlanResult value error. {noformat}{ kind: 'bolt/invalid-plan-result', message: "Plan #{plan_name} returned and invalid result of type #{datatype_name}" details: {plan_name: plan_name,type: datatype_name, }}{noformat}We should expose a new type alias {{ PlanData PlanResult }} to match the acceptable return values.{noformat}type PlanData PlanResult = Variant[Data, Error, Result, ResultSet, Target, Array[PlanData], Hash[String, PlanData]]{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-454) Plans should return undef without an explicit return
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-454 Plans should return undef without an explicit return Change By: Michael Smith Assignee: Alex Dreyer Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-372) Associate jobs with plans when using the PCP transport
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-372
Associate jobs with plans when using the PCP transport
Change By:
Michael Smith
During the first action that uses the PCP transport with a new config while running a plan attempt to use {{/commands/plan_start}} (providing the plan name of the top level plan called from the CLI, parameters and to orch) to get a plan_job_id plan_job id . If the command is not supported by Orchestrator, continue without a plan_job_id plan_job id and use the {{task}} command instead of {{plan_task}}. Other errors should halt the plan.The plan job id should be logged at notice level.Subsequent actions over the PCP transport with the same config should use the same plan_job_id plan_job id .On completion] Bolt should call {{/commands/plan_end}} for every orchestrator it's tracking a {{ plan_job_id plan_job }} id for. This indicates that transports need a concept of setup and teardown and the orchestrator transport needs to track "connections". Teardown should not be called on control+c.The name and parameters of nested plans are essentially ignored by the PCP transport. Only the plan named from the CLI should be used.Executor will need to pass information about the CLI invocation to transports to support this. It needs to know if it is running as part of a plan and if so what the plan info is. We may be able to simplify some logging using this too.Plan descriptions are out of scope for this ticket. It will eventually be a CLI --description argument (see BOLT-410)
Add Comment
Jira (BOLT-440) Publish bolt orchestrator shim to the Puppet Forge
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-440 Publish bolt orchestrator shim to the Puppet Forge Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1761) Infiniband's mac (hardware) address not provided
Title: Message Title Jonathan Morris updated an issue Facter / FACT-1761 Infiniband's mac (hardware) address not provided Change By: Jonathan Morris Fix Version/s: FACT 3.6.10 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1504) Uptime resolver fact for Windows uses unreliable metric for uptime
Title: Message Title Jonathan Morris updated an issue Facter / FACT-1504 Uptime resolver fact for Windows uses unreliable metric for uptime Change By: Jonathan Morris Fix Version/s: FACT 3.6.10 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1819) Facter.rb is swallowing useful exception details when failing to load libfacter
Title: Message Title Jonathan Morris updated an issue Facter / FACT-1819 Facter.rb is swallowing useful exception details when failing to load libfacter Change By: Jonathan Morris Fix Version/s: FACT 3.6.10 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8556) environment.conf modulepath should accept globs
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8556 environment.conf modulepath should accept globs Change By: Melissa Stone Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8561) Augeas unable to handle escaped quotes within quotes
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-8561 Augeas unable to handle escaped quotes within quotes Change By: Henrik Lindberg Assignee: David Lutterkort Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-459) Reboot a target and wait for it to become available.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-459
Reboot a target and wait for it to become available.
Change By:
Alex Dreyer
A lot of deployment workflows require a reboot step where the target will be inaccessible. There should be an option in plans to support this.Should there be a special plan function specifically targeted at rebooting? Should there be a plan function that waits for a target to become available leaving the reboot to some other step? Should there be a flag to run_* to signify the action will make the target inaccessible?Step one is probably to spike on a plan that will run a command, expect the execution to fail with a disconnect and then poll until the target is available again.{noformat} {noformat} plan reboot( $nodes, $command/task/script_params, $timeout = 120 ) { $result = run_task/command/script()$rebooting_targets = $result.map |$r|{ [types of disconnect].contains? $r.kind }.map |$r|{ $r.target }$failed = range(0, $timeout).reduce($rebooting_targets) |$down, $_| { $available = run_task(is_available, $down, _catch_errors => true) if $avilable.ok{ break [] }$available.error_set().targets } unless $failed.empty { fail_plan({ kind => 'bolt/reboot-failed' , msg => "Failed to reboot ${failed}", details =>{ "failed_target" => $failed }}{noformat} {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-459) Reboot a target and wait for it to become available.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-459
Reboot a target and wait for it to become available.
Change By:
Alex Dreyer
A lot of deployment workflows require a reboot step where the target will be inaccessible. There should be an option in plans to support this.Should there be a special plan function specifically targeted at rebooting? Should there be a plan function that waits for a target to become available leaving the reboot to some other step? Should there be a flag to run_* to signify the action will make the target inaccessible?Step one is probably to spike on a plan that will run a command, expect the execution to fail with a disconnect and then poll until the target is available again. {noformat} {noformat} plan reboot( $nodes, $command/task/script_params, $timeout = 120 ) { $result = run_task/command/script()$rebooting_targets = $result.map |$r| { { [types of disconnect].contains? $r.kind } .map |$r|{ $r.target }$failed = range(0, $timeout).reduce($rebooting_targets) |$down, $_| { $available = run_task(is_available, $down, _catch_errors => true) if $avilable.ok{ break [] }$available.error_set().targets } unless $failed.empty { fail_plan({ kind => 'bolt/reboot-failed' , msg => "Failed to reboot ${failed}", details =>{ "failed_target" => $failed } } {noformat} {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-459) Reboot a target and wait for it to become available.
Title: Message Title
Alex Dreyer created an issue
Puppet Task Runner / BOLT-459
Reboot a target and wait for it to become available.
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/04/06 9:46 AM
Priority:
Normal
Reporter:
Alex Dreyer
A lot of deployment workflows require a reboot step where the target will be inaccessible. There should be an option in plans to support this. Should there be a special plan function specifically targeted at rebooting? Should there be a plan function that waits for a target to become available leaving the reboot to some other step? Should there be a flag to run_* to signify the action will make the target inaccessible? Step one is probably to spike on a plan that will run a command, expect the execution to fail with a disconnect and then poll until the target is available again. plan reboot( $nodes, $command/task/script_params, $timeout = 120 ) { $result = run_task/command/script() $rebooting_targets = $result.map |$r| { [types of disconnect].contains? $r.kind } .map |$r| { $r.target } $failed = range(0, $timeout).reduce($rebooting_targets) |$down, $_| { $available = run_task(is_available, $down, _catch_errors => true) if $avilable.ok { break [] } $available.error_set().targets } unless $failed.empty { fail_plan({ kind => 'bolt/reboot-failed' , msg => "Failed to reboot ${failed}", details => { "failed_target" => $failed } }
Add Comment
Jira (PUP-8556) environment.conf modulepath should accept globs
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8556 environment.conf modulepath should accept globs Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-439) Allow nested subgroups in inventory files
Title: Message Title David Kramer assigned an issue to Unassigned Puppet Task Runner / BOLT-439 Allow nested subgroups in inventory files Change By: David Kramer Assignee: Michal Ruzicka Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-454) Plans should return undef without an explicit return
Title: Message Title David Kramer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-454 Plans should return undef without an explicit return Change By: David Kramer Assignee: Michael Smith Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-454) Plans should return undef without an explicit return
Title: Message Title David Kramer assigned an issue to Michael Smith Puppet Task Runner / BOLT-454 Plans should return undef without an explicit return Change By: David Kramer Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-458) Document using facts plans and Target properties
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-458 Document using facts plans and Target properties Issue Type: Task Assignee: Unassigned Created: 2018/04/06 9:06 AM Priority: Normal Reporter: Michael Smith Add documentation to writing plans that covers retrieving and using facts. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-458) Document using facts plans and Target properties
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-458 Document using facts plans and Target properties Change By: Michael Smith Labels: docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-410) run_* functions should accept a description
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-410 run_* functions should accept a description Change By: Michael Smith Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-370) file_upload() function docs should have a caveat for transferring large files
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-370 file_upload() function docs should have a caveat for transferring large files Change By: Michael Smith Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-395) Improve documentation
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-395 Improve documentation Change By: Michael Smith Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-370) file_upload() function docs should have a caveat for transferring large files
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-370 file_upload() function docs should have a caveat for transferring large files Change By: Michael Smith Labels: docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-440) Publish bolt orchestrator shim to the Puppet Forge
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-440 Publish bolt orchestrator shim to the Puppet Forge Change By: Michael Smith Labels: docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-440) Publish bolt orchestrator shim to the Puppet Forge
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-440 Publish bolt orchestrator shim to the Puppet Forge Change By: Michael Smith Assignee: Alex Dreyer Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-440) Publish bolt orchestrator shim to the Puppet Forge
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-440 Publish bolt orchestrator shim to the Puppet Forge Change By: Michael Smith Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-457) Facter PowerShell task relies on method that is not implemented in all versions of .NET
Title: Message Title Michael Smith commented on BOLT-457 Re: Facter PowerShell task relies on method that is not implemented in all versions of .NET Did any of those links point to a better approach? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8636) Don't prefetch if every resource using a provider is noop'd or no scheduled
Title: Message Title
Martin Ewings updated an issue
Puppet / PUP-8636
Don't prefetch if every resource using a provider is noop'd or no scheduled
Change By:
Martin Ewings
When a Particular Resource provider is defaulting to No-op or is part of a schedule which is not active, Puppet shouldn't prefetch any data relating to that provider in order to speed up compilation, for example: {code:java} schedule { 'narrow': range => '1:01 - 1:02', }Package <| provider == 'pkgutil' |> { schedule => 'narrow', } {code} this works in that the packages are skipped, the background provider tasks are still being completed:{code:java} Prefetching pkgutil resources for packageDebug: Executing: '/opt/csw/bin/pkgutil -a'Debug: Executing: '/opt/csw/bin/pkgutil -c'Debug: /Package[sudo]: Not scheduledDebug: /Package[sudo]: Resource is being skipped, unscheduling all eventsDebug: /Package[name]: Not scheduledDebug: /Package[name]: Resource is being skipped, unscheduling all events{code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8634) Chown of ssldir Causing Failures
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8634 Chown of ssldir Causing Failures Change By: Craig Gomes Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8636) Don't prefetch if every resource using a provider is noop'd or no scheduled
Title: Message Title Martin Ewings updated an issue Puppet / PUP-8636 Don't prefetch if every resource using a provider is noop'd or no scheduled Change By: Martin Ewings CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8636) Don't prefetch if every resource using a provider is noop'd or no scheduled
Title: Message Title
Martin Ewings created an issue
Puppet / PUP-8636
Don't prefetch if every resource using a provider is noop'd or no scheduled
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2018/04/06 7:16 AM
Priority:
Normal
Reporter:
Martin Ewings
When a Particular Resource provider is defaulting to No-op or is part of a schedule which is not active, Puppet shouldn't prefetch any data relating to that provider in order to speed up compilation, for example:
schedule { 'narrow':
range => '1:01 - 1:02',
}
Package <| provider == 'pkgutil' |> {
schedule => 'narrow',
Jira (PUP-8635) Add a Deferred data type for lazy function call
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8635 Add a Deferred data type for lazy function call Issue Type: New Feature Assignee: Henrik Lindberg Created: 2018/04/06 6:32 AM Priority: Normal Reporter: Henrik Lindberg Add a data type Deferred that is used to describe a function call that is to be performed in the future (at some time when a resolution/call is wanted). The data type should be an Object and have the attributes name - the name of the function, and optional arguments an array with arguments to the function. The data type is not parameterized. While it would be of interest to have a Deferred[T] where T is the return type - this gets complicated as it is not possible in general to infer what the return type of a variable is because of overloading. We do not have such functionality (yet) in puppet and adding this could be done sometime in the future to ensure that the result of a deferred has a particular data type. This will most likely also mean that an instance of Deferred will need to have that type as a type constraint. The same can however be achieved by making a deferred call to assert_type, and giving a Deferred as an argument. Add Comment
Jira (PUP-8240) ERB and EPP templates handle CRLF line endings inconsistently
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-8240 ERB and EPP templates handle CRLF line endings inconsistently Change By: Henrik Lindberg Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8240) ERB and EPP templates handle CRLF line endings inconsistently
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8240 ERB and EPP templates handle CRLF line endings inconsistently Change By: Henrik Lindberg Release Notes Summary: EPP templates containing CRLF line breaks did not generate files containing CRLF line breaks, which is the expected result and also the result when using CRLF line breaks in ERB templates. This is now corrected. Also, when using CRLF escape sequences (`\r\n`) in either ERB or EPP templates, Puppet doesn't convert the sequences to CRLF line breaks as expected. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8240) ERB and EPP templates handle CRLF line endings inconsistently
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8240 ERB and EPP templates handle CRLF line endings inconsistently Change By: Henrik Lindberg Release Notes Summary: EPP templates that contain containing CRLF line breaks do did not generate files containing CRLF line breaks, which is the expected result and also the result when using CRLF line breaks in ERB templates. This is now corrected. Also, when using CRLF escape sequences (`\r\n`) in either ERB or EPP templates, Puppet doesn't convert the sequences to CRLF line breaks as expected. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8240) ERB and EPP templates handle CRLF line endings inconsistently
Title: Message Title Henrik Lindberg commented on PUP-8240 Re: ERB and EPP templates handle CRLF line endings inconsistently My first attempt of solving this was both naive (hoping it would cure all problems oft this kind) but I got it wrong. The FileSystem.read takes options, and those are naturally used - just trying to delegate to read_preserve_line_endings won't work as that method does not take options. While possible to add optional options to that method, it in itself does things with options with respect to encoding, and it would need to get more complicated if it were to also try to honour the various options that can be passed into Ruby's read. Also, the read_preserve_line_endings may result in a String that is not UTF-8. Instead, I fixed the issue for Puppet and EPP by modifying the lexer to read with 'rb' mode and with UTF-8 encoding. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8634) Chown of ssldir Causing Failures
Title: Message Title Daniel Mcilhagga created an issue Puppet / PUP-8634 Chown of ssldir Causing Failures Issue Type: New Feature Assignee: Unassigned Created: 2018/04/06 1:01 AM Priority: Normal Reporter: Daniel Mcilhagga Currently Puppet as part of the install does a chown of the ssldir to puppet:puppet. A customer is currently asking if it is possible to disable this functionality. Below is a description of the customer's use case. "We only have a user called 'puppet' on a handful of our unix clients (relatively speaking - it is a few hundred), and for all other hosts the $ssldir is owned by root:root. We know why the GID isn't resolving (missing LDAP data) but as the use of a 'puppet' account on clients doesn't appear to gain us anything but causes the occasional agent installation failure (impacting our build automation) I wanted to look at preventing the chown operation during agent install." Add Comment
Jira (FACT-1843) Make prtdiag timeout configurable on Solaris
Title: Message Title Stefan Pijnappels commented on FACT-1843 Re: Make prtdiag timeout configurable on Solaris This appears to have been addressed in a number of previous Jiras such as FACT-547, FACT-825, FACT-922 and FACT-1408, but this is still manifesting on Facter 3.6.4 on PE2016.4.9. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1843) Make prtdiag timeout configurable on Solaris
Title: Message Title Stefan Pijnappels created an issue Facter / FACT-1843 Make prtdiag timeout configurable on Solaris Issue Type: Improvement Affects Versions: FACT 3.6.4 Assignee: Unassigned Created: 2018/04/06 12:50 AM Priority: Normal Reporter: Stefan Pijnappels From a customer report, when facter runs on some Solaris nodes, prtdiag may time out if it takes a long time to run. It appears that prtdiag is only used to get the productname, and as this is returned first by prtdiag the fact is still returned, along with an error message saying that prtdiag has timed out. This appears to be purely cosmetic as the correct (expected) info is returned, but if the timeout could be made configurable, or the error suppressed, this would allow the facter run to completely without extraneous output. Problem Illustration: # /opt/puppetlabs/puppet/bin/facter -p productname (ctrl-111) Ovcd is not yet started.
