Jira (PDB-5020) Document / present pe-puppetdb-extensions

2021-02-18 Thread Bogdan Irimie (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie assigned an issue to Bogdan Irimie  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-5020  
 
 
  Document / present pe-puppetdb-extensions   
 

  
 
 
 
 

 
Change By: 
 Bogdan Irimie  
 
 
Assignee: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.386971.1612971055000.146187.1613719020050%40Atlassian.JIRA.


Jira (PUP-10928) Puppet falls back to non-rich data if there is binary data in the catalog

2021-02-18 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10928  
 
 
  Puppet falls back to non-rich data if there is binary data in the catalog   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2021/02/18 9:51 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 If a catalog contains binary data, such as kerberos keytab files, then puppetserver will fallback to PSON. However, if the catalog also contains Sensitive/Binary/Deferred etc data types, then they will not work properly since rich data can't be serialized via PSON currently. We should either fail the catalog, provide more information that the conversion is lossy, or look at adding a rich_data_pson serialization format.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by 

Jira (PUP-10927) Puppet should fail parsing if the manifest(s) don't exist

2021-02-18 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10927  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet should fail parsing if the manifest(s) don't exist   
 

  
 
 
 
 

 
 Forgot I filed this already  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.388070.1613710231000.146170.1613710500023%40Atlassian.JIRA.


Jira (PUP-10927) Puppet should fail parsing if the manifest(s) don't exist

2021-02-18 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10927  
 
 
  Puppet should fail parsing if the manifest(s) don't exist   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2021/02/18 8:50 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 The compiler may produce an empty catalog if the manifests directory doesn't exist. During puppet apply manifest.pp, the apply application verifies that the manifest.pp file exists, but if a custom fact changes the current working directory, then the parser tries to parse /manifest.pp, which doesn't exist. Most surprisingly, puppet apply produces an empty catalog! See PUP-9997. It is also possible to request a catalog from the v4 endpoint with environment "" (empty string), and the compiler similarly tries to parse a non-existent /etc/puppetlabs/code/environments/manifests directory and returns an empty catalog.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
  

Jira (PUP-10924) `module install` can't unpack modules with long paths because of minitar bug

2021-02-18 Thread Josh Cooper (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10924  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: `module install` can't unpack modules with long paths because of minitar bug   
 

  
 
 
 
 

 
 Shouldn't we submit a fix to upstream minitar? It's been downloaded 25M times so seems like we shouldn't reinvent the wheel.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387906.1613638812000.146135.1613701140041%40Atlassian.JIRA.


Jira (PUP-10926) Cloudinit support for Puppet 6 onwards

2021-02-18 Thread Vijay Kumar (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vijay Kumar updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10926  
 
 
  Cloudinit support for Puppet 6 onwards   
 

  
 
 
 
 

 
Change By: 
 Vijay Kumar  
 
 
Priority: 
 High Normal  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387968.1613669787000.146128.1613697300055%40Atlassian.JIRA.


Jira (PUP-523) Make it possible to declare classes, defines and functions (and more) as private to a module

2021-02-18 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-523  
 
 
  Make it possible to declare classes, defines and functions (and more) as private to a module   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Team/s: 
 Froyo  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.16276.138092460.146036.1613692380045%40Atlassian.JIRA.


Jira (PUP-10012) Impact Analysis: Functions and Templates

2021-02-18 Thread Maggie Dreyer (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer commented on  PUP-10012  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Impact Analysis: Functions and Templates   
 

  
 
 
 
 

 
 Nick Walker do you know if this is something that is still wanted?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323829.156778568.146007.1613691900088%40Atlassian.JIRA.


Jira (PUP-10901) Puppet Platform 7.4.1 Release - 2021-02-16

2021-02-18 Thread Molly Waggett (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Molly Waggett updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10901  
 
 
  Puppet Platform 7.4.1 Release - 2021-02-16
 

  
 
 
 
 

 
Change By: 
 Molly Waggett  
 
 
Team/s: 
 Froyo  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387514.1613168188000.145948.1613690700048%40Atlassian.JIRA.


Jira (PUP-10911) Puppet Platform 6.21.1 Release - 2021-02-16

2021-02-18 Thread Molly Waggett (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Molly Waggett updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10911  
 
 
  Puppet Platform 6.21.1 Release - 2021-02-16
 

  
 
 
 
 

 
Change By: 
 Molly Waggett  
 
 
Team/s: 
 Froyo  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387536.1613168341000.145945.1613690640043%40Atlassian.JIRA.


Jira (PUP-10926) Cloudinit support for Puppet 6 onwards

2021-02-18 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10926  
 
 
  Cloudinit support for Puppet 6 onwards   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Labels: 
 community  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387968.1613669787000.145465.1613671680030%40Atlassian.JIRA.


Jira (FACT-2944) During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname

2021-02-18 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2944  
 
 
  During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Labels: 
 community  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387583.1613309929000.145374.1613669880280%40Atlassian.JIRA.


Jira (FACT-2944) During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname

2021-02-18 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2944  
 
 
  During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Component/s: 
 Puppet Server  
 
 
Key: 
 SERVER FACT - 2963 2944  
 
 
Affects Version/s: 
 SERVER 7.0.3  
 
 
Project: 
 Puppet Server Facter  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web 

Jira (PUP-10926) Cloudinit support for Puppet 6 onwards

2021-02-18 Thread Vijay Kumar (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vijay Kumar created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10926  
 
 
  Cloudinit support for Puppet 6 onwards   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Support Script  
 
 
Created: 
 2021/02/18 9:36 AM  
 
 
Priority: 
  High  
 
 
Reporter: 
 Vijay Kumar  
 

  
 
 
 
 

 
 Dear Puppet Team, Hope you are doing well. Thank you for amazing support. We love puppet. It helps us to automate our infrastructure. We need a bit of support to further automate the provisioning of the servers a bit more. Currently, we use Cloud-Init to provide initial configuration of the server such as add usernames, ssh-keys and others. Cloud-init also has Puppet Module which automatically installs puppet and set up the puppet-agent configuration which helps that the users such that they don't have to manually install the puppet and edit the /etc/hosts to provide the puppetserver IP Address. Problem: Cloud init installs the puppet version 4 which is outdated. Possible Workaround Use cloud-init write-files to create a script which download the puppet package from the Repository and install that. However, This requires creation of script which has to be OS-independent. For instance for Debian, Ubuntu download from apt.puppetlabs.com and for Centos/Redhat download from yum.puppetlabs.com. Request Would it be possible for the Puppet Team to support Puppet 6/7 via cloud-init? Probably, we need changes in the cc_puppet.py which currently installs Puppet 4. Inclusion of Puppet 6 in Cloud-init would help the provision of the servers and automatic install of puppet.  
 

  
 
 
 
 

 
 
 

Jira (PUP-10844) Agent failures with server_list when one puppetserver fails

2021-02-18 Thread Vadym Chepkov (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vadym Chepkov commented on  PUP-10844  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Agent failures with server_list when one puppetserver fails   
 

  
 
 
 
 

 
 That's not my experience, I have 6.19.1 in PE2019.8.4 and each time I have to restart primary server for patching or other maintenance, dozens of agents fail, which defeats the purpose of HA. When we had PE 2018.1.x, agents have worked without failures  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.381638.1608653215000.145249.1613667420322%40Atlassian.JIRA.


Jira (PUP-9473) Systemd daemon-reload doesn't get triggered for removal of unit file

2021-02-18 Thread Ewoud Kohl van Wijngaarden (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ewoud Kohl van Wijngaarden commented on  PUP-9473  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Systemd daemon-reload doesn't get triggered for removal of unit file   
 

  
 
 
 
 

 
 This showed up in https://github.com/puppetlabs/puppetlabs-postgresql/pull/1233 as well. From that PR, the root cause is that querying for the property failed:  
 
 
 
 
 # systemctl show --property=NeedDaemonReload -- postgresql  
 
 
 Failed to get properties: Access denied
  
 
 
 
  Perhaps the safest bet is to treat an access denied as needs reload.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Jira (PUP-10925) Default timeout not respected for Windows services

2021-02-18 Thread Mihai Buzgau (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10925  
 
 
  Default timeout not respected for Windows services   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Labels: 
 community  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387947.1613664109000.145117.1613664600320%40Atlassian.JIRA.


Jira (PUP-10925) Default timeout not respected for Windows services

2021-02-18 Thread Gabriel Nagy (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Nagy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10925  
 
 
  Default timeout not respected for Windows services   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2021/02/18 8:01 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Gabriel Nagy  
 

  
 
 
 
 

 
 Puppet Version: 6.21.1 Puppet Server Version: n/a OS Name/Version: Windows Windows services have a timeout for service-related operations that defaults to 30 seconds, as seen here: https://github.com/puppetlabs/puppet/blob/e4a654400a4c1ad3b5bc73fb558d28219a4626b2/lib/puppet/util/windows/service.rb#L24 This variable is used in the following method: https://github.com/puppetlabs/puppet/blob/c6412ea369aa1613ca166b10fb819fcf6130814b/lib/puppet/provider/service/windows.rb#L118 The method is called in the base service type: https://github.com/puppetlabs/puppet/blob/e4a654400a4c1ad3b5bc73fb558d28219a4626b2/lib/puppet/type/service.rb#L301 Desired Behavior: Not setting the timeout parameter on a Windows service should cause it to default to 30 seconds. Actual Behavior: Not setting the timeout parameter on a Windows services causes it to default to 10 seconds.   The line in the service type should change from:  
 
 
 
 
 defaultto { provider.class.respond_to?(:default_timeout) ? provider.default_timeout : 10 }
  
 
 
 
  to  
 
 
 
 
 defaultto { provider.respond_to?(:default_timeout) ? 

Jira (FACT-2943) Fix os.name detection of AlmaLinux

2021-02-18 Thread Christoph Schug (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Schug commented on  FACT-2943  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fix os.name detection of AlmaLinux   
 

  
 
 
 
 

 
 Still no luck with the CLA process. Requests to https://cla.puppet.com/ no just timeout retuern a vanilla Nginx "504 Gateway Time-out: error page.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387803.1613568551000.145000.1613649300028%40Atlassian.JIRA.


Jira (PUP-10924) `module install` can't unpack modules with long paths because of minitar bug

2021-02-18 Thread David Schmitt (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Schmitt created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10924  
 
 
  `module install` can't unpack modules with long paths because of minitar bug   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 7.3.0, PUP 6.21.1  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2021/02/18 1:00 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 David Schmitt  
 

  
 
 
 
 

 
 Puppet Version: 6.21.1 but because of minitar 0.9 origins, likely also relevant to all other recent releases. OS Name/Version: xenial Trying to install modules with puppet module install when the module contains deeply nested paths fails with a minitar error. See https://github.com/puppetlabs/puppet-modulebuilder/pull/37 for the puppet-modulebuilder code changes to trigger this; See https://travis-ci.com/github/puppetlabs/puppet-modulebuilder/jobs/484161960#L423-L430 for the test results. Desired Behavior: Puppet should be able to install all valid modules. Actual Behavior: puppet module install fails with   
 
 
 
 
 Failed to install the module using Puppet. Exit code 1: Notice: Preparing to install into /tmp/d20210218-7106-kfle20 ...  
 
 
 Error: "/1234567890" is not a valid octal string  
 
 
 Error: Try 'puppet help module install' for usage