Jira (PUP-7295) Puppet is too permissive about skipping SSL verification
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-7295 Puppet is too permissive about skipping SSL verification Change By: Adrien Thebo Assignee: Adrien Thebo 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 Adrien Thebo assigned an issue to Unassigned Puppet / PUP-3114 Puppet needs to use default keylength 2048 on FIPS enabled systems Change By: Adrien Thebo Assignee: Adrien Thebo 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-6824) Use UUIDs for certificate serial numbers
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-6824 Use UUIDs for certificate serial numbers Change By: Adrien Thebo Assignee: Adrien Thebo 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-7295) Puppet is too permissive about skipping SSL verification
Title: Message Title
Adrien Thebo updated an issue
Puppet / PUP-7295
Puppet is too permissive about skipping SSL verification
Change By:
Adrien Thebo
The majority of SSL connections Puppet makes to Puppet masters (which are mainly done by the indirector) can rely on the CA cert and a signed client certificate being available, which means that we can perform SSL peer verification and can provide a client certificate for client cert based authentication. However the current behavior of the SSL Validator code is able to downgrade to an unauthenticated connection at any point. This introduces unneeded risk when we can clearly identify the small set of code paths that might have a real reason for using a less thorough validator.Instead of having our validators defaulting to no validation, we should reverse this. The default validator should require a CA certificate for peer verification and should have a client certificate available in case client cert based authentication is required. The code paths that need to have reduced validators should specifically use those validators when absolutely necessary and should default to using the cert auth validator in all other cases.The locations that I can think of that can justify reducing or disabling verification are as follows: * Fetching the CA certificate when we don't have a local copy of the CA certificate (AKA { { :localcacert} } ). * Submitting a CSR when a client certificate isn't available (AKA { { :hostcert} } ).
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message
Jira (PUP-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Adrien Thebo Sprint: AP 2017-01-11, AP 2017-03-08, Agent 2017-03-22, Platform Core KANBAN 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-1391) puppet device cannot create certs when run as root
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1391 puppet device cannot create certs when run as root Change By: Adrien Thebo 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-7951) agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-7951 agent - server setup - file bucketing for binary files fails in case same file is bucketed for 2 different paths Change By: Adrien Thebo Assignee: Adrien Thebo 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-7845) Support leaf certificate CRL checking
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7845 Support leaf certificate CRL checking See the `certificate_revocation` documentation for more information about the new `leaf` setting. https://github.com/puppetlabs/puppet/blob/5.3.1/lib/puppet/defaults.rb#L859 Change By: Adrien Thebo Release Notes Summary: Puppet can be configured to perform end entity certificate revocation checking. When the `certificate_revocation` setting is set to `leaf` and Puppet is authenticating an SSL connection, Puppet will check the revocation status of the end entity certificate of the peer, instead of attempting to check the revocation status of every certificate in the chain. This allows users to perform basic revocation checking when using an intermediate CA certificate with Puppet. 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
Jira (PUP-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Adrien Thebo Assignee: Adrien Thebo 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-7985) `puppet cert generate` uses the wrong CA certificate
Title: Message Title Adrien Thebo created an issue Puppet / PUP-7985 `puppet cert generate` uses the wrong CA certificate Issue Type: Bug Assignee: Unassigned Created: 2017/09/22 4:28 PM Priority: Normal Reporter: Adrien Thebo When `puppet cert generate` is invoked, it configures itself as a "local" CA. This configures the indirector 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 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. To add to the fun, when this circumstance appears Puppet is hardcoded to indicate that the agent private key and certificate don't match, and debugging this is effectively impossible without injecting pry invocations through the source code.
Jira (PUP-7984) `puppet cert revoke` doesn't verify the loaded CRL
Title: Message Title Adrien Thebo created an issue Puppet / PUP-7984 `puppet cert revoke` doesn't verify the loaded CRL Issue Type: Bug Assignee: Unassigned Created: 2017/09/22 3:21 PM Priority: Normal Reporter: Adrien Thebo When Puppet loads the CRL in order to revoke a certificate, it does so without verifying that the loaded CRL was issued by the CA that will be revoking the certificate. If a user mistakenly copied a CRL from a different CA to where Puppet will load it, and then revokes a certificate, Puppet will merrily add the serial number of the revoked certificate, sign the CRL using the wrong CA key, and will leave the Issuer field alone. If this CRL is used it will contain revocation information for two unrelated PKIs and the Issuer field of the original CA. This is problematic because identifying and resolving the issue is extremely difficult to do without a deep understanding of X.509. In environments where people are using intermediate CAs it's not unreasonable for them to accidentally copy a CRL from the root CA into the intermediate CA environment, which will create and distribute unusable CRLs. Add Comment
Jira (PUP-7451) Puppet HTTP client should respect Retry-After headers
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-7451 Puppet HTTP client should respect Retry-After headers Change By: Adrien Thebo Assignee: Adrien Thebo 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-7845) Support leaf certificate CRL checking
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-7845 Support leaf certificate CRL checking Change By: Adrien Thebo Assignee: Adrien Thebo 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-4755) Puppet config set --section main foo bar does not set or respect an empty [main] section
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-4755 Puppet config set --section main foo bar does not set or respect an empty [main] section Change By: Adrien Thebo Assignee: Adrien Thebo 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-4065) errors/warnings in environment.conf should not be duplicated
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-4065 errors/warnings in environment.conf should not be duplicated Change By: Adrien Thebo Labels: this_issue_is_bad_and_you_should_feel_bad 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-7941) Autogenerated custom types never get all properties set
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7941 Autogenerated custom types never get all properties set Change By: Adrien Thebo Team: Platform Core 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-7948) selmodversion_loaded lines variable broken
Title: Message Title
Adrien Thebo updated an issue
Puppet / PUP-7948
selmodversion_loaded lines variable broken
Change By:
Adrien Thebo
I was playing with rubocop when it complained about:{code}== lib/puppet/provider/selmodule/semodule.rb ==W:121: 13: Lint/EmptyExpression: Avoid empty expressions.{code}Looking at the code its complaining about the "lines = ()" assignment:{code} def selmodversion_loadedlines = ()begin execpipe("#{command(:semodule)} --list") do |output|output.each_line do |line| line.chomp! bits = line.split if bits[0] == @resource[:name]self.debug "load version #{bits[1]}"return bits[1] endend endrescue Puppet::ExecutionFailure raise Puppet::ExecutionFailure, "Could not list policy modules: #{lines.join(' ').chomp!}", $!.backtraceendnil end{code ] } Looking at the code, lines will be assigned "nil" which doesn't have a .join method. So the exception will fail. We also fail to do anything with the lines variable in the method so if it was intended to be an array, it never gets changed from an empty array which is kind of pointless.We should enable "Lint/EmptyExpression" in the .robocop.yml if when this is fixed and we're on 0.49 or greater.
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
Jira (PUP-7950) Allow specifying an MD5 URI for files with HTTP(s) sources
Title: Message Title Adrien Thebo commented on PUP-7950 Re: Allow specifying an MD5 URI for files with HTTP(s) sources Thank you for filing this issue. We agree it is likely an improvement, but due to other issues demanding precedence, we don’t anticipate being able to address this any time soon. If you are interested in submitting a patch to the repository for this project at https://github.com/puppetlabs, please open a pull request for this feature. 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
Adrien Thebo 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:
Adrien Thebo
Scenario: Puppet Agent is bucketing file to PuppetserverFollowing scenario (but in agent-server) configuration should show the error: {noformat} puppet apply -e 'file { "/tmp/d1/file1": source => "/usr/bin/at" }'puppet apply -e 'file { "/tmp/d1/file1": source => "/usr/bin/bash" }'# file1 already exists, so it is bucketed before rewritten by contents of 'bash'puppet apply -e 'file { "/tmp/d2/file2": source => "/usr/bin/at" }'puppet apply -e 'file { "/tmp/d2/file2": source => "/usr/bin/bash" }'# file2 already exists, so it is bucketed before rewritten by contents of 'bash'. It is bucketed to same directory on server because md5 hash of file2 is same as md5 hash of bucketed file1. And bucketing fails. {noformat} In theory this should work. And for local bucketing it works. There are 2 artefacts on server for each bucketed file - contents and paths. Paths contains all paths where contents was stored on origin system.When file is bucketed there are multiple checks - size, md5 hash and file to be bucketed is byte-to-byte compared with already bucketed file.In case that given file is bucketed (file with md5sum hash exists on server) and path on origin system is different to path stored in 'paths' than there are 2 checks - size of backeted file and chacksum. Size is compared between data of file received over network from agent and existing 'contents' on server.The problem is, that this comparison usually fails because encoding of data received over network are 'UTF-8' encoded and contents is "like" plain bytes. So size doesn't match and it is considered error and processing of file resource fails.For puppet-agent-1.10.4-1.el7.x86_64 rpm:Comparison is in: method Puppet::FileBucketFile::File.verify_identical_file()bucket_file is: Puppet::FileBucket::File::StringContentsSolution should be to ensure size of data received over network to be converted to something like "ASCII-8BIT" encoding even for 'size' operation.
Add Comment
Jira (PUP-7953) Add git:// as a source in the File class
Title: Message Title Adrien Thebo commented on PUP-7953 Re: Add git:// as a source in the File class Thank you for filing this issue. However, we believe this change represents a technical direction that we have decided not to follow in Puppet. The reasoning behind this decision is that adding such functionality to core Puppet would bring in a number of dependencies and complexity as well as ongoing maintenance obligations, and right now these costs are greater than the benefit of having this functionality in core Puppet. In theory this behavior could be implemented as an extension in the form of a provider for the File type, though off the cuff I can't gauge the complexity of taking this implementation approach. As such, we are closing this as “Won’t Do”. If any watcher believes this is an error, please add a comment explaining. 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-7957) Puppet uses SHA1 when revoking certificates
Title: Message Title Adrien Thebo created an issue Puppet / PUP-7957 Puppet uses SHA1 when revoking certificates Issue Type: Bug Affects Versions: PUP 5.2.0, PUP 4.10.8 Assignee: Unassigned Created: 2017/09/18 9:22 AM Priority: Major Reporter: Adrien Thebo When Puppet revokes a certificate and updates the corresponding CRL, it uses SHA1 for generating the CRL signature. SHA1 is being deprecated and should be replaced by SHA256 or better. Add Comment
Jira (PUP-4755) Puppet config set --section main foo bar does not set or respect an empty [main] section
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-4755 Puppet config set --section main foo bar does not set or respect an empty [main] section Change By: Adrien Thebo Sprint: Platform Core Hopper 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-7451) Puppet HTTP client should respect Retry-After headers
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-7451 Puppet HTTP client should respect Retry-After headers Change By: Adrien Thebo Assignee: Patrick Carlisle Adrien Thebo Sprint: Platform Core Hopper 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-4755) Puppet config set --section main foo bar does not set or respect an empty [main] section
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-4755 Puppet config set --section main foo bar does not set or respect an empty [main] section Change By: Adrien Thebo Assignee: Adrien Thebo 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Adrien Thebo Sprint: AP 2017-01-11, AP 2017-03-08, Agent 2017-03-22, Platform Core Hopper 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Adrien Thebo commented on PUP-6986 Re: Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars PR is currently targeted at 4.10.x; I'm inquiring into whether we can retarget it at master to make the merge easier to justify. 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Adrien Thebo Assignee: Adrien Thebo 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-7844) A Puppet report from an interrupted run can cause exit_status to throw an exception
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7844 A Puppet report from an interrupted run can cause exit_status to throw an exception Change By: Adrien Thebo Sprint: Platform Core Hopper 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-7845) Support leaf certificate CRL checking
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7845 Support leaf certificate CRL checking Change By: Adrien Thebo Sprint: Platform Core 2017-08-22, Platform Core Hopper 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-7918) puppet fails to change user group membership if directory group names have spaces
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7918 puppet fails to change user group membership if directory group names have spaces Change By: Adrien Thebo 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-7929) No ensure property default value for types without any other property set
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7929 No ensure property default value for types without any other property set Change By: Adrien Thebo Team: Platform Core 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-7938) I18N Indented and line wrapped face plugin output
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7938 I18N Indented and line wrapped face plugin output Change By: Adrien Thebo Team: Platform Core 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-7928) Error: Facter: error while resolving custom fact "environment": undefined method `application_name' for Puppet:Module
Title: Message Title Adrien Thebo commented on PUP-7928 Re: Error: Facter: error while resolving custom fact "environment": undefined method `application_name' for Puppet:Module In order to resolve this ticket we need to steps to reproduce the issue locally; without that information we aren't able to fix this issue. I'm closing this issue until we have more information; when you're able to provide that information please reopen it and we can continue the conversation from there. 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-7935) Prefetching custom types not possible if namevar is not "name"
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7935 Prefetching custom types not possible if namevar is not "name" Change By: Adrien Thebo Team: Platform Core 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-7931) Support HTTPS Compression on report upload
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7931 Support HTTPS Compression on report upload Change By: Adrien Thebo Team: Platform Core 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-7936) double space versus single space in output messages
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7936 double space versus single space in output messages Change By: Adrien Thebo Team: Platform Core 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-7934) I18N dates in localized output should also be localized
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7934 I18N dates in localized output should also be localized Change By: Adrien Thebo Team: Platform Core 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-7937) extra "." or missing "." in csr message
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7937 extra "." or missing "." in csr message Change By: Adrien Thebo Team: Platform Core 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-6697) Allow full downloaded CA bundle to be stored to agent's localcacert file
Title: Message Title Adrien Thebo commented on PUP-6697 Re: Allow full downloaded CA bundle to be stored to agent's localcacert file This ticket has the same issues that we have with using multiple CRLs, as described in this comment on PUP-3788. Right now Puppet/the Indirector assumes the certificate endpoint will return a single entry and doesn't have good support for searching for and caching multiple entries. Once we do the necessary work to implement PUP-3788 this will be simpler, but implementing this means making some nontrivial changes to the indirector or extracting the CA certificate downloading and caching logic out of the indirector. 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-7845) Support leaf certificate CRL checking
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-7845 Support leaf certificate CRL checking Change By: Adrien Thebo Assignee: Adrien Thebo 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-7845) Support leaf certificate CRL checking
Title: Message Title Adrien Thebo created an issue Puppet / PUP-7845 Support leaf certificate CRL checking Issue Type: New Feature Assignee: Unassigned Created: 2017/08/15 11:55 AM Priority: Normal Reporter: Adrien Thebo Apache 2.4 added the SSLCARevocationCheck setting, which controls the depth of revocation checking done for client certificates. Supporting leaf certificate revocation checking provides the same level of security as full chain checking when intermediate CAs are not used, and still provides a good level of security when intermediate CAs are in use. The work required for full chaining (discussed in PUP-3788) is fairly involved, so while we're working on the larger picture we should support leaf revocation checking so that CRLs can be used in some form when intermediate CAs are in use. Add Comment
Jira (PUP-4549) puppet acts like a module's subcommand doesn't exist if given a bad --environmentpath
Title: Message Title Adrien Thebo commented on PUP-4549 Re: puppet acts like a module's subcommand doesn't exist if given a bad --environmentpath Setting the environmentpath to a location where Puppet can't find the preview module code, and then expecting Puppet to find it anyways, isn't really a solvable problem. Per Charlie's comments the module itself could be installed in a different location but we can't fix the issue where setting the environmentpath incorrectly leads Puppet to miss installed modules. 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-3788) Puppet Agent does not support Chained CRLs
Title: Message Title Adrien Thebo commented on PUP-3788 Re: Puppet Agent does not support Chained CRLs The assumption that Puppet will have a single CRL is wired deeply into the code and unwinding this assumption may require a number of nontrivial and potentially dangerous changes. First off, Puppet::SSL::CertificateRevocationList itself is hardcoded for a single CRL, and it hardcodes a number of things like the CRL name. For example: # Convert a string into an instance. def self.from_s(string) super(string, 'foo') # The name doesn't matter end # ... # The name doesn't actually matter; there's only one CRL. # We just need the name so our Indirector stuff all works more easily. def initialize(fakename)
Jira (PUP-3788) Puppet Agent does not support Chained CRLs
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-3788 Puppet Agent does not support Chained CRLs Change By: Adrien Thebo Assignee: Adrien Thebo 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-1677) facter get child interfaces's ip address twice with intended for the primary interface
Title: Message Title Adrien Thebo updated an issue Facter / FACT-1677 facter get child interfaces's ip address twice with intended for the primary interface Change By: Adrien Thebo 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-1677) facter get child interfaces's ip address twice with intended for the primary interface
Title: Message Title Adrien Thebo updated an issue Facter / FACT-1677 facter get child interfaces's ip address twice with intended for the primary interface Change By: Adrien Thebo Labels: offboarding 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-1722) off-by-one error in using gethostname()
Title: Message Title
Adrien Thebo updated an issue
Facter / FACT-1722
off-by-one error in using gethostname()
Change By:
Adrien Thebo
PR filed as https://github.com/puppetlabs/facter/pull/1605On Linux hosts with hostnames of exactly 64 bytes, facter fqdn fails with the same error from FACT-1238. Digging into the spec, the Linux manpage for gethostname(2) says...POSIX.1 guarantees that "Host names (not including the terminating null byte)are limited to HOST_NAME_MAX bytes". On Linux, HOST_NAME_MAX isdefined with the value 64, which has been the limit since Linux 1.0(earlier kernels imposed a limit of 8 bytes).The "you have to count the null byte" behavior is confirmed in the spec (link), so this should be true everywhere vaguely unix-like.{HOST_NAME_MAX}Maximum length of a host name (not including the terminating null) as returned from the gethostname() function.Here's a trivial example: {noformat} tmaher@lowryder:~/puppet-fqdn-bug$ hostname -flowryder.pw0n.metmaher@lowryder:~/puppet-fqdn-bug$ ./offbyoneHOST_NAME_MAX: 64PASS: lowryderPASS: size 65, lowrydertmaher@lowryder:~/puppet-fqdn-bug$ sudo hostname a23456789.b23456789.c23456789.d23456789.e23456789.f23456789.wxyztmaher@lowryder:~/puppet-fqdn-bug$ hostnamea23456789.b23456789.c23456789.d23456789.e23456789.f23456789.wxyztmaher@lowryder:~/puppet-fqdn-bug$ host=$(hostname); echo -n $host | wc -c64tmaher@lowryder:~/puppet-fqdn-bug$ ./offbyoneHOST_NAME_MAX: 64FAIL: size 64, error File name too long (errno 36)PASS: size 65, a23456789.b23456789.c23456789.d23456789.e23456789.f23456789.wxyz {noformat} {noformat} tmaher@lowryder:~/puppet-fqdn-bug$ cat offbyone.c#include #include #include #include #include #include #include #include int main(void){ int size = sysconf(_SC_HOST_NAME_MAX); char buffer[256]; printf("HOST_NAME_MAX: %d\n", size); errno = 0; if (gethostname(buffer, size) != 0){printf("FAIL: size %d, error %s (errno %d)\n", size, strerror(errno), errno); } else {printf("PASS: %s\n", buffer); } size += 1; if (gethostname(buffer, size) != 0){printf("FAIL: size %d, error %s (errno %d)\n", size, strerror(errno), errno); } else {printf("PASS: size %d, %s\n", size, buffer); } return 0;} {noformat}
Add Comment
Jira (PUP-1935) puppetd ignores local ca.pem when connecting to master for the first time
Title: Message Title Adrien Thebo commented on PUP-1935 Re: puppetd ignores local ca.pem when connecting to master for the first time I believe https://github.com/adrienthebo/puppet/tree/revert-pup-7283 was the last branch that touched this. There were some issues with acceptance tests that caused this to be rejected, it just needs a bit of work to chase down the last issues. 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-7749) Puppet to read "X509v3 Extended Key Usage" for trusted facts
Title: Message Title Adrien Thebo commented on PUP-7749 Re: Puppet to read "X509v3 Extended Key Usage" for trusted facts Per Eric's comment, we don't plan on using the X.509v3 extended key attribute certificate extension and thus don't plan on exposing it as part of trusted facts. The reasoning for this is that not many services respect that value, there's limited use of that field since it can only contain OIDs, and the general certificate extensions provide enough flexibility for policy autosigning. That said this can be worked around via a custom function. A general sketch of this function would be as follows: Fetch the raw certificate from the CA server via the puppetserver CA endpoint (https://docs.puppet.com/puppet/latest/http_api/http_certificate.html#find) Decode the certificate, you can probably use Puppet::SSL::Certificate.from_s to decode the string (https://github.com/puppetlabs/puppet/blob/master/lib/puppet/ssl/certificate.rb) Extract the extended key usage attribute and decode it as necessary; https://github.com/puppetlabs/puppet/blob/master/lib/puppet/ssl/certificate.rb#L79 might be of use here. So if you really need this then you can build it in, but as it stands it's quite unlikely that we'll build this into the product itself. 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
Jira (PUP-7192) Add state machines for complex logic in Puppet
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7192 Add state machines for complex logic in Puppet Change By: Adrien Thebo 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-7192) Add state machines for complex logic in Puppet
Title: Message Title Adrien Thebo commented on PUP-7192 Re: Add state machines for complex logic in Puppet This work was reverted and never shipped. 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-7283) Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization
Title: Message Title Adrien Thebo commented on PUP-7283 Re: Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization Sean McDonald this work could not be completed and was not shipped. 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-7283) Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7283 Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization Change By: Adrien Thebo 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 (PDB-1919) Move away from `moustache` to `compojure`
Title: Message Title Adrien Thebo updated an issue PuppetDB / PDB-1919 Move away from `moustache` to `compojure` Change By: Adrien Thebo Labels: triaged 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-1872) puppetdb module problems on centos7 after "Add pathing for AIO" commit
Title: Message Title Adrien Thebo updated an issue PuppetDB / PDB-1872 puppetdb module problems on centos7 after "Add pathing for AIO" commit Change By: Adrien Thebo Labels: triaged 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-1223) Unexpected behavior in apply run mode with resource indirection
Title: Message Title Adrien Thebo updated an issue PuppetDB / PDB-1223 Unexpected behavior in apply run mode with resource indirection Change By: Adrien Thebo Labels: triaged 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-1223) Unexpected behavior in apply run mode with resource indirection
Title: Message Title
Adrien Thebo commented on PDB-1223
Re: Unexpected behavior in apply run mode with resource indirection
I tested this against PE 2016.5.1 and couldn't reproduce:
[root@pe-201651-master puppet]# cat test.pp
service { 'vboxadd-x11':
ensure => 'running',
enable => 'false',
}
[root@pe-201651-master puppet]# puppet apply test.pp
Notice: Compiled catalog for pe-201651-master.puppetdebug.vlan in environment production in 0.36 seconds
Notice: Applied catalog in 0.36 seconds
[root@pe-201651-master puppet]# puppet resource service | head
Jira (PDB-1273) -Djava.net.preferIPv4Stack=true should be set by default in /etc/sysconfig/puppetdb
Title: Message Title Adrien Thebo updated an issue PuppetDB / PDB-1273 -Djava.net.preferIPv4Stack=true should be set by default in /etc/sysconfig/puppetdb Change By: Adrien Thebo Labels: triaged 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-1273) -Djava.net.preferIPv4Stack=true should be set by default in /etc/sysconfig/puppetdb
Title: Message Title Adrien Thebo commented on PDB-1273 Re: -Djava.net.preferIPv4Stack=true should be set by default in /etc/sysconfig/puppetdb This would be a breaking change and could surprise a lot of users. In addition RFC3484 indicates that IPv6 should be preferred when available, and I don't like overriding RFC recommendations. In an ideal world the JVM would respect /etc/gai.conf and render this concern moot, but that's only an option for jdk9 (https://bugs.openjdk.java.net/browse/JDK-8016521). For what it's worth I saw openjdk demonstrating this desired behavior on SERVER-1801 , so it's happening by default - for Puppetserver at least. In any case, operators in an IPv6 enabled environment will have to deal with these concerns for a lot of software stacks, so I'd rather conform to JVM standard behavior. PDB-1430 does allow users to manage /etc/sysconfig/puppetdb so that they can add this setting if it's appropriate for their environment. 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-4393) Tidy and Mount interaction has a race condition
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-4393 Tidy and Mount interaction has a race condition Change By: Adrien Thebo Labels: this_issue_is_bad_and_you_should_feel_bad triaged 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-2250) [UX] Initial version of UI mockup
Title: Message Title Adrien Thebo commented on PDB-2250 Re: [UX] Initial version of UI mockup This looks like an orphaned autogenerated ticket, closing. 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-2250) [UX] Initial version of UI mockup
Title: Message Title Adrien Thebo updated an issue PuppetDB / PDB-2250 [UX] Initial version of UI mockup Change By: Adrien Thebo Labels: triaged 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-767) Show if an event was due to a change in the catalog or not
Title: Message Title Adrien Thebo updated an issue PuppetDB / PDB-767 Show if an event was due to a change in the catalog or not Change By: Adrien Thebo Labels: triaged 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-159) Corrupt KahaDB db.data file may cause exception upon receiving any command
Title: Message Title Adrien Thebo commented on PDB-159 Re: Corrupt KahaDB db.data file may cause exception upon receiving any command ActiveMQ and the accompanying KahaDB functionality was removed as part of https://tickets.puppetlabs.com/browse/PDB-2730. 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-133) "puppet node clean" complains about missing sqlite3 lib when using PuppetDB as stored configs backend
Title: Message Title Adrien Thebo updated an issue PuppetDB / PDB-133 "puppet node clean" complains about missing sqlite3 lib when using PuppetDB as stored configs backend Change By: Adrien Thebo Labels: needs_repro redmine triaged 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-133) "puppet node clean" complains about missing sqlite3 lib when using PuppetDB as stored configs backend
Title: Message Title Adrien Thebo commented on PDB-133 Re: "puppet node clean" complains about missing sqlite3 lib when using PuppetDB as stored configs backend This was resolved in PUP-405 when the legacy storeconfigs functionality was removed; Michael Witrant if this is still an issue with Puppet 4 or later please reopen this ticket and we can continue to investigate. 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-133) "puppet node clean" complains about missing sqlite3 lib when using PuppetDB as stored configs backend
Title: Message Title Adrien Thebo updated an issue PuppetDB / PDB-133 "puppet node clean" complains about missing sqlite3 lib when using PuppetDB as stored configs backend Change By: Adrien Thebo Labels: needs_repro redmine 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-20) Establish consistent pattern for establishing sample data for unit tests
Title: Message Title Adrien Thebo updated an issue PuppetDB / PDB-20 Establish consistent pattern for establishing sample data for unit tests Change By: Adrien Thebo Labels: puppetdb technical_debt triaged 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-3093) PMT upgrade fails if installed version has invalid semver
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3093 PMT upgrade fails if installed version has invalid semver Change By: Adrien Thebo Labels: triaged 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-3132) Resources type unless_uid exhibits bad behavior
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-3132 Resources type unless_uid exhibits bad behavior Change By: Adrien Thebo Assignee: Kylo Ginsberg 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-3073) Error message "Could not send report": appear when puppet client is pulling config from puppet master
Title: Message Title Adrien Thebo commented on PUP-3073 Re: Error message "Could not send report": appear when puppet client is pulling config from puppet master Thank you for reporting this issue. However, we believe this issue only affects a version of Puppet that has reached its end of life or is no longer supported. For more info on getting the current version of Puppet Agent, see https://docs.puppet.com/puppet/latest/install_pre.html. 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-3087) PMT upgrade should let you specify the path to your modules
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3087 PMT upgrade should let you specify the path to your modules Change By: Adrien Thebo Labels: help_wanted triaged 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-3087) PMT upgrade should let you specify the path to your modules
Title: Message Title Adrien Thebo commented on PUP-3087 Re: PMT upgrade should let you specify the path to your modules Thank you for filing this issue. We agree it is likely an improvement, but due to other issues demanding precedence, we don’t anticipate being able to address this any time soon. If you are interested in submitting a patch to the repository for this project at https://github.com/puppetlabs, please open a pull request and re-open this ticket. Pending that, we are closing this as “Won’t Fix.” We may revisit it at a later time, and if so will re-open this ticket. 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-3118) Run vendored library spec tests from top-level rake tasks
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3118 Run vendored library spec tests from top-level rake tasks Change By: Adrien Thebo Labels: needs_decision triaged 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-3118) Run vendored library spec tests from top-level rake tasks
Title: Message Title Adrien Thebo assigned an issue to Britt Gresham Puppet / PUP-3118 Run vendored library spec tests from top-level rake tasks Change By: Adrien Thebo Assignee: Britt Gresham 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-3118) Run vendored library spec tests from top-level rake tasks
Title: Message Title Adrien Thebo commented on PUP-3118 Re: Run vendored library spec tests from top-level rake tasks Britt Gresham do you think we'll actually get to this, or can we close it out? 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-3118) Run vendored library spec tests from top-level rake tasks
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3118 Run vendored library spec tests from top-level rake tasks Change By: Adrien Thebo Labels: triaged 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-3004) Shadow password updated by agent but not while running in daemon
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3004 Shadow password updated by agent but not while running in daemon Change By: Adrien Thebo Labels: triaged 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-3004) Shadow password updated by agent but not while running in daemon
Title: Message Title Adrien Thebo commented on PUP-3004 Re: Shadow password updated by agent but not while running in daemon This is probably an issue with how Ruby is installed and the environment in which Puppet is run by the system service manager. Puppet 4.0 changed to use an all in one environment that sidestepped possible environmental/load issues. However, we haven’t been able to reproduce this against the current version of Puppet, and are closing this issue now as Cannot Reproduce. If you have additional information or reproduction scenarios that may be of use, please comment in this ticket with details. 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-3052) puppet doc --mode rdoc fails with two pp files in a directory when using future parser
Title: Message Title Adrien Thebo commented on PUP-3052 Re: puppet doc --mode rdoc fails with two pp files in a directory when using future parser puppet doc was deprecated/removed in PUP-3638 and has been replaced with puppet-strings (https://github.com/puppetlabs/puppet-strings). 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-3052) puppet doc --mode rdoc fails with two pp files in a directory when using future parser
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3052 puppet doc --mode rdoc fails with two pp files in a directory when using future parser Change By: Adrien Thebo Labels: triaged 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-3040) Change init/upstart instance-based services from blacklist to whitelist
Title: Message Title Adrien Thebo commented on PUP-3040 Re: Change init/upstart instance-based services from blacklist to whitelist Thank you for filing this issue. However, we believe this change represents a technical direction that we have decided not to follow in Puppet. As such, we are closing this as “Won’t Do”. If any watcher believes this is an error, please add a comment explaining. 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-3059) add support for crlDistributionPoint
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3059 add support for crlDistributionPoint Change By: Adrien Thebo Labels: triaged 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-3014) Add acceptance test for PMT generate command changes for 3.7
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3014 Add acceptance test for PMT generate command changes for 3.7 Change By: Adrien Thebo Labels: triaged 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-3011) Add acceptance test for PMT install command changes for 3.7
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3011 Add acceptance test for PMT install command changes for 3.7 Change By: Adrien Thebo Labels: triaged 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-3012) Add acceptance test for PMT upgrade command changes for 3.7
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3012 Add acceptance test for PMT upgrade command changes for 3.7 Change By: Adrien Thebo Labels: triaged 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-3055) file type can't implicitly manage /
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3055 file type can't implicitly manage / Change By: Adrien Thebo Labels: triaged 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-3055) file type can't implicitly manage /
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-3055 file type can't implicitly manage / Change By: Adrien Thebo Assignee: Kylo Ginsberg 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-3055) file type can't implicitly manage /
Title: Message Title Adrien Thebo commented on PUP-3055 Re: file type can't implicitly manage / Thank you for filing this issue. We agree it is likely an improvement, but due to other issues demanding precedence, we don’t anticipate being able to address this any time soon. If you are interested in submitting a patch to the repository for this project at https://github.com/puppetlabs, please open a pull request and re-open this ticket. Pending that, we are closing this as “Won’t Fix.” We may revisit it at a later time, and if so will re-open this ticket. 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-3085) possible Directory Environments bug
Title: Message Title Adrien Thebo commented on PUP-3085 Re: possible Directory Environments bug This ticket has not been updated in some time and is now being closed due to inactivity. This isn’t necessarily a statement that this ticket isn’t important - other issues may have demanded precedence since it was filed, or it may have simply slipped through the cracks. If any viewer/watcher feels closing this ticket is an error, please re-open it and add a comment explaining. Our apologies in advance for any mistake on this. 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-3122) It's time we wrote a more usable no cert found warning!
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-3122 It's time we wrote a more usable no cert found warning! Change By: Adrien Thebo Assignee: Kylo Ginsberg 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-3122) It's time we wrote a more usable no cert found warning!
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3122 It's time we wrote a more usable no cert found warning! Change By: Adrien Thebo Labels: triaged 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-3147) New gid fact is causing problems in one of my defined types
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3147 New gid fact is causing problems in one of my defined types Change By: Adrien Thebo Labels: needs_repro triaged 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-3147) New gid fact is causing problems in one of my defined types
Title: Message Title Adrien Thebo commented on PUP-3147 Re: New gid fact is causing problems in one of my defined types We'll need to get a reproduction case to see if the variable shadowing or lack thereof is an issue. 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-3187) Puppet file parameter selinux_ignore_defaults doesn't work as expected
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3187 Puppet file parameter selinux_ignore_defaults doesn't work as expected Change By: Adrien Thebo Labels: triaged 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-3193) No way to create a sysidcfg for a zone with multiple network interfaces
Title: Message Title
Adrien Thebo updated an issue
Puppet / PUP-3193
No way to create a sysidcfg for a zone with multiple network interfaces
Change By:
Adrien Thebo
When creating a zone we can set sysidcfg to a template that generates the sysidcfg file. In the documentation there is a example. When configuring a zone with 2 interface the 'network_interface' is not 'primary' but the interface name. The problem i have is that the interface name i set in the puppet file is not the interface name needed in the sysidcfg.erb file. In the sysidcfg file the interface is extend with a number, which depends on the global zone.Below example has the networkinterface in the sysidcfg.erb hardcoded to get it to work.How do i define a sysidcfg.erb that can handle multiple interfaces ?zone def : -- {noformat} zone { "test": name => "${zone_name}", ensure => "running", iptype => "shared", ip => [ 'ixgbe288000:10.17.24.101:10.17.24.1', 'ixgbe29:10.17.24.102:10.17.24.1', ], path => "/var/zones/test", sysidcfg => template('global_zone/sysidcfg.erb'),} {noformat} sysidcfg.erb :-- {noformat} system_locale=Ctimezone=Europe/Amsterdamterminal=vt100security_policy=NONEroot_password=Bn6s2d5MWIYhctimeserver=localhostname_service=NONEnetwork_interface=ixgbe288000:2 { hostname=<%= @zone_name %> ip_address=10.17.24.101 netmask=255.255.255.0 protocol_ipv6=no}network_interface=ixgbe29:3 { hostname=<%= @zone_name %> ip_address=10.17.26.101 netmask=255.255.255.0 protocol_ipv6=no}nfs4_domain=dynamic {noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-3193) No way to create a sysidcfg for a zone with multiple network interfaces
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-3193 No way to create a sysidcfg for a zone with multiple network interfaces Change By: Adrien Thebo Assignee: Kylo Ginsberg 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-3198) puppet module containing a PAXHeader fails to install on Solaris 11
Title: Message Title Adrien Thebo commented on PUP-3198 Re: puppet module containing a PAXHeader fails to install on Solaris 11 Thank you for reporting this. We believe this issue has already been addressed in a later release of Puppet. If you experience this issue against the current version of Puppet, please add a comment to this ticket with your reproduction scenario. For more info on getting the current version of Puppet Agent, see https://docs.puppet.com/puppet/latest/install_pre.html. 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-3199) requesting a catalog from an invalid environment barfs in a spectacular way
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3199 requesting a catalog from an invalid environment barfs in a spectacular way Change By: Adrien Thebo Affects Version/s: PUP 4.10.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.
