Jira (PUP-9826) Puppet exec timeout does not match documentation
Title: Message Title Josh Cooper commented on PUP-9826 Re: Puppet exec timeout does not match documentation The timeout applies to each try, but the problem is if a timeout occurs for any one try, then the entire resource is marked as failed, instead of continuing to retry. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316540.1563215346000.17292.1563252660103%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9826) Puppet exec timeout does not match documentation
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9826 Puppet exec timeout does not match documentation Change By: Josh Cooper 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316540.1563215346000.17267.1563248700187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9209) Don't support the home property on Windows users
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9209 Don't support the home property on Windows users Change By: Josh Cooper Fix Version/s: PUP 7.0.0 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.279042.1538689778000.17193.1563234720174%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8305) Git testing should consume the runtime archive rather than install system packages
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8305 Git testing should consume the runtime archive rather than install system packages Change By: Josh Cooper Fix Version/s: PUP 6.0.z Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.228912.1515016048000.17181.1563234660620%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8349) SPIKE scheduled_task : should we deprecate scheduled_task resource?
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8349 SPIKE scheduled_task : should we deprecate scheduled_task resource? Change By: Josh Cooper Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.229519.1515439294000.17189.1563234660655%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7990) Create internal puppet API implementation satisfying requirements for win32-service
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7990 Create internal puppet API implementation satisfying requirements for win32-service Change By: Josh Cooper Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.213012.1506362553000.17177.1563234660586%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7262) 5.y Model - model related things in the 5.y release cycle
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7262 5.y Model - model related things in the 5.y release cycle Change By: Josh Cooper Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.176569.1487944921000.17161.1563234600872%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7269) SPIKE: split non-core functionality out of puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7269 SPIKE: split non-core functionality out of puppet Change By: Josh Cooper Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.176683.1487961466000.17163.1563234600878%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7618) PSON -> JSON Testing
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7618 PSON -> JSON Testing Change By: Josh Cooper Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.194241.1496440966000.17172.1563234600911%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7512) Explore FIPS certification of our openssl
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7512 Explore FIPS certification of our openssl Change By: Josh Cooper Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.190040.1494396439000.17169.1563234600901%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6920) Windows package provider should set working directory (cwd)
Title: Message Title Josh Cooper commented on PUP-6920 Re: Windows package provider should set working directory (cwd) Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/60eedb0c143ea7b43251776a11708130fbe50fb0 and first released in 5.5.7 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.161236.1479279288000.17149.1563234480321%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6920) Windows package provider should set working directory (cwd)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6920 Windows package provider should set working directory (cwd) Change By: Josh Cooper Fix Version/s: PUP 5.y Fix Version/s: PUP 5.5.7 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.161236.1479279288000.17152.1563234480336%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6722) User Phase 1 Type/Provider Improvements
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6722 User Phase 1 Type/Provider Improvements Change By: Josh Cooper Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.153106.1474501632000.17143.1563234420091%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5757) Replace win32-service calls with internal API implementations that are wide-string compatibles
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5757 Replace win32-service calls with internal API implementations that are wide-string compatibles Change By: Josh Cooper Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.114063.1453854158000.17138.1563234360401%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3715) Determine package provider tests to be added
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3715 Determine package provider tests to be added Change By: Josh Cooper Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.59917.1417041339000.17100.1563234302150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5518) Puppet lookup: document precedence of mixed styles of defaults
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5518 Puppet lookup: document precedence of mixed styles of defaults Change By: Josh Cooper Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.106413.144793082.17134.1563234302645%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3021) User resource on AIX returns a non-working structure or 'attributes'
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3021 User resource on AIX returns a non-working structure or 'attributes' Change By: Josh Cooper Fix Version/s: PUP 5.y Fix Version/s: PUP 5.5.7 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.46494.1407249153000.17097.1563234301971%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5068) Windows - Allow logging to a different event log
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5068 Windows - Allow logging to a different event log Change By: Josh Cooper Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.94718.1440428723000.17130.1563234302595%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4457) Puppet::Node::Facts add_local_facts -- review for deprecation
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4457 Puppet::Node::Facts add_local_facts -- review for deprecation Change By: Josh Cooper Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.77114.1429739346000.17103.1563234302255%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4669) Varargs support for "args by name" calls to user defined resource types and EPP templates
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4669 Varargs support for "args by name" calls to user defined resource types and EPP templates Change By: Josh Cooper Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.82102.1432890543000.17113.1563234302461%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4682) Deprecate Cisco types/providers
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4682 Deprecate Cisco types/providers Change By: Josh Cooper Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.82785.1433278523000.17122.1563234302533%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6716) Error when purging local users on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6716 Error when purging local users on Windows Change By: Josh Cooper Fix Version/s: PUP 5.y Fix Version/s: PUP 5.5.7 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.106593.1448040542000.17070.1563234240690%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2149) Deprecate implicit creation of symlinks when file ensure parameter is unknown
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2149 Deprecate implicit creation of symlinks when file ensure parameter is unknown Change By: Josh Cooper Fix Version/s: PUP 5.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.30952.1396554658000.17075.1563234240707%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3021) User resource on AIX returns a non-working structure or 'attributes'
Title: Message Title Josh Cooper commented on PUP-3021 Re: User resource on AIX returns a non-working structure or 'attributes' Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/67495be0e1a5d924522adb7d83a2a9cf9c910431 and first released in 5.5.7 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.46494.1407249153000.17086.1563234240766%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6716) Error when purging local users on Windows
Title: Message Title Josh Cooper commented on PUP-6716 Re: Error when purging local users on Windows Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/46de26c468fc78ae0a0ab8ad9aa1eb5ed8a819e9 and first released in 5.5.7 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.106593.1448040542000.17060.1563234180265%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4605) With a systemd masked service: 'enable=true ensure=running' doesn't work on CentOS with default selinux rules
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4605 With a systemd masked service: 'enable=true ensure=running' doesn't work on CentOS with default selinux rules Change By: Josh Cooper Fix Version/s: PUP 4.2.2 Fix Version/s: PUP 5.5.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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.80006.1431544434000.17046.1563234060625%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8495) Ubuntu 16.10 _AND NEWER_ use systemd provider as default
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8495 Ubuntu 16.10 _AND NEWER_ use systemd provider as default Change By: Josh Cooper Fix Version/s: PUP 5.3.6 Fix Version/s: PUP 5.5.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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.238529.1519746382000.17033.1563233940484%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8495) Ubuntu 16.10 _AND NEWER_ use systemd provider as default
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8495 Ubuntu 16.10 _AND NEWER_ use systemd provider as default Change By: Josh Cooper Fix Version/s: PUP 5.5.1 Fix Version/s: PUP 5.5.0 Fix Version/s: PUP 4.10.11 Fix Version/s: PUP 6.0.0 Fix Version/s: PUP 5.5.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
Jira (PUP-8495) Ubuntu 16.10 _AND NEWER_ use systemd provider as default
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8495 Ubuntu 16.10 _AND NEWER_ use systemd provider as default Change By: Josh Cooper Fix Version/s: PUP 5.5.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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.238529.1519746382000.17023.1563233880759%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9819) Puppet Failure on MacOS 10.15 'Catalina' Beta3
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9819 Puppet Failure on MacOS 10.15 'Catalina' Beta3 Change By: Josh Cooper Fix Version/s: PUP 6.4.0 Fix Version/s: PUP 6.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316143.1562866804000.17013.1563233820135%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9698) Backport PUP-8967 to 5.5.x
Title: Message Title Jean Bond updated an issue Puppet / PUP-9698 Backport PUP-8967 to 5.5.x Change By: Jean Bond Labels: resolved-issue-added 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308037.1557423516000.16927.1563231840244%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8970) Puppet cron acceptance tests should be skipped on Fedora 28
Title: Message Title Josh Cooper commented on PUP-8970 Re: Puppet cron acceptance tests should be skipped on Fedora 28 First released in 5.5.3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.263028.153013708.16925.1563231780074%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8970) Puppet cron acceptance tests should be skipped on Fedora 28
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8970 Puppet cron acceptance tests should be skipped on Fedora 28 Change By: Josh Cooper Fix Version/s: PUP 5.5.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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.263028.153013708.16923.1563231720372%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9068) Windows admin? check should consider group membership
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9068 Windows admin? check should consider group membership Change By: Josh Cooper Fix Version/s: PUP 5.5.z Fix Version/s: PUP 5.5.7 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.271381.153435409.16921.1563231720365%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9107) Deprecate non-manifest orderings
Title: Message Title Josh Cooper commented on PUP-9107 Re: Deprecate non-manifest orderings This was first released in 5.5.7 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.274396.1536179051000.16913.1563231660147%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9107) Deprecate non-manifest orderings
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9107 Deprecate non-manifest orderings Change By: Josh Cooper Fix Version/s: PUP 5.5.z Fix Version/s: PUP 5.5.7 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.274396.1536179051000.16911.1563231660139%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9647) Pip package provider does not handle pip executable paths with spaces
Title: Message Title Josh Cooper commented on PUP-9647 Re: Pip package provider does not handle pip executable paths with spaces Ah nice find Sean Millichamp! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305257.133562000.16876.1563230220114%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9295) Notify resource exposes Sensitive data when message is a Sensitive data
Title: Message Title Kris Bosland commented on PUP-9295 Re: Notify resource exposes Sensitive data when message is a Sensitive data The team is coming to the view that the least surprise for users is if only code specifically designed to handle Sensitive values can get the unredacted version. It should not show up in even Debug logs by default, because that requires our users to manage their debug logs and reports as Sensitive data. This is a larger scale engineering effort, and we will work towards tickets and epics to outline this work. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.283215.1540998541000.16863.1563229920271%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs
Title: Message Title Josh Cooper commented on PUP-8736 Re: /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs Agree we don't want to "move the device confdirs from /opt/puppetlabs/puppet/cache to /etc/puppetlabs/puppet" since it current contains things like state directory, which we don't want in /etc. I'd recommend: 1. Add puppet settings to defaults.rb for the /etc/puppetlabs/puppet/devices and /etc/puppetlabs/puppet/devices/ssl directories in the main section 2. In the device application, when managing a specific device, set Puppet[:ssldir] = "/etc/puppetlabs/puppet/devices/ssl/" and then call Puppet.settings.use(:main, etc) 3. Continue to use Puppet[:devicedir] to refer to the var related stuff. 4. Add symlink so /etc/puppetlabs/puppet/devices/ssl/DEVICE points to /opt/puppetlabs/puppet/cache/devices/DEVICE/ssl 5. Update file_paths.md One question though. Are there going to be other per device conf related stuff that need to live in /etc? If so, then we should probably use /etc/puppetlabs/puppet/devices/DEVICE/ssl instead, so that we can create additional directories under DEVICE. 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. To view this discussion on the web visit
Jira (PUP-9792) Merge of lookup_options not working
Title: Message Title Henrik Lindberg commented on PUP-9792 Re: Merge of lookup_options not working Jorie Tappa Someone needs to set up and try to reproduce his case. I added some notes about things to look at - for example, does this work if the hierarchy does not depend on compilation - something that Matt Dainty could try as well as someone at Puppet. This could also be a bug that has been fixed as he is using Puppet 5.5.14. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313541.1561115342000.16749.1563227640192%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Henrik Lindberg commented on PUP-9816 Re: puppet parser validate version 6.6.0 does not accept STDIN properly Jesse Scott, Jorie Tappa I reviewed the PR - looks fine. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315541.1562618702000.16726.1563227160247%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1888) 'os.release' values not correct for VZ7
Title: Message Title Jean Bond updated an issue Facter / FACT-1888 'os.release' values not correct for VZ7 Change By: Jean Bond Labels: community help_wanted resolved-issue-added virtualization 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.278967.1538669961000.16705.1563225960349%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1910) Mountpoint fact only shows tmpfs and physical mounts
Title: Message Title Jean Bond updated an issue Facter / FACT-1910 Mountpoint fact only shows tmpfs and physical mounts Change By: Jean Bond Labels: resolved-issue-added 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.299364.1552075723000.16700.1563225720176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-284) Release dyna_symbols fix
Title: Message Title Tom Beech created an issue Puppet Strings / PDOC-284 Release dyna_symbols fix Issue Type: Improvement Assignee: Unassigned Created: 2019/07/15 2:16 PM Priority: Normal Reporter: Tom Beech Currently Bolt is pinning the yard gem to 0.9.19 due to an update in 0.9.20 that changes how symbols are parsed. A security alert was recently sent out concerning a vulnerability with 0.9.19, and being able to unpin from 0.9.19 would resolve this issue. Since the issue caused by 0.9.20 was corrected by a recent PR to puppet-strings (https://github.com/puppetlabs/puppet-strings/pull/206), making a release would allow Bolt to unpin the yard gem. Add Comment This message was sent by Atlassian
Jira (PUP-9813) Performance of unpacking modules is extremely slow
Title: Message Title Josh Cooper commented on PUP-9813 Re: Performance of unpacking modules is extremely slow Added comments on the PR: https://github.com/puppetlabs/puppet/pull/7602#issuecomment-511561502 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315304.156219440.16685.1563225240249%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1473) Release dyna_symbols fix for puppet-strings
Title: Message Title Tom Beech created an issue Puppet Task Runner / BOLT-1473 Release dyna_symbols fix for puppet-strings Issue Type: Improvement Assignee: Unassigned Created: 2019/07/15 2:13 PM Priority: Normal Reporter: Tom Beech Currently Bolt is pinning the yard gem to 0.9.19 due to an update in 0.9.20 that changes how symbols are parsed. A security alert was recently sent out concerning a vulnerability with 0.9.19, and being able to unpin from 0.9.19 would resolve this issue. Since the issue caused by 0.9.20 was corrected by a recent PR to puppet-strings (https://github.com/puppetlabs/puppet-strings/pull/206), making a release would allow Bolt to unpin the yard gem. Add Comment This message
Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Jesse Scott commented on PUP-9816 Re: puppet parser validate version 6.6.0 does not accept STDIN properly Jorie Tappa not sure who I should ping for review of the fix PR ^^ 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315541.1562618702000.16660.1563224700099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Jesse Scott commented on PUP-9816 Re: puppet parser validate version 6.6.0 does not accept STDIN properly Opened https://github.com/puppetlabs/puppet/pull/7611 which should resolve this. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315541.1562618702000.16652.1563224580333%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Jesse Scott commented on PUP-9816 Re: puppet parser validate version 6.6.0 does not accept STDIN properly Yes, sorry I did not mean to imply that a blank manifest was the only example. Any manifest that does not produce parse errors will trigger this, of which a blank manifest is the minimal example. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315541.1562618702000.16649.1563224460116%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Konrad Scherer commented on PUP-9816 Re: puppet parser validate version 6.6.0 does not accept STDIN properly I see it both with empty files and large valid puppet files like my manifests/nodes.pp 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315541.1562618702000.16562.1563222900429%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1916) facter fails to parse routing table
Title: Message Title Jean Bond updated an issue Facter / FACT-1916 facter fails to parse routing table Change By: Jean Bond Labels: resolved-issue-added 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307043.155680303.16557.1563222780306%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Jesse Scott commented on PUP-9816 Re: puppet parser validate version 6.6.0 does not accept STDIN properly This seems to only surface when there are no parse errors in the manifest. (E.g. a blank manifest) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315541.1562618702000.16538.1563222480370%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1918) Facter is pinned to ruby version 2.1.7
Title: Message Title Jean Bond updated an issue Facter / FACT-1918 Facter is pinned to ruby version 2.1.7 Change By: Jean Bond Labels: resolved-issue-added 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307213.1556842594000.16541.1563222480382%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9638) Add an option to verify the CA bundle download against a fingerprint
Title: Message Title Josh Cooper commented on PUP-9638 Re: Add an option to verify the CA bundle download against a fingerprint Passed CI in f29b9681e7 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.304299.1554918771000.16489.1563221640176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9826) Puppet exec timeout does not match documentation
Title: Message Title
Nate McCurdy commented on PUP-9826
Re: Puppet exec timeout does not match documentation
exec { 'test':
command => '/bin/sleep 5; /bin/false',
tries => 10,
try_sleep => 1,
timeout => 4,
}
That triggers the timeout error, but this does not:
exec { 'test':
command => '/bin/sleep 4; /bin/false',
tries => 10,
try_sleep => 1,
timeout => 5,
}
Jira (PUP-8711) Implement Agent Functions to support secret lookups at catalog application time
Title: Message Title Henrik Lindberg commented on PUP-8711 Re: Implement Agent Functions to support secret lookups at catalog application time Lindsey Smith Those open PRs are all from me and they are about feature / changes beyond what this ticket is about. A couple of details: PUP-9323 is not really possible to do in a good way given that many resource types need to read all the parameters and would force resolution of deferred values which works against the desire to resolve just before apply. Worth revisiting in the future as resource framework changes. I think PUP-9254 should be merged as it makes it dead simple instead of having to jump through hoops to do certain things (see that ticket). And PUP-8971 got stuck after it was reviewed as I need help to address what was asked for - also a question about how valuable the feature really is. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.250291.1525994276000.16337.1563217080312%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9826) Puppet exec timeout does not match documentation
Title: Message Title
Nate McCurdy updated an issue
Puppet / PUP-9826
Puppet exec timeout does not match documentation
Change By:
Nate McCurdy
*Puppet Version: 5.5.14-1xenial *Puppet Server Version: 5.3.8-1xenial *OS Name/Version: Ubuntu 16.04 XenialDescribe your issue in as much detail as possible…When using tries in an exec resource the documentation states that the timeout parameter of the exec block applies to each try, but the code currently does not implement the functionality in that way. The timeout should apply to each try.Slack community chat snippet{quote}natemccurdy [11 minutes ago] The timeout is for *the entire exec*, not for each try. (edited)Jason Grammenos [10 minutes ago] `Note that the timeout parameter applies to each try rather than to the complete set of tries.`natemccurdy [10 minutes ago] err.. sorry, You’re right.natemccurdy [10 minutes ago] Read that wrong.josh [9 minutes ago] The docs are wrong unfortunatelyJason Grammenos [9 minutes ago] oh?natemccurdy [9 minutes ago] Oh, hah :slightly_smiling_face:josh [8 minutes ago] maybe it used to apply to each try at some point?natemccurdy [8 minutes ago] Either way, try removing the `timeout` or set it to `0` and see what happens.josh [6 minutes ago] Looks like it's been broken since [https://github.com/puppetlabs/puppet/commit/e0e6b642c4e]josh [5 minutes ago] The begin/rescue needs to be inside `tries.times do |try|` Describe steps to reproduce… {quote} *Desired Behavior:* {code} exec { 'test': command => '/bin/false', tries => 10, try_sleep => 5, timeout => 10,}{code} This should have a per try timeout of 10 seconds as per the documentation.*Actual Behavior:*The exec time's out because the current implementation applies the timeout to the whole set of tries.current documentation:[https://puppet.com/docs/puppet/6.6/types/exec.html#exec-attribute-tries]Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.{code} Exec try 1/10 /etc/puppetlabs/code/modules/mm/manifests/graylog/graylog.pp:83 Jul 15 2019 - 14:10:34 Exec[configure-ldap](provider=posix) Executing 'curl -s -v -i --netrc-file /etc/graylog/server/configure_ldap.netrc -o /etc/graylog/server/configure_ldap.log -H "Content-Type: application/json" -H "X-Requested-By: puppet" -X PUT [http://localhost:9000/api/system/ldap/settings] --data @/etc/graylog/server/configure_ldap_data.json 2>&1 | grep 'HTTP/1.1 204''Jul 15 2019 - 14:10:34 Puppet debug Executing: 'curl -s -v -i --netrc-file /etc/graylog/server/configure_ldap.netrc -o /etc/graylog/server/configure_ldap.log -H "Content-Type: application/json" -H "X-Requested-By: puppet" -X PUT [http://localhost:9000/api/system/ldap/settings] --data @/etc/graylog/server/configure_ldap_data.json 2>&1 | grep 'HTTP/1.1 204'' Jul 15 2019 - 14:10:44 Puppet err Command exceeded timeout {code}
Jira (PUP-9826) Puppet exec timeout does not match documentation
Title: Message Title
Nate McCurdy updated an issue
Puppet / PUP-9826
Puppet exec timeout does not match documentation
Change By:
Nate McCurdy
*Puppet Version: 5.5.14-1xenial *Puppet Server Version: 5.3.8-1xenial *OS Name/Version: Ubuntu 16.04 XenialDescribe your issue in as much detail as possible…When using tries in an exec resource the documentation states that the timeout parameter of the exec block applies to each try, but the code currently does not implement the functionality in that way. The timeout should apply to each try.Slack community chat snippet{quote}natemccurdy [11 minutes ago] The timeout is for *the entire exec*, not for each try. (edited)Jason Grammenos [10 minutes ago] `Note that the timeout parameter applies to each try rather than to the complete set of tries.`natemccurdy [10 minutes ago] err.. sorry, You’re right.natemccurdy [10 minutes ago] Read that wrong.josh [9 minutes ago] The docs are wrong unfortunatelyJason Grammenos [9 minutes ago] oh?natemccurdy [9 minutes ago] Oh, hah :slightly_smiling_face:josh [8 minutes ago] maybe it used to apply to each try at some point?natemccurdy [8 minutes ago] Either way, try removing the `timeout` or set it to `0` and see what happens.josh [6 minutes ago] Looks like it's been broken since [https://github.com/puppetlabs/puppet/commit/e0e6b642c4e]josh [5 minutes ago] The begin/rescue needs to be inside `tries.times do |try|` Describe steps to reproduce…{quote}*Desired Behavior:* {code} exec { 'test': command => '/bin/false', tries => 10, try_sleep => 5, timeout => 10,}{code} This should have a per try timeout of 10 seconds as per the documentation.*Actual Behavior:*The exec time's out because the current implementation applies the timeout to the whole set of tries.current documentation: [https://puppet.com/docs/puppet/ 5 6 . 3 6 /types/exec.html#exec-attribute-tries]Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. {code} Exec try 1/10 /etc/puppetlabs/code/modules/mm/manifests/graylog/graylog.pp:83 Jul 15 2019 - 14:10:34 Exec[configure-ldap](provider=posix) Executing 'curl -s -v -i --netrc-file /etc/graylog/server/configure_ldap.netrc -o /etc/graylog/server/configure_ldap.log -H "Content-Type: application/json" -H "X-Requested-By: puppet" -X PUT [http://localhost:9000/api/system/ldap/settings] --data @/etc/graylog/server/configure_ldap_data.json 2>&1 | grep 'HTTP/1.1 204''Jul 15 2019 - 14:10:34 Puppet debug Executing: 'curl -s -v -i --netrc-file /etc/graylog/server/configure_ldap.netrc -o /etc/graylog/server/configure_ldap.log -H "Content-Type: application/json" -H "X-Requested-By: puppet" -X PUT [http://localhost:9000/api/system/ldap/settings] --data @/etc/graylog/server/configure_ldap_data.json 2>&1 | grep 'HTTP/1.1 204'' Jul 15 2019 - 14:10:44 Puppet err Command exceeded timeout {code}
Jira (PUP-9826) Puppet exec timeout does not match documentation
Title: Message Title Nate McCurdy commented on PUP-9826 Re: Puppet exec timeout does not match documentation Here's the faulty block of code: https://github.com/puppetlabs/puppet/blob/6.6.0/lib/puppet/type/exec.rb#L129-L142 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316540.1563215346000.16321.1563216180448%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9826) Puppet exec timeout does not match documentation
Title: Message Title
Nate McCurdy updated an issue
Puppet / PUP-9826
Puppet exec timeout does not match documentation
Change By:
Nate McCurdy
Affects Version/s:
PUP 5.5.14
Affects Version/s:
PUP 6.6.0
*Puppet Version: 5.5.14-1xenial*Puppet Server Version: 5.3.8-1xenial*OS Name/Version: Ubuntu 16.04 XenialDescribe your issue in as much detail as possible…When using tries in an exec resource the documentation states that the timeout parameter of the exec block applies to each try, but the code currently does not implement the functionality in that way. The timeout should apply to each try.Slack community chat snippet ``` {quote} natemccurdy [11 minutes ago]The timeout is for *the entire exec*, not for each try. (edited) Jason Grammenos [10 minutes ago]`Note that the timeout parameter applies to each try rather than to the complete set of tries.`natemccurdy [10 minutes ago]err.. sorry, You’re right.natemccurdy [10 minutes ago]Read that wrong.josh [9 minutes ago]The docs are wrong unfortunatelyJason Grammenos [9 minutes ago]oh?natemccurdy [9 minutes ago]Oh, hah :slightly_smiling_face:josh [8 minutes ago]maybe it used to apply to each try at some point?natemccurdy [8 minutes ago]Either way, try removing the `timeout` or set it to `0` and see what happens.josh [6 minutes ago]Looks like it's been broken since [ https://github.com/puppetlabs/puppet/commit/e0e6b642c4e ] josh [5 minutes ago]The begin/rescue needs to be inside `tries.times do |try|` ``` Describe steps to reproduce… {quote} *Desired Behavior:* ``` {code} exec { ' configure test ':command => " ' /bin/false ",path => [ ' /usr/bin' , '/bin'], tries => 10,try_sleep => 5,timeout = > 10, } ``` {code} This should have a per try timeout of 10 seconds as per the documentation.*Actual Behavior:*The exec time's out because the current implementation applies the timeout to the whole set of tries.current documentation: [ https://puppet.com/docs/puppet/5.3/types/exec.html#exec-attribute-tries ] Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. ``` {code} Exec try 1/10 /etc/puppetlabs/code/modules/mm/manifests/graylog/graylog.pp:83Jul 15 2019 - 14:10:34 Exec[configure-ldap](provider=posix) Executing 'curl -s -v -i --netrc-file /etc/graylog/server/configure_ldap.netrc -o /etc/graylog/server/configure_ldap.log -H "Content-Type: application/json" -H "X-Requested-By: puppet" -X PUT [ http://localhost:9000/api/system/ldap/settings ] --data @/etc/graylog/server/configure_ldap_data.json 2>&1 | grep 'HTTP/1.1 204''
Jira (PUP-9826) Puppet exec timeout does not match documentation
Title: Message Title
Jason Grammenos created an issue
Puppet / PUP-9826
Puppet exec timeout does not match documentation
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/07/15 11:29 AM
Priority:
Normal
Reporter:
Jason Grammenos
*Puppet Version: 5.5.14-1xenial *Puppet Server Version: 5.3.8-1xenial *OS Name/Version: Ubuntu 16.04 Xenial Describe your issue in as much detail as possible… When using tries in an exec resource the documentation states that the timeout parameter of the exec block applies to each try, but the code currently does not implement the functionality in that way. The timeout should apply to each try. Slack community chat snippet ``` natemccurdy [11 minutes ago] The timeout is for the entire exec, not for each try. (edited) Jason Grammenos [10 minutes ago] `Note that the timeout parameter applies to each try rather than to the complete set of tries.` natemccurdy [10 minutes ago] err.. sorry, You’re right. natemccurdy [10 minutes ago] Read that wrong. josh [9 minutes ago] The docs are wrong unfortunately Jason Grammenos [9 minutes ago] oh? natemccurdy [9 minutes ago] Oh, hah :slightly_smiling_face: josh [8 minutes ago] maybe it used to apply to each try at some point? natemccurdy [8 minutes ago] Either way, try removing the `timeout` or set it to `0` and see what happens. josh [6 minutes ago] Looks like it's been broken since https://github.com/puppetlabs/puppet/commit/e0e6b642c4e josh [5 minutes ago] The begin/rescue needs to be inside `tries.times do |try|` ``` Describe steps to reproduce… Desired Behavior: ``` exec { 'configure': command => "/bin/false", path => ['/usr/bin','/bin'], tries => 10, try_sleep => 5, timeout = 10, } ``` This should have a per try timeout of 10 seconds as per the documentation. Actual Behavior: The exec time's out because the current implementation applies the timeout to the whole set of tries. current documentation: https://puppet.com/docs/puppet/5.3/types/exec.html#exec-attribute-tries Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. ``` Exec try 1/10 /etc/puppetlabs/code/modules/mm/manifests/graylog/graylog.pp:83 Jul 15 2019 - 14:10:34
Jira (PUP-8711) Implement Agent Functions to support secret lookups at catalog application time
Title: Message Title Lindsey Smith commented on PUP-8711 Re: Implement Agent Functions to support secret lookups at catalog application time Eric Thompson should this be marked closed fixed? Looks nearly all tickets have been resolved. Also, don't know the status of the remaining ready for merge tickets 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.250291.1525994276000.16301.1563215400503%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4422) initial migration at first start fails puppetdb hangs.
Title: Message Title Austin Blatt commented on PDB-4422 Re: initial migration at first start fails puppetdb hangs. LeLutin correct, we believe the bug likely affects all their newest Postgres versions (which are 11.4, 10.9, 9.6.14, 9.5.18, 9.4.23). Importing the fix from PuppetDB should fix the problem on 11.4 as well, please let us know if it doesn't. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313863.1561448596000.16265.1563214620905%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9825) Print meaningful error message if the user/group providers are not suitable when applying the settings catalog
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9825 Print meaningful error message if the user/group providers are not suitable when applying the settings catalog Change By: Josh Cooper Priority: Blocker Normal 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316059.1562848736000.16237.1563214200820%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9825) Print meaningful error message if the user/group providers are not suitable when applying the settings catalog
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9825 Print meaningful error message if the user/group providers are not suitable when applying the settings catalog Change By: Josh Cooper 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316059.1562848736000.16232.1563214200803%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9825) Print meaningful error message if the user/group providers are not suitable when applying the settings catalog
Title: Message Title Jonny (JT) Tripathy commented on PUP-9825 Re: Print meaningful error message if the user/group providers are not suitable when applying the settings catalog Hey Josh Thanks for this information. Do you have any idea why clearing the cache and re-running will unblock the issue (and subsequently coz it to reoccur in the next next run?) Thanks JT 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316059.1562848736000.16228.1563214140141%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9825) Print meaningful error message if the user/group providers are not suitable when applying the settings catalog
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9825 Print meaningful error message if the user/group providers are not suitable when applying the settings catalog Change By: Josh Cooper Summary: Error: Could Print meaningful error message if the user/group providers are not create resources for managing Puppet's files and directories in sections suitable when applying the settings catalog 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316059.1562848736000.16223.1563214080263%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9825) Error: Could not create resources for managing Puppet's files and directories in sections
Title: Message Title Josh Cooper moved an issue Puppet / PUP-9825 Error: Could not create resources for managing Puppet's files and directories in sections Change By: Josh Cooper Key: PA PUP - 2776 9825 Project: Puppet Agent 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316059.1562848736000.16221.1563214080255%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4422) initial migration at first start fails puppetdb hangs.
Title: Message Title LeLutin commented on PDB-4422 Re: initial migration at first start fails puppetdb hangs. Hi there! for what it's worth, we've just hit exactly the same problem with puppet 6.2.0 paired with postgresql 11.4 on debian buster (using debian packages for both). Downgrading to 11.3 lets puppetdb finish its schema upgrade, so the same change that happened in the 9.6.x branch must have also happened somewhere between 11.3 and 11.4 We're going to try importing the fix for puppetdb from one of the versions mentioned above to see if it fixes the issue for the 11.x branch of postgresql, too. The debian bug report is here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932135 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313863.1561448596000.16202.1563213600550%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9792) Merge of lookup_options not working
Title: Message Title Jorie Tappa commented on PUP-9792 Re: Merge of lookup_options not working ping Henrik Lindberg does this ticket need action, or more information from Matt Dainty? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313541.1561115342000.16148.1563211800135%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9812) With "root" account, Puppet "ssh_authorized_keys" create file "authorized_keys" & change the owner & group
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9812
With "root" account, Puppet "ssh_authorized_keys" create file "authorized_keys" & change the owner & group
Change By:
Josh Cooper
``` {code:puppet} ssh_authorized_key { 'ever...@magpie.example.com': ensure => present, user => 'everetv', type => 'ssh-rsa', key => 'B3Nza[...]qXfdaQ==', target => '/opt/sysadm/etc/ssh_keys/everetv/authorized_keys', } ``` {code} By default, in this example, the resource type "ssh_authorized_key" looks for the file "authorized_keys" owned by the specific user "everetv" inside the directory "/opt/sysadm/etc/ssh_keys/everetv/". In the secure environment, this file can't be created as a specific user and end with following error. ``` {noformat} Error: /Stage[main]/Main/Ssh_authorized_key[ever...@magpie.example.com]: Could not evaluate: Permission denied @ dir_s_mkdir - /opt/sysadm/etc/ssh_keys/everetv ``` {noformat} Running agent service as root, there should be a feature to create the key file and change an owner and group as per property is given while defining the resource.This feature will be very handy to deal with the security requirement of the organization where the "non-root" account is not permitted to create the files.This case is raised in connection with customer ticket "https://puppetlabs.zendesk.com/agent/tickets/35293"
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9813) Performance of unpacking modules is extremely slow
Title: Message Title Jorie Tappa commented on PUP-9813 Re: Performance of unpacking modules is extremely slow This could introduce a regression on Solaris if implemented as-is, so the PR might need updating to account for that. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315304.156219440.16111.1563211200245%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9813) Performance of unpacking modules is extremely slow
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9813 Performance of unpacking modules is extremely slow Change By: Jorie Tappa 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315304.156219440.16087.1563210720188%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Jorie Tappa commented on PUP-9816 Re: puppet parser validate version 6.6.0 does not accept STDIN properly Regression likely caused by PUP-8984 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315541.1562618702000.16084.1563210540276%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Jorie Tappa assigned an issue to Jesse Scott Puppet / PUP-9816 puppet parser validate version 6.6.0 does not accept STDIN properly Change By: Jorie Tappa Assignee: Jesse Scott 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315541.1562618702000.16080.1563210540262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9816 puppet parser validate version 6.6.0 does not accept STDIN properly Change By: Jorie Tappa Team: Puppet Developer Experience 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315541.1562618702000.16074.1563210480163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9820) managing a File user or group or mode breaks require on Windows
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9820 managing a File user or group or mode breaks require on Windows Change By: Jorie Tappa 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316149.1562868793000.16061.1563210360394%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9820) managing a File user or group or mode breaks require on Windows
Title: Message Title Jorie Tappa commented on PUP-9820 Re: managing a File user or group or mode breaks require on Windows Validation should happen here instead: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/file/windows.rb#L42 We want to make sure we've mounted the drive before we make the check. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316149.1562868793000.16054.1563210360360%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9822) Windows package provider doesn't have reinstallable feature
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9822 Windows package provider doesn't have reinstallable feature Change By: Jorie Tappa Team: Night's Watch 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316209.1562919122000.16043.1563209940291%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-126) Support WinRM with Kerberos (from Linux node)
Title: Message Title Ethan Brown commented on BOLT-126 Re: Support WinRM with Kerberos (from Linux node) BOLT-1472 has been created to cover the testing aspect of this ticket, so that we can move forward on merging the basics of this work with manual testing only. As mentioned in https://github.com/puppetlabs/bolt/pull/1087 the caveats are: Works only with MIT Kerberos from a Linux node Does not work with Heimdal on OSX - gssapi gem support for Heimdal is not well vetted - OSX doesn't export Kerberos IOV functions needed for MS DCE RPC Does not work from a Windows node as winrm / gssapi gems only support MIT Kerberos, and Windows has its own APIs Has been manually tested in a simple AD environment that has a CentOS host domain joined to Windows Active Directory Provides initial support for the --realm command line switch, which can be used intead of --username / --password. Note that Kerberos is an authentication method, not a transport, so can be used with or without SSL just like other authentication. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this
Jira (BOLT-1472) Automated Test WinRM with Kerberos (from Linux node)
Title: Message Title Ethan Brown updated an issue Puppet Task Runner / BOLT-1472 Automated Test WinRM with Kerberos (from Linux node) Change By: Ethan Brown Sprint: Bolt Ready for Grooming 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316522.1563208774000.15956.1563208861519%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1472) Automated Test WinRM with Kerberos (from Linux node)
Title: Message Title Ethan Brown created an issue Puppet Task Runner / BOLT-1472 Automated Test WinRM with Kerberos (from Linux node) Issue Type: Task Assignee: Unassigned Components: WinRM Created: 2019/07/15 9:39 AM Labels: winrm kerberos Priority: Normal Reporter: Ethan Brown This has been spun off of the work in BOLT-126 for enabling Kerberos support. In an effort to get the code merged to support the feature, this separate ticket exists for the sake of completing the work on testing in https://github.com/puppetlabs/bolt/pull/999 At a high level, this involves doing a few things: Spinning up a new Samba container to host an Active Directory Domain joining the existing OMI container to the AD Enabling OMI server to use Kerberos authentication Configuring TravisCI to acquire a Kerberos ticket from AD, so that it can use Kerberos authentication to run PowerShell commands against OMI server New tests to demonstrate the behavior functioning properly
Jira (BOLT-1315) Collect analytics about Boltdir usage
Title: Message Title Tom Beech assigned an issue to Tom Beech Puppet Task Runner / BOLT-1315 Collect analytics about Boltdir usage Change By: Tom Beech Assignee: Tom Beech 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309059.1558038203000.15582.1563207000875%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9814) pxp-agent.conf file missing Administrators rights when puppet agent run as SYSTEM
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-9814 pxp-agent.conf file missing Administrators rights when puppet agent run as SYSTEM Change By: Gabriel Nagy Assignee: Gabriel Nagy 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315397.1562338786000.15338.1563191940583%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9824) Expand the apt provider to support virtual packages
Title: Message Title Alexandru Popa updated an issue Puppet / PUP-9824 Expand the apt provider to support virtual packages Change By: Alexandru Popa Release Notes Summary: This enables apt and dpkg providers to install virtual packages. Release Notes: New Feature 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305263.135711000.15178.1563180300266%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9824) Expand the apt provider to support virtual packages
Title: Message Title Alexandru Popa moved an issue Puppet / PUP-9824 Expand the apt provider to support virtual packages Change By: Alexandru Popa Key: PA PUP - 2635 9824 Project: Puppet Agent 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305263.135711000.15162.1563177840174%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
