Jira (BOLT-702) Add macOS support
Title: Message Title Michael Smith assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-702 Add macOS support 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-493) Bolt apply tasks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-493 Bolt apply tasks Change By: Alex Dreyer Summary: Bolt Apply apply tasks 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-702) Add macOS support
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-702 Add macOS support Change By: Michael Smith Assignee: Cas Donoghue 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-735) #{owner} resolves to nothing in a container on Docker for Mac
Title: Message Title
Michael Smith assigned an issue to Unassigned
Puppet Task Runner / BOLT-735
#{owner} resolves to nothing in a container on Docker for Mac
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-735) #{owner} resolves to nothing in a container on Docker for Mac
Title: Message Title
Michael Smith assigned an issue to Michael Smith
Puppet Task Runner / BOLT-735
#{owner} resolves to nothing in a container on Docker for Mac
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-741) Add Jenkins testing for macOS and Windows
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-741 Add Jenkins testing for macOS and Windows Issue Type: Sub-task Assignee: Unassigned Created: 2018/08/03 1:24 PM Priority: Normal Reporter: Michael Smith Add a step in the puppet_agent test suite that runs the task_spec acceptance tests on Windows (32 and 64-bit) and macOS. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-740) Bug? Bolt tasks seems to require /opt/puppetlabs/puppet/bin/ruby on target machines
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-740 Bug? Bolt tasks seems to require /opt/puppetlabs/puppet/bin/ruby on target machines Change By: Alex Dreyer Issue Type: Bug 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-740) Bug? Bolt tasks seems to require /opt/puppetlabs/puppet/bin/ruby on target machines
Title: Message Title Eric Griswold created an issue Puppet Task Runner / BOLT-740 Bug? Bolt tasks seems to require /opt/puppetlabs/puppet/bin/ruby on target machines Issue Type: Bug Affects Versions: BOLT 0.21.5 Assignee: Unassigned Components: Tasks Created: 2018/08/03 1:12 PM Priority: Normal Reporter: Eric Griswold I used vmpooler to create a CentOS 7 machine. On my dev box, I type: $ bolt task run package action="" name=sudo --nodes ay6lmvra38ku0lb I get back: Failed on ay6lmvra38ku0lb: The task failed with exit code 126: bash: /tmp/7584a478-1c5e-4b28-8c25-3e6b0038701b/init.rb: /opt/puppetlabs/puppet/bin/ruby: bad interpreter: No such file or directory
Jira (BOLT-739) Write rspec matchers for Result and ResultSet objects
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-739 Write rspec matchers for Result and ResultSet objects Issue Type: New Feature Assignee: Unassigned Created: 2018/08/03 1:09 PM Priority: Normal Reporter: Alex Dreyer In order to avoid task boilerplate bolt_spec should have rspec matchers for: successful resultsets error kinds error message matches Add Comment This message was
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title
Erik Hansen updated an issue
Puppet / PUP-9041
AIX nim provider can't be used on a NIM master
Change By:
Erik Hansen
Environment:
Platform: AIX 7.2
When using a package resource and the nim provider, the resource cannot be applied to a NIM master. The error received is:{noformat}Error: Failed to apply catalog: Execution of '/usr/sbin/nimclient -o showres -a installp_flags=L -a resource=lpp_resource' returned 147: 0042-147 nimclient: this command may not be executed on a NIM master.{noformat}This can be reproduced with a simple resource such as:{code:java}package { $install_pkgs: ensure => latest, provider => nim,}{code}On a NIM master you cannot use the nimclient command, the command would have to be:{noformat}/usr/sbin/nim -o showres -a installp_flags=L lpp_resource{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title
Erik Hansen created an issue
Puppet / PUP-9041
AIX nim provider can't be used on a NIM master
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/08/03 12:35 PM
Priority:
Normal
Reporter:
Erik Hansen
When using a package resource and the nim provider, the resource cannot be applied to a NIM master. The error received is:
Error: Failed to apply catalog: Execution of '/usr/sbin/nimclient -o showres -a installp_flags=L -a resource=lpp_resource' returned 147: 0042-147 nimclient: this command may not be executed on a NIM master.
This can be reproduced with a simple resource such as:
package { $install_pkgs:
ensure => latest,
provider => nim,
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Erik Hansen updated an issue Puppet / PUP-9041 AIX nim provider can't be used on a NIM master Change By: Erik Hansen Issue Type: Bug Improvement 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 (PDB-3996) Test merge 5.2.x
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3996 Test merge 5.2.x Issue Type: Bug Assignee: Unassigned Created: 2018/08/03 12:24 PM Priority: Normal Reporter: gepetto-bot 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.
Jira (PUP-9040) puppet lookup command returns warning with poor formatting
Title: Message Title Paul Schaffer created an issue Puppet / PUP-9040 puppet lookup command returns warning with poor formatting Issue Type: Task Affects Versions: PUP 5.5.2 Assignee: Unassigned Created: 2018/08/03 12:15 PM Labels: maintenance triage Priority: Normal Reporter: Paul Schaffer When performing a hiera lookup against a hierarchy that includes an undefined variable, the warning message that Puppet returns includes a new line marker: [root@pe-201812-master ~]# puppet lookup "foo" Warning: Undefined variable 'bar'; \n (file & line not available) Otherwise the lookup appears to perform as intended: [root@pe-201812-master ~]# puppet lookup
Jira (BOLT-738) Hide implementations of tasks by default
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-738 Hide implementations of tasks by default Issue Type: Improvement Assignee: Unassigned Created: 2018/08/03 11:29 AM Priority: Normal Reporter: Michael Smith Right now bolt task show includes a lot of extraneous content you don't need, such as facts Gather system facts facts::bashGather system facts using bash facts::powershell Gather system facts using powershell facts::rubyGather system facts using ruby and facter The only one that most people should use there is facts. We should hide tasks that are included in implementations of another task by default (option to show all) to show a more constrained view.
Jira (PUP-7648) Fix ci:test:git pre-suite on OSX 10.11
Title: Message Title Melissa Stone commented on PUP-7648 Re: Fix ci:test:git pre-suite on OSX 10.11 This will be fixed as a part of PUP-8305 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-9039) Resource collector support in apply() statement
Title: Message Title Nick Lewis updated an issue Puppet / PUP-9039 Resource collector support in apply() statement Change By: Nick Lewis Team: 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 options, visit https://groups.google.com/d/optout.
Jira (PUP-9039) Resource collector support in apply() statement
Title: Message Title Nick Lewis moved an issue Puppet / PUP-9039 Resource collector support in apply() statement Change By: Nick Lewis Issue Type: New Feature Improvement Key: BOLT PUP - 659 9039 Project: Puppet Task Runner 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-659) Resource collector support in apply() statement
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-659 Resource collector support in apply() statement Change By: Nick Lewis The behavior of virtual/ exported resources and collectors is not straightforward in manifest apply() blocks. Should export/collect Virtual resources and collectors should be allowed and should work for as normal, because they're only meaningful within the life context of a plan? Should it single catalog application.Exported resources and collectors should not be backed by puppetdb? We allowed. Collectors should disable these features in manifest blocks and make sure they fail cleanly explicitly, and exported resources should just be ignored for compatibility with existing code . 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
Jira (BOLT-659) Resource collector support in apply() statement
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-659 Resource collector support in apply() statement Change By: Nick Lewis Acceptance Criteria: # 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-659) Resource collector support in apply() statement
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-659 Resource collector support in apply() statement Change By: Nick Lewis Summary: Resource collector support in bolt apply() statement 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-8763) Remove puppet module build functionality
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8763 Remove puppet module build functionality Change By: Josh Cooper 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 (PUP-8763) Remove puppet module build functionality
Title: Message Title Josh Cooper commented on PUP-8763 Re: Remove puppet module build functionality Merged to puppet#master in https://github.com/puppetlabs/puppet/commit/4fc612518099762ee85c2bd2545f4c81b6fa51a6. Passed CI awhile ago, resolving. 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-7582) Make attempt to export or virtualize a class an error
Title: Message Title Josh Cooper commented on PUP-7582 Re: Make attempt to export or virtualize a class an error ping Henrik Lindberg, Thomas Hallgren 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-8320) True/truthy inconsistencies between function filter() and functions all() and any()
Title: Message Title Josh Cooper commented on PUP-8320 Re: True/truthy inconsistencies between function filter() and functions all() and any() Henrik Lindberg, Thomas Hallgren what is the status of 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8987) add resource_api gem to puppet gemspec
Title: Message Title Josh Cooper commented on PUP-8987 Re: add resource_api gem to puppet gemspec What are the implications for puppetserver? Does resource_api depend on gems with native extensions? /cc Maggie Dreyer, Branan Riley 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-8597) Modify rich data serialization to use shorter tags instead of __pcore_type__
Title: Message Title Josh Cooper commented on PUP-8597 Re: Modify rich data serialization to use shorter tags instead of __pcore_type__ Davin Hanlon, Rick Sherman will this change break YANG modules? Do you know if there is a specification for pcore format? 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-8716) Remove puppet module generate functionality
Title: Message Title Josh Cooper commented on PUP-8716 Re: Remove puppet module generate functionality This passed CI awhile ago, resolving. 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-8694) Comparison of Numeric to Timestamp/Timespan fails, but other way is ok
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8694 Comparison of Numeric to Timestamp/Timespan fails, but other way is ok Change By: Josh Cooper 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 (PUP-8976) A hash containing the key __ptype cannot be serialized using the human readable JSON format
Title: Message Title Josh Cooper commented on PUP-8976 Re: A hash containing the key __ptype cannot be serialized using the human readable JSON format Merged to puppet#master in https://github.com/puppetlabs/puppet/commit/0b4b32c666cce76bc2c696c97dfffede15541e28 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-8976) A hash containing the key __ptype cannot be serialized using the human readable JSON format
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8976 A hash containing the key __ptype cannot be serialized using the human readable JSON format Change By: Josh Cooper 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 (PUP-8694) Comparison of Numeric to Timestamp/Timespan fails, but other way is ok
Title: Message Title Josh Cooper commented on PUP-8694 Re: Comparison of Numeric to Timestamp/Timespan fails, but other way is ok This passed CI awhile ago, resolving 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-8976) A hash containing the key __ptype cannot be serialized using the human readable JSON format
Title: Message Title Josh Cooper commented on PUP-8976 Re: A hash containing the key __ptype cannot be serialized using the human readable JSON format This passed CI awhile ago, resolving 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-8761) Make convert_to() function accept additional arguments
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8761 Make convert_to() function accept additional arguments Change By: Josh Cooper 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 (PUP-8761) Make convert_to() function accept additional arguments
Title: Message Title Josh Cooper commented on PUP-8761 Re: Make convert_to() function accept additional arguments This passed CI awhile ago, resolving 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-8761) Make convert_to() function accept additional arguments
Title: Message Title Josh Cooper commented on PUP-8761 Re: Make convert_to() function accept additional arguments Merged to puppet#master in https://github.com/puppetlabs/puppet/commit/aa5a7d4fd2262325217da075072c0386052c200a 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-8693) Add a compare() function
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8693 Add a compare() function Change By: Josh Cooper 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 (PUP-8693) Add a compare() function
Title: Message Title Josh Cooper commented on PUP-8693 Re: Add a compare() function This passed CI awhile ago, resolving. 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-8693) Add a compare() function
Title: Message Title Josh Cooper commented on PUP-8693 Re: Add a compare() function Helen Campbell, Thomas Honey could you verify that stdlib contains the deprecation warnings Henrik Lindberg mentioned? 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-8693) Add a compare() function
Title: Message Title Josh Cooper commented on PUP-8693 Re: Add a compare() function Merged to puppet#master in https://github.com/puppetlabs/puppet/commit/274a1e0c35b40a1e3377db3cee0f4ccc78b55a17 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-8480) Puppet::Util::Execution.execute should always default failonfail to true, even if other options are set
Title: Message Title Josh Cooper commented on PUP-8480 Re: Puppet::Util::Execution.execute should always default failonfail to true, even if other options are set For this ticket, I think we want to create a new API with sane semantics. There's no telling how many modules/providers we'd break changing the current API. 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-6645) Remove the hiera_xxx functions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6645 Remove the hiera_xxx functions Change By: Josh Cooper Fix Version/s: PUP 6.0.0 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8605) Move sort function from stdlib to puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8605 Move sort function from stdlib to puppet Change By: Josh Cooper 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 (PUP-8604) Move String functions upcase, downcase, capitalize, camelcase, lstrip, rstrip, strip, chop, chomp from stdlib to puppet
Title: Message Title Josh Cooper commented on PUP-8604 Re: Move String functions upcase, downcase, capitalize, camelcase, lstrip, rstrip, strip, chop, chomp from stdlib to puppet Helen Campbell, Thomas Honey could you verify that stdlib contains the deprecation warnings Henrik Lindberg mentioned? 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-8605) Move sort function from stdlib to puppet
Title: Message Title Josh Cooper commented on PUP-8605 Re: Move sort function from stdlib to puppet Helen Campbell, Thomas Honey could you verify that stdlib contains the deprecation warnings Henrik Lindberg mentioned? 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-8604) Move String functions upcase, downcase, capitalize, camelcase, lstrip, rstrip, strip, chop, chomp from stdlib to puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8604 Move String functions upcase, downcase, capitalize, camelcase, lstrip, rstrip, strip, chop, chomp from stdlib to puppet Change By: Josh Cooper 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 (PUP-8604) Move String functions upcase, downcase, capitalize, camelcase, lstrip, rstrip, strip, chop, chomp from stdlib to puppet
Title: Message Title Josh Cooper commented on PUP-8604 Re: Move String functions upcase, downcase, capitalize, camelcase, lstrip, rstrip, strip, chop, chomp from stdlib to puppet This passed CI awhile ago, resolving. 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-8603) Move math functions abs, ceil, floor, round, min, max from stdlib to puppet
Title: Message Title Josh Cooper commented on PUP-8603 Re: Move math functions abs, ceil, floor, round, min, max from stdlib to puppet Helen Campbell, Thomas Honey could you verify that stdlib contains the deprecation warnings Henrik Lindberg mentioned? 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-8605) Move sort function from stdlib to puppet
Title: Message Title Josh Cooper commented on PUP-8605 Re: Move sort function from stdlib to puppet This passed CI awhile ago, resolving. 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-8603) Move math functions abs, ceil, floor, round, min, max from stdlib to puppet
Title: Message Title Josh Cooper commented on PUP-8603 Re: Move math functions abs, ceil, floor, round, min, max from stdlib to puppet This passed CI awhile ago, resolving. 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-8603) Move math functions abs, ceil, floor, round, min, max from stdlib to puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8603 Move math functions abs, ceil, floor, round, min, max from stdlib to puppet Change By: Josh Cooper 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-737) Bolt documentation dissonance with acronyms and audience assumptions
Title: Message Title Michael Smith commented on BOLT-737 Re: Bolt documentation dissonance with acronyms and audience assumptions There's a navigation reorg in the works. I can imagine making the Orchestrator page a little better at introducing the concept though. Config and setting up Orchestrator are definitely not where we should start. 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-737) Bolt documentation dissonance with acronyms and audience assumptions
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-737 Bolt documentation dissonance with acronyms and audience assumptions 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 (BOLT-737) Bolt documentation dissonance with acronyms and audience assumptions
Title: Message Title Eric Griswold created an issue Puppet Task Runner / BOLT-737 Bolt documentation dissonance with acronyms and audience assumptions Issue Type: Bug Affects Versions: BOLT 0.21.5 Assignee: Unassigned Components: DOCS Created: 2018/08/03 10:23 AM Priority: Normal Reporter: Eric Griswold I started reading Bolt documentation, with the intention of being a novice to any Puppet product. This conceit based upon the idea that Bolt is our introduction to the Puppet world. After installation, I started reading this page: https://puppet.com/docs/bolt/0.x/bolt_configuration_options.html The next page I ran into (using navigation in the left pane), was: https://puppet.com/docs/bolt/0.x/bolt_configure_orchestrator.html Some thoughts, following my conceit: I don't know what "orchestrator" is. There is no reference on how to find an explanation. I don't know what "PE" is. IMO, acronyms in documentation should be avoided or at least expanded the first time on each page, that they are used. It references "Bolt plans" before I have been told what a "Bolt plan" is. I don't know what "RBAC" is. Much of the rest of the page suggest that one is already a seasoned PE admin. This is probably not a good assumption this early in the Bolt documentation.
Jira (BOLT-618) Automate updating homebrew-puppet with Bolt releases
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-618 Automate updating homebrew-puppet with Bolt releases 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-735) #{owner} resolves to nothing in a container on Docker for Mac
Title: Message Title
Michael Smith commented on BOLT-735
Re: #{owner} resolves to nothing in a container on Docker for Mac
Suggested alternative is Etc.getpwuid.name. This is used in apply workflows when untar-ing on a target: https://github.com/puppetlabs/bolt/blob/0.21.5/libexec/apply_catalog.rb#L49 and https://github.com/puppetlabs/bolt/blob/0.21.5/libexec/custom_facts.rb#L14.
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-735) #{owner} resolves to nothing in a container on Docker for Mac
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-735
#{owner} resolves to nothing in a container on Docker for Mac
Change By:
David Kramer
Sprint:
Bolt 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 (BOLT-659) Resource collector support in bolt
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-659 Resource collector support in bolt Change By: Alex Dreyer Summary: Exported resources should fail cleanly Resource collector support in 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 options, visit https://groups.google.com/d/optout.
Jira (PUP-9004) Spike hiera 3 removal
Title: Message Title Nick Walker commented on PUP-9004 Re: Spike hiera 3 removal Josh Cooper should we be considering this for Puppet 7? Is there anything we'd want to do to further highlight the deprecation of hiera 3 and get users onto hiera 5? 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-736) Give 'bolt puppetfile install' an option to not delete existing modules
Title: Message Title
Kevin Reeuwijk updated an issue
Puppet Task Runner / BOLT-736
Give 'bolt puppetfile install' an option to not delete existing modules
Change By:
Kevin Reeuwijk
I'd like to be able to bundle my Bolt Task Plan with my application repo in a straightforward way. I've done this here for my Pipelines for Applications demo: [https://github.com/puppetlabs-seteam/PFA_NodeJS_SampleApp/tree/kevin]The Boltdir contains a Puppetfile for supporting modules and a custom 'sampleapp' module which contains my Bolt Task Plan to install all the prereqs for the application.Now ideally, my script would have just these 2 commands:{code}bolt puppetfile installbolt plan run sampleapp::prereqs{code}However if I run *bolt puppetfile install*, it will delete the sampleapp module and only install the modules in the Puppetfile.Since there is no way to use a Boltdir with supporting modules together with different modulepath that contains the module with my plan(s), I would need to make things more complicated then than desired: * publish the sampleapp module somewhere in a separate repo and put in the Puppetfile * checkout the code, run *bolt puppetfile install*, manually add the sampleapp module back in and push the code back to git.Right now I did the second option to get it working. The first option is the neatest, but I feel a simpler option should be available: {code}bolt puppetfile install --no-purge{code}This option would install the modules in the Puppetfile but not delete existing modules in the Boltdir.
Add Comment
Jira (BOLT-736) Give 'bolt puppetfile install' an option to not delete existing modules
Title: Message Title Kevin Reeuwijk created an issue Puppet Task Runner / BOLT-736 Give 'bolt puppetfile install' an option to not delete existing modules Issue Type: Improvement Assignee: Unassigned Created: 2018/08/03 7:43 AM Priority: Normal Reporter: Kevin Reeuwijk I'd like to be able to bundle my Bolt Task Plan with my application repo in a straightforward way. I've done this here for my Pipelines for Applications demo: https://github.com/puppetlabs-seteam/PFA_NodeJS_SampleApp/tree/kevin The Boltdir contains a Puppetfile for supporting modules and a custom 'sampleapp' module which contains my Bolt Task Plan to install all the prereqs for the application. Now ideally, my script would have just these 2 commands: bolt puppetfile install bolt plan run sampleapp::prereqs However if I run bolt puppetfile install, it will delete the sampleapp module and only install the modules in the Puppetfile. Since there is no way to use a Boltdir with supporting modules together with different modulepath that contains the module with my plan(s), I would need to make things more complicated then desired: publish the sampleapp module somewhere in a separate repo and put in the Puppetfile checkout the code, run bolt
Jira (BOLT-735) #{owner} resolves to nothing in a container on Docker for Mac
Title: Message Title
Kevin Reeuwijk created an issue
Puppet Task Runner / BOLT-735
#{owner} resolves to nothing in a container on Docker for Mac
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/08/03 7:23 AM
Environment:
Docker for Mac 8.06.0-ce-mac70 (26399) centos:latest container
Priority:
Normal
Reporter:
Kevin Reeuwijk
When using the apply_prep() function in a Task Plan in Bolt 0.21.5, I get the following error when I run it in a centos:latest container under Docker for Mac 18.06.0-ce-mac70 (26399):
Starting: install puppet and gather facts on localhost
{
"kind": "bolt/run-failure",
"msg": "Plan aborted: run_task 'custom_facts' failed on 1 nodes",
"details": {
Jira (PUP-9038) Ability to pass variables into puppet lookup
Title: Message Title Nick Maludy created an issue Puppet / PUP-9038 Ability to pass variables into puppet lookup Issue Type: New Feature Affects Versions: PUP 5.5.3 Assignee: Thomas Hallgren Components: Hiera & Lookup Created: 2018/08/03 6:05 AM Priority: Normal Reporter: Nick Maludy In the old `hiera` CLI you could pass in variables like so: hiera my_key var1=xxx With `puppet lookup` this is only possible by supplying a facts file. puppet lookup --facts facts.yaml my_key It would be great if the new CLI could support passing variables like the old Hiera 3 CLI did!
Jira (PUP-3204) Find LDAP users and groups created mid-transaction.
Title: Message Title Russell Knighton commented on PUP-3204 Re: Find LDAP users and groups created mid-transaction. It's a long shot, but perhaps PuppetLabs could use a bit of their commercial power/popularity and get the above RedHat ticket reopened, or create a replacement one that petitions for this to be properly fixed at the glibc level? That original bug report was closed with the answer: That file will never be automatically reloaded. The file is not supposed to be changed after the initial configuration and if it does, better reboot and restart all relevant programs. I will not add any code which penalizes normal operations. All this can in general be avoided by using nscd. If nscd is used only this one program needs to be restarted for the new setting to be used. If you need to use change the nsswitch.conf setting for services other than passwd, group, and hosts then this is something else. The solution then might be to add support for these other services to nscd. So in summary, us nscd and never let programs directly use NSS services. which may have been true/applicable/satisfactory 14 years ago in 2004, but it's now 2018. Tools of the like of puppet were barely conceived back then. Hardware is an order of magnitude more powerful now, so what sort of penalty would normal operations really under go now-a-days? As for the suggested NSCd, well, it has been pretty much entirely replaced by SSSd, but neither of these solve that the ticket was originally for. Clearly, this isn't something that just affects puppet, so for the benefit of all OSes that use glibc, it would surely be better that this is fixed properly, once and for all. I appreciate that, even if this was ever implemented by the overlords of glibc, it would take a long time to make it into released distros, but at least we'd be on the right path to a real fix, even if it means we'd still need and be relying on a hacky workaround in the meantime. Add Comment
