Jira (PUP-7983) Test puppet-agent built against system openssl in PA CI pipes
Title: Message Title Jayant Sane commented on PUP-7983 Re: Test puppet-agent built against system openssl in PA CI pipes After some investigation, and after wrong leads, it was narrowed to redhat platforms. Any binary linked to system openssl on redhat systems caused failures on things like SSL_CTX_set_ecdh_auto. Some additional experimentation, using a test C application using the same API functions, indicates the problem to be peculiar to puppet binaries. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7511) Test puppet-agent against FIPS-compliant system openssl library
Title: Message Title Trevor Vaughan commented on PUP-7511 Re: Test puppet-agent against FIPS-compliant system openssl library Jayant Sane RHEL and CentOS 6 and 7. I really need to be able to change the hash algorithms from the central config file. Different customers have had different requirements for their algorithms and it's something that's supported by the underlying code, just not exposed as a configuration option. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3114) Puppet needs to use default keylength 2048 on FIPS enabled systems
Title: Message Title Trevor Vaughan commented on PUP-3114 Re: Puppet needs to use default keylength 2048 on FIPS enabled systems Jayant Sane That's good news! I just double checked on one of my systems and the updates to openssl do indeed seem to support 4096 bit keys. However, this will not be compatible with all versions of EL6 and EL7 since I know for a fact that they used to die on 4096 bit keys. Ideally, you would try for 4096 and then either step it down to something that works or just provide a helpful error message. Personally, I would step it down if possible. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7848) Capitals in variable names in EPP templates hang threads forever
Title: Message Title Kenn Hussey commented on PUP-7848 Re: Capitals in variable names in EPP templates hang threads forever Garrett Guillotte the fix was merged to the 5.3.x branch so yes, it will be going out with 5.3.0. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7971) Transient failures on Cisco NX
Title: Message Title Erik Dasher commented on PUP-7971 Re: Transient failures on Cisco NX There are some closely related tickets here; Let us use this one for the long term issues that Rick Sherman mentions above. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7971) Transient failures on Cisco NX
Title: Message Title Erik Dasher updated an issue Puppet / PUP-7971 Transient failures on Cisco NX Change By: Erik Dasher Summary: Transient failure to install cisco agent failures on Cisco NX Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3114) Puppet needs to use default keylength 2048 on FIPS enabled systems
Title: Message Title Jayant Sane commented on PUP-3114 Re: Puppet needs to use default keylength 2048 on FIPS enabled systems I seem to be able to generate & use 4k key/cert fine on Centos 6 in fips mode. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3677) Prepare PupppetDB 4.2.3.x release for PE(2016.4.z LTS release (Oct 24, 2017)
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3677 Prepare PupppetDB 4.2.3.x release for PE(2016.4.z LTS release (Oct 24, 2017) Change By: Jeff Yarnell Summary: Prepare PupppetDB 4.2.3.x release for PE (2016.4 ) .z LTS release (Oct 24, 2017) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3678) Prepare PupppetDB release for PE Hoyt 2017.3.1 (Oct 25, 2017)
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3678 Prepare PupppetDB release for PE Hoyt 2017.3.1 (Oct 25, 2017) Change By: Jeff Yarnell Summary: Prepare PupppetDB release for PE Hoyt ( 2017.3 ) Z release .1 (Oct 25, 2017) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3686) PDB migration error due to facts deduplication and null values
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3686 PDB migration error due to facts deduplication and null values Change By: Jeff Yarnell Sprint: Hopper Data Platform 2017-10-04 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3686) PDB migration error due to facts deduplication and null values
Title: Message Title Jeff Yarnell assigned an issue to Russell Mull PuppetDB / PDB-3686 PDB migration error due to facts deduplication and null values Change By: Jeff Yarnell Assignee: Jeff Yarnell Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3686) PDB migration error due to facts deduplication and null values
Title: Message Title Alexander Johnson commented on PDB-3686 Re: PDB migration error due to facts deduplication and null values Just chatted with Russ and Jeff. Russ is going to work on this asap, and the good news is that they can promote directly into PE (i.e. we don't need a platform release). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7971) Transient failure to install cisco agent
Title: Message Title Erik Dasher updated an issue Puppet / PUP-7971 Transient failure to install cisco agent Change By: Erik Dasher Issue Type: Bug CI Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7511) Test puppet-agent against FIPS-compliant system openssl library
Title: Message Title Jayant Sane commented on PUP-7511 Re: Test puppet-agent against FIPS-compliant system openssl library Trevor Vaughan Q: Which platform & version specifically did you test the system openssl linked agent on? Like centos, redhat, ?? thx Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3686) PDB migration error due to facts deduplication and null values
Title: Message Title Rajasree Talla commented on PDB-3686 Re: PDB migration error due to facts deduplication and null values Jeff Yarnell - This is a release blocker for PE Hoyt. Who is going to pick this up? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3686) PDB migration error due to facts deduplication and null values
Title: Message Title Rajasree Talla assigned an issue to Jeff Yarnell PuppetDB / PDB-3686 PDB migration error due to facts deduplication and null values Change By: Rajasree Talla Assignee: Jeff Yarnell Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3686) PDB migration error due to facts deduplication and null values
Title: Message Title Rajasree Talla updated an issue PuppetDB / PDB-3686 PDB migration error due to facts deduplication and null values Change By: Rajasree Talla Fix Version/s: PE Hoyt Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3686) PDB migration error due to facts deduplication and null values
Title: Message Title Rajasree Talla updated an issue PuppetDB / PDB-3686 PDB migration error due to facts deduplication and null values Change By: Rajasree Talla Labels: hoyt-ss Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7991) Investigate puppet server CRL handling for atomicity
Title: Message Title Nick Walker commented on PUP-7991 Re: Investigate puppet server CRL handling for atomicity I think this is just SERVER-115 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-2189) The CRL can get corrupted if two workers revoke certs at same time
Title: Message Title Moses Mendoza commented on PUP-2189 Re: The CRL can get corrupted if two workers revoke certs at same time Nick Walker just trying to make the tickets more granular - filed PUP-7991 for server-side effort Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7991) Investigate puppet server CRL handling for atomicity
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7991 Investigate puppet server CRL handling for atomicity Issue Type: Task Assignee: Unassigned Created: 2017/09/25 3:00 PM Priority: Normal Reporter: Moses Mendoza In Scope Review CRL handling in puppet server. Is it possible to clobber the CRL or corrupt with simultaneous writes? If so, investigate fixes. If easy, do them. Add Comment
Jira (PUP-2189) The CRL can get corrupted if two workers revoke certs at same time
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-2189 The CRL can get corrupted if two workers revoke certs at same time Change By: Moses Mendoza The CRL file (and many other SSL related files) are missing locking, so concurrent access can lead to corruptions.*In Scope** Confirm that PE in the Cloud etc will be leveraging puppet cert command line tools (as opposed to modifying CRL directly or revoking certs via server http api)* If so,** Investigate filesystem-based locking of CRL file in ruby puppet on update** Limited to updates to CRL via the puppet cert CLI*Out of Scope** Changes to puppet server CRL handling / API - PUP-7991 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7848) Capitals in variable names in EPP templates hang threads forever
Title: Message Title Garrett Guillotte commented on PUP-7848 Re: Capitals in variable names in EPP templates hang threads forever Will this land in 5.3.0? I'm compiling release notes for that release. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-2189) The CRL can get corrupted if two workers revoke certs at same time
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-2189 The CRL can get corrupted if two workers revoke certs at same time Change By: Moses Mendoza The CRL file (and many other SSL related files) are missing locking, so concurrent access can lead to corruptions. *In Scope** Confirm that PE in the Cloud etc will be leveraging puppet cert command line tools (as opposed to modifying CRL directly or revoking certs via server http api)* If so,** Investigate filesystem-based locking of CRL file in ruby puppet on update** Limited to updates to CRL via the puppet cert CLI*Out of Scope** Changes to puppet server CRL handling / API Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-2189) The CRL can get corrupted if two workers revoke certs at same time
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-2189 The CRL can get corrupted if two workers revoke certs at same time Change By: Moses Mendoza Acceptance Criteria: Testbed is success in PE in the Cloud etc. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7933) Remove documentation about 'last' in scheduledtasks type
Title: Message Title Garrett Guillotte updated an issue Puppet / PUP-7933 Remove documentation about 'last' in scheduledtasks type Change By: Garrett Guillotte Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7677) Create a feature flag setting for puppet 6 features during puppet 5 lifetime
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7677 Create a feature flag setting for puppet 6 features during puppet 5 lifetime Change By: Craig Gomes Sprint: Platform Core Grooming Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7951) agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7951 agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths Change By: Moses Mendoza Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7951) agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7951 agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths Change By: Moses Mendoza Fix Version/s: PUP 5.3.1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7951) agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7951 agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths Change By: Moses Mendoza Fix Version/s: PUP 4.10.9 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7951) agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths
Title: Message Title Moses Mendoza commented on PUP-7951 Re: agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths I've reproduced this issue given the original scenario. I can confirm it appears that rather than being in binary, the content of the bucket_file, a Puppet::FileBucket::File instance, is encoded in UTF-8: code [21] pry(#)> bucket_file.to_binary.encoding bucket_file.to_binary.encoding => # code Since this is an instance over the wire, we're dealing with a StringContents implementation, and #to_binary just returns the content of the object. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7951) agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7951 agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths Change By: Moses Mendoza Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7971) Transient failure to install cisco agent
Title: Message Title Rick Sherman commented on PUP-7971 Re: Transient failure to install cisco agent I believe we have to tracks we need to follow here. 1) Are these transients a known issue with the Cisco image? We can confer with them, and also update to the latest version of the VM 2) Can we make our tooling more robust when it comes to dealing with transients? Are there opportunities for us to retry commands, etc. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7926) vendored pathspec library has an over-reaching regexp
Title: Message Title Glenn Sarti commented on PUP-7926 Re: vendored pathspec library has an over-reaching regexp Yes. It wouldn't been picked up in https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/5.3.x/view/Components/job/platform_puppet_init-van-component-simple_5.3.x/14/ which was green Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7971) Transient failure to install cisco agent
Title: Message Title Erik Dasher updated an issue Puppet / PUP-7971 Transient failure to install cisco agent Change By: Erik Dasher Attachment: rutroh.jpg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7842) language for SLES 11.3 service not being set correctly during boot
Title: Message Title Scott McClellan commented on PUP-7842 Re: language for SLES 11.3 service not being set correctly during boot After looking into this a bit, I found that there were some differences between SLES 11 and SLES 12. One being whether the service is enabled on startup. I was able to reproduce on SLES 11, however. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7842) language for SLES 11.3 service not being set correctly during boot
Title: Message Title Scott McClellan assigned an issue to Unassigned Puppet / PUP-7842 language for SLES 11.3 service not being set correctly during boot Change By: Scott McClellan Assignee: Scott McClellan Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7926) vendored pathspec library has an over-reaching regexp
Title: Message Title Kenn Hussey commented on PUP-7926 Re: vendored pathspec library has an over-reaching regexp Glenn Sarti this must have made it through CI by now, right? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1759) facter should compute the correct logical and physical cpu count on Power for the processors.count and processors.physicalcount facts
Title: Message Title Enis Inan commented on FACT-1759 Re: facter should compute the correct logical and physical cpu count on Power for the processors.count and processors.physicalcount facts Just discussed this with Branan Riley. We agreed on the following approach for Power architectures: (1) The /sys/devices/system/cpu will only compute the physical count by checking for non-negative physical id entries. (2) The logical count will be computed by examining /proc/cpuinfo and incrementing the # of "processor" entries encountered. Note there is a possibility that (1) will fail to compute the physical count. If this happens, then we cannot compute the physical count by reading /proc/cpuinfo (as we could for x86 families) because there is no "physical id" entry in this file for Power machines. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7985) `puppet cert generate` uses the wrong CA certificate
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7985 `puppet cert generate` uses the wrong CA certificate Change By: Adrien Thebo When `puppet cert generate` is invoked, it configures itself as a ["local" CA|https://github.com/puppetlabs/puppet/blob/5.2.0/lib/puppet/application/cert.rb#L288-L292]. This [configures the indirector|https://github.com/puppetlabs/puppet/blob/5.2.0/lib/puppet/ssl/host.rb#L93-L95] for SSL files to use the CA locations, but cache files in the agent location. The intent of this is unclear but it looks like this is done in order to [ cache generated files |https://projects.puppetlabs.com/issues/3961] in a location that the Puppet agent will read.This becomes a problem if the contents of `cacert` does not match the contents of `localcacert`. In an environment where intermediate CA certificates are in use, `cacert` needs to contain the intermediate CA certificate (since it contains information used during signing certificates) while `localcacert` needs to contain the root certificate (because the Puppet agent needs the root certificate in order to validate the server SSL certificate chain).If this case occurs, when Puppet configures itself to use the CA file terminii but uses the normal SSL file terminii as a cache. Because the cached files are consulted first Puppet will ignore the `cacert` location and read the `localcacert` file. Because Puppet is reading the `cakey` file for signing certificates but the `localcacert` for certificate information, [validating the key against the certificate will fail|https://github.com/puppetlabs/puppet/blob/5.2.0/lib/puppet/ssl/host.rb#L209].To add to the fun, when this circumstance appears Puppet is hardcoded to indicate that the [agent private key and certificate don't match|https://github.com/puppetlabs/puppet/blob/5.2.0/lib/puppet/ssl/host.rb#L213], and debugging this is effectively impossible without injecting pry invocations through the source code. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-7916) An Object Data Type with an unresolved parent causes an undefined method error
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7916 An Object Data Type with an unresolved parent causes an undefined method error Change By: Moses Mendoza Sprint: Platform Core Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7916) An Object Data Type with an unresolved parent causes an undefined method error
Title: Message Title Moses Mendoza commented on PUP-7916 Re: An Object Data Type with an unresolved parent causes an undefined method error this has been tagged as part of 5.3.0 so i'm assuming it has passed ci Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-5757) Replace win32-service calls with internal API implementations that are wide-string compatibles
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-5757 Replace win32-service calls with internal API implementations that are wide-string compatibles Change By: Moses Mendoza Sprint: Platform Core Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-5757) Replace win32-service calls with internal API implementations that are wide-string compatibles
Title: Message Title
Moses Mendoza updated an issue
Puppet / PUP-5757
Replace win32-service calls with internal API implementations that are wide-string compatibles
Change By:
Moses Mendoza
win32-service has some ANSI API calls that may cause problems in a non-US language environment. *In Scope* This ticket should involve replacing API calls internally where applicable, and PUP-5758 involves the mechanics * Replace existing uses of removing the gems from puppet-win32-ruby (should that be necessary) Win32::Service , etc.The current gem implements our primarily in provider/ service hosting /windows & tests , so it may be OK to leave this in place for now - but make patches to our local copy of with the gem API defined in {{puppet PUP - win32-ruby}} and propose the same changes to the upstream gem. 7990
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7990) Create internal puppet API implementation satisfying requirements for win32-service
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7990 Create internal puppet API implementation satisfying requirements for win32-service Change By: Moses Mendoza win32-service has some ANSI API calls that may cause problems in a non-US language environment.*In Scope** Identify existing uses of the Win32::Service API, located primarily (if not entirely) in provider/service/windows* Create a new API implementation inside of puppet that meets these same requirements, using FFI or fiddle* For an example of a similar effort which defined an API replacing our need for Win32::EventLog, see https://github.com/puppetlabs/puppet/commit/a158879977570227c857ddf232bc00edac69e9fe * New API _must_ make use of the Unicode-compatible versions of functions in the Windows API Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7990) Create internal puppet API implementation satisfying requirements for win32-service
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7990 Create internal puppet API implementation satisfying requirements for win32-service Change By: Moses Mendoza Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7990) Create internal puppet API implementation satisfying requirements for win32-service
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7990 Create internal puppet API implementation satisfying requirements for win32-service Change By: Moses Mendoza Acceptance Criteria: An API exists in puppet which can be used to interface with service management in Windows, and satisfies the existing needs of the windows service provider. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7990) Create internal puppet API implementation satisfying requirements for win32-service
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7990 Create internal puppet API implementation satisfying requirements for win32-service Issue Type: Task Assignee: Unassigned Created: 2017/09/25 11:02 AM Labels: i18n utf-8 Priority: Normal Reporter: Moses Mendoza win32-service has some ANSI API calls that may cause problems in a non-US language environment. In Scope Identify existing uses of the Win32::Service API, located primarily (if not entirely) in provider/service/windows Create a new API implementation inside of puppet that meets these same requirements, using FFI or fiddle For an example of a similar effort which defined an API replacing our need for Win32::EventLog, see https://github.com/puppetlabs/puppet/commit/a158879977570227c857ddf232bc00edac69e9fe
Jira (PUP-7884) Scheduled task test audit
Title: Message Title Erick Banks assigned an issue to Michael Lombardi Puppet / PUP-7884 Scheduled task test audit Change By: Erick Banks Assignee: Michael Lombardi Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1752) Add support for AIX LPAR and WPAR detection
Title: Message Title Geoff Nichols commented on FACT-1752 Re: Add support for AIX LPAR and WPAR detection Merged to libwhereami#master at https://github.com/puppetlabs/libwhereami/commit/abd5e9f985e0484c96b67a28ecb02769f8ac0f51. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7971) Transient failure to install cisco agent
Title: Message Title Erik Dasher commented on PUP-7971 Re: Transient failure to install cisco agent This may be related to PCP-798. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1642) facter should understand cpu model on Power for the processors.model fact
Title: Message Title Geoff Nichols assigned an issue to Branan Riley Facter / FACT-1642 facter should understand cpu model on Power for the processors.model fact Change By: Geoff Nichols Assignee: Enis Inan Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7955) Update puppet to use the rubocop 0.49 or greater
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7955 Update puppet to use the rubocop 0.49 or greater Change By: Craig Gomes Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7955) Update puppet to use the rubocop 0.49 or greater
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7955 Update puppet to use the rubocop 0.49 or greater Change By: Craig Gomes Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1761) Infiniband's mac (hardware) address not provided
Title: Message Title Radosław Piliszek commented on FACT-1761 Re: Infiniband's mac (hardware) address not provided Sure thing! Infiniband hardware addresses are always 20 bytes (160 bits) long. I hope it helps. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3690) (maint) Update 5.1.x to latest ezbake
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3690 (maint) Update 5.1.x to latest ezbake Issue Type: Bug Assignee: Unassigned Created: 2017/09/25 9:56 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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
Jira (FACT-1762) valid networking facts in 3.x get ignored in 4.x
Title: Message Title Branan Riley updated an issue Facter / FACT-1762 valid networking facts in 3.x get ignored in 4.x Change By: Branan Riley Sprint: Platform OS Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1762) valid networking facts in 3.x get ignored in 4.x
Title: Message Title Branan Riley commented on FACT-1762 Re: valid networking facts in 3.x get ignored in 4.x I know we were never really happy with that munging (and we'd prefer you migrate to structured facts!), but Facter 3 was intended to be compatible with Facter 2, so I believe this is something we could take on as a bugfix in the 3.6.x series. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1762) valid networking facts in 3.x get ignored in 4.x
Title: Message Title Branan Riley updated an issue Facter / FACT-1762 valid networking facts in 3.x get ignored in 4.x Change By: Branan Riley Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-2420) CRLs should be signed with SHA256 when available
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-2420 CRLs should be signed with SHA256 when available Change By: Moses Mendoza Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7951) agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths
Title: Message Title Moses Mendoza commented on PUP-7951 Re: agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths Thanks for filing Standa eM. In Agent => Server filebucket communication the data is supposed to be sent over the network as binary with content type application/octet-stream. If it's being transcoded as UTF-8 somewhere that's a problem. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1754) fact "java_version" fails when JAVA_TOOL_OPTIONS is used
Title: Message Title Branan Riley updated an issue Facter / FACT-1754 fact "java_version" fails when JAVA_TOOL_OPTIONS is used Change By: Branan Riley Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1754) fact "java_version" fails when JAVA_TOOL_OPTIONS is used
Title: Message Title Branan Riley updated an issue Facter / FACT-1754 fact "java_version" fails when JAVA_TOOL_OPTIONS is used Change By: Branan Riley Sprint: Platform OS Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3689) (maint) Update to latest ezbake
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3689 (maint) Update to latest ezbake Issue Type: Bug Assignee: Unassigned Created: 2017/09/25 9:46 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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
Jira (FACT-1761) Infiniband's mac (hardware) address not provided
Title: Message Title Branan Riley updated an issue Facter / FACT-1761 Infiniband's mac (hardware) address not provided Change By: Branan Riley Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1761) Infiniband's mac (hardware) address not provided
Title: Message Title Branan Riley updated an issue Facter / FACT-1761 Infiniband's mac (hardware) address not provided Change By: Branan Riley Sprint: Platform OS Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1761) Infiniband's mac (hardware) address not provided
Title: Message Title Branan Riley commented on FACT-1761 Re: Infiniband's mac (hardware) address not provided We don't use ip link for mac addresses - we hit the lower-level getifaddrs() function instead. Some quick reading on the internet seems to imply that should work for infiniband interfaces, but it appears our code makes assumptions as to the length of a hardware address. I can make our code a bit smarter about handling MACs of different lengths, but I can't be 100% sure that will fix the issue without access to infiniband hardware... which I don't have. If I can provide a test build to you later in the week, will you be able to work with me on testing a possible fix? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7963) Tagged runs ignore defined resources' tags
Title: Message Title Moses Mendoza commented on PUP-7963 Re: Tagged runs ignore defined resources' tags Awesome! In that case, i'm going to close this one as a duplicate of that and we'll track the fix via PUP-7308. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7989) 404 failure when trying to fetch the latest puppetserver
Title: Message Title Enis Inan created an issue Puppet / PUP-7989 404 failure when trying to fetch the latest puppetserver Issue Type: CI Blocker Assignee: Unassigned Created: 2017/09/25 9:37 AM Labels: transient Priority: Normal Reporter: Enis Inan This occurred on the debian8-32a and windows2012r2_ja-64a platforms. Relevant part of the output: 12:24:44 Beaker::Host::CommandFailure: Host 'g14zk0fj7kz78ef.delivery.puppetlabs.net' exited with 1 running: 12:24:44 yum -y install puppetserver 12:24:44 Last 10 lines of output were: 12:24:44 4. Configure the failing repository to be skipped, if it is unavailable. 12:24:44 Note that yum will try to contact the repo. when it runs most commands, 12:24:44 so will have to try and fail each time (and thus. yum will be be much 12:24:44 slower). If it is a very temporary problem though, this is often a nice 12:24:44 compromise: 12:24:44 12:24:44 yum-config-manager --save --setopt=pl-puppetserver-latest.skip_if_unavailable=true 12:24:44 12:24:44 failure: repodata/repomd.xml from pl-puppetserver-latest: [Errno 256] No more mirrors to try. 12:24:44 http://nightlies.puppetlabs.com/puppetserver-latest/repos/el/7/PC1/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Jira (PUP-7988) resources/group/should_create test fails on fedora-26-64a
Title: Message Title Enis Inan created an issue Puppet / PUP-7988 resources/group/should_create test fails on fedora-26-64a Issue Type: CI Blocker Assignee: Unassigned Attachments: 201709025-platform_puppet-agent_intn-van-sys_suite-daily-puppet-master.log Created: 2017/09/25 9:30 AM Fix Versions: PUP 5.4.0 Priority: Normal Reporter: Enis Inan The test resources/group/should_create fails with the following output: Errored Tests Cases: 03:55:12 Test Case tests/resource/group/should_create.rb reported: # 03:55:12 if getent group pl372022; then groupdel pl372022; fi 03:55:12 Last 10 lines of output were: 03:55:12 pl372022:x:1001: 03:55:12 groupdel: cannot remove the primary group of user 'symuser'> 03:55:12 Test line: tests/resource/group/should_create.rb:22:in `block (2 levels) in run_test'
Jira (PUP-7963) Tagged runs ignore defined resources' tags
Title: Message Title
Arnaud Saric commented on PUP-7963
Re: Tagged runs ignore defined resources' tags
Hello Moses Mendoza,
I've just ran the same tests with Maggie Dreyer's patch on top of 4.10.8 and it does work with the patch:
$ puppet apply -t --tags c /var/tmp/test.pp
Info: Applying configuration version '1506356355'
Notice: /Stage[main]/A/File[/tmp/a]/ensure: defined content as '{md5}098f6bcd4621d373cade4e832627b4f6'
Info: /Stage[main]/A/File[/tmp/a]: Scheduling refresh of B[-]
Info: B[-]: Scheduling refresh of Exec[cat /tmp/a]
Notice: /Stage[main]/A/B[-]/Exec[cat /tmp/a]/returns: test
Notice: /Stage[main]/A/B[-]/Exec[cat /tmp/a]: Triggered 'refresh' from 1 events
Info: Stage[main]: Unscheduling all events on Stage[main]
Notice: Applied catalog in 0.13 seconds
Jira (PUP-7987) Add support to defined top scope variables to the Pal API
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-7987 Add support to defined top scope variables to the Pal API Issue Type: Improvement Assignee: Thomas Hallgren Created: 2017/09/25 9:21 AM Priority: Normal Reporter: Henrik Lindberg The Puppet::Pal API when creating a tmp or regular environment should accept a hash of variable names to values that it will use to define those top scope variables. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1762) valid networking facts in 3.x get ignored in 4.x
Title: Message Title Thomas J Miller jr commented on FACT-1762 Re: valid networking facts in 3.x get ignored in 4.x Thank you for confirming that I'm still sane Please let me know of any changes/fixes that occur, though we have implemented a workaround (detailed in the description) that has equal efficacy and minimal future impact. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7986) Puppet tests do not wait for the puppet-agent install on Windows to finish
Title: Message Title Enis Inan created an issue Puppet / PUP-7986 Puppet tests do not wait for the puppet-agent install on Windows to finish Issue Type: CI Blocker Assignee: Unassigned Attachments: 20170925-platform_puppet-agent_intn-van-sys_suite-daily-puppet-1.10.x.log Created: 2017/09/25 9:16 AM Fix Versions: PUP 4.10.9 Priority: Normal Reporter: Enis Inan https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/1.10.x/view/Suite/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-1.10.x/62/SLAVE_LABEL=beaker,TEST_TARGET=windows2012r2-64a/ The relevant part of the output is: p72wdcdl1rtxf54.delivery.puppetlabs.net (windows2012r2-64-1) executed in 0.07 seconds Exited: 1 Beaker::Host::CommandFailure: Host 'p72wdcdl1rtxf54.delivery.puppetlabs.net' exited with 1 running: cmd.exe /c puppet --version Last 10 lines of output were: 'puppet' is not recognized as an internal or external command, operable program or batch file. ^This type of failure means that the install has not completed yet
Jira (FACT-1762) valid networking facts in 3.x get ignored in 4.x
Title: Message Title Michael Smith commented on FACT-1762 Re: valid networking facts in 3.x get ignored in 4.x This was likely unintentional. Facter 3 was a rewrite, and it looks like we missed how Facter 2 was munging the network interface names. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1762) valid networking facts in 3.x get ignored in 4.x
Title: Message Title Michael Smith updated an issue Facter / FACT-1762 valid networking facts in 3.x get ignored in 4.x Change By: Michael Smith Affects Version/s: FACT 3.9.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3114) Puppet needs to use default keylength 2048 on FIPS enabled systems
Title: Message Title Trevor Vaughan commented on PUP-3114 Re: Puppet needs to use default keylength 2048 on FIPS enabled systems Jayant Sane The 2048, 3072, and 15360 key sizes were found by trial and error based on the FIPS documentation and an understanding of the standard key sizes. 4096 may work on EL7, but check EL6 as well. They may have updated both, and that would be nice, but you're going to be in a bit of a bind if you end up with different systems that support different settings based on patch-level. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7980) Add a run_script() function to enable this bolt feature from the language
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7980 Add a run_script() function to enable this bolt feature from the language Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7979) Add a run_command() function
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7979 Add a run_command() function Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7980) Add a run_script() function to enable this bolt feature from the language
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7980 Add a run_script() function to enable this bolt feature from the language Change By: Kenn Hussey Sprint: Tasks EUP (PuppetConf) Kanban Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7979) Add a run_command() function
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7979 Add a run_command() function Change By: Kenn Hussey Sprint: Tasks EUP (PuppetConf) Kanban Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7980) Add a run_script() function to enable this bolt feature from the language
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7980 Add a run_script() function to enable this bolt feature from the language Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7981) Puppet extension for Linux disappeared from Azure
Title: Message Title Kevin Reeuwijk commented on PUP-7981 Re: Puppet extension for Linux disappeared from Azure Why wouldn't we have an extension handler for Linux? Linux is our main platform... Automation of cloud deployments is significantly easier when the agent can be bootstrapped as part of the VM deployment template. Why do Azure users have to use a custom script extension to do this while Chef does provide an extension for both Linux and Windows? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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.
