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 I'm considering expanding this issue to cover all network transient failures in the Cisco NX vm pooler image. Frequently SCP fails as well. On a recent scp failure, I found these messages in the bottom of the dmesg: [ 385.394869] _local_bh_enable_ip: cpu:2 Bottom half held between start-6860787165720 end-6860811783828 [ 385.394896] [ 385.394896] _local_bh_enable_ip:cpu-2 Bottom half held for 24 msecs disable_ip=_raw_spin_lock_bh+0x16/0x40 enable_ip=mts_sys_recv+0x527/0x1520 [klm_mts] 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 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-7845) Support leaf certificate CRL checking
Title: Message Title Eric Delaney assigned an issue to Adrien Thebo Puppet / PUP-7845 Support leaf certificate CRL checking Change By: Eric Delaney 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-4708) Refresh Windows Environment Variables during run
Title: Message Title
Ian Ellis commented on PUP-4708
Re: Refresh Windows Environment Variables during run
Thomas Kishel could you do this?
Package { provider => 'chocolatey' }
package { 'python3':
ensure => '3.6.2',
require => Package['chocolatey'],
}
exec { 'refresh env':
command => 'c:\programdata\chocolatey\bin\refreshenv.cmd',
require => Package['python3']
Jira (PDB-3687) ordering on fact value
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3687 ordering on fact value Issue Type: Bug Assignee: Unassigned Created: 2017/09/22 2:03 PM Priority: Normal Reporter: Wyatt Alt Users should be able to order facts and fact-contents by value. This should result in a lexicographical ordering on coalesce(value_string, value_integer, value_float, ... ). See https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/puppet-users/qF3BChrwRuU/Yl4OcwYEBAAJ for recent discussion. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7983) Test puppet-agent built against system openssl in PA CI pipes
Title: Message Title Jayant Sane created an issue Puppet / PUP-7983 Test puppet-agent built against system openssl in PA CI pipes Issue Type: Bug Assignee: Jayant Sane Created: 2017/09/22 1:43 PM Priority: Normal Reporter: Jayant Sane Testing PA built against system openssl thru CI has turned into quite a non-trivial exercise. First attempt resulted in some tests failing on the master host that CI sets up. Ironically, such agents have been able to get their certificate signed by the master fine when setup manually. That led to reproducing the failure using beaker locally. Testing using beaker led to a different failure during the pre-suite/setup step of PA acceptance tests. Managed to overcome that by customizing pre-suite scripts in puppet. Now need to use this custom version of puppet when launching CI. Lets see how long this goes on... All to get a PA CI test passing certificate to be able to submit PR in puppet to enable building against system openssl. Add Comment
Jira (FACT-1762) valid networking facts in 3.x get ignored in 4.x
Title: Message Title Thomas J Miller jr created an issue Facter / FACT-1762 valid networking facts in 3.x get ignored in 4.x Issue Type: Bug Assignee: Unassigned Created: 2017/09/22 1:37 PM Environment: Any Priority: Minor Reporter: Thomas J Miller jr Certain hiera entries which rely on calling Facter to fill values in PE 3.8 fail miserably in PE 4.8.1. We traced it to a behavior in Facter. Specifically, we found that calling the fact key of "ipaddress_eth0_1" used to return a good value in 3.8, but now returns a blank in 4.8.1. However, I have discovered that calling ipaddress_eth0:1 in 4.8.1 does work. I was not aware of this change until one of my teams and I found out the hard way. To test locally, one only needs to do this (as root, on any Linux server with bonding set up): facter ipaddress_bond0_1 (this should return a blank in 4.8.1, yet return the ip address value of bond0:1 in 3.8) facter ipaddress_bond0:1 (this should return an ip address that corresponds to bond0:1, and this is the workaround we put into the hiera .yaml file.) (There may be
Jira (FACT-1642) facter should understand cpu model on Power for the processors.model fact
Title: Message Title Casey Williams assigned an issue to Enis Inan Facter / FACT-1642 facter should understand cpu model on Power for the processors.model fact Change By: Casey Williams Assignee: Casey Williams Enis Inan 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 created an issue PuppetDB / PDB-3686 PDB migration error due to facts deduplication and null values Issue Type: Bug Assignee: Unassigned Created: 2017/09/22 10:56 AM Priority: Major Reporter: Jeff Yarnell [4:14 PM] Russell Mull: there's two different ways that null is represented in the ops facts table [4:14 PM] Russell Mull: both have the correct null type [4:14 PM] Russell Mull: (4) [4:14 PM] Russell Mull: but one of them has the json string "null" as its value [4:14 PM] Russell Mull: and the other has the value set to sql null [4:15 PM] Russell Mull: when we recompute value hashes as part of the redupe migration, we unify the two [4:15 PM] Russell Mull: so they hash to the same thing [4:15 PM] Russell Mull: which is nearly always what we want; but in this case, because they're inhabiting two rows, it turns into a conflict Add Comment
Jira (FACT-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result
Title: Message Title Branan Riley commented on FACT-1284 Re: Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result Jakob For this ticket we just implemented $? for compatibility with Facter 2. Given how weird that is internally in Ruby, I agree it'd be worthwhile to expose a cleaner API that's more testable. Unfortunately the return of execute right now is just the output of the executed command, so we don't really have a good extension point. We'd likely have to introduce a new API that can return the additional data. Do you mind filing a separate ticket for that feature request? Regarding the documentation, a bit more information about what you find misleading would be helpful so we can correct it. 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 Casey Williams Facter / FACT-1642 facter should understand cpu model on Power for the processors.model fact Change By: Geoff Nichols Assignee: Enis Inan Casey Williams 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-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result
Title: Message Title Michael Smith assigned an issue to Branan Riley Facter / FACT-1284 Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result Change By: Michael Smith Assignee: 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 (FACT-1760) test for "java_version" fails for "other systems" when java is not installed
Title: Message Title Michael Smith commented on FACT-1760 Re: test for "java_version" fails for "other systems" when java is not installed I'm not sure why this is a FACT ticket. It looks like it's a simple modules test fix, which should go in the MODULES project (or even just be a (maint) PR). 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-7882) lookup() function: set a kind of default value which is merged
Title: Message Title Henrik Lindberg commented on PUP-7882 Re: lookup() function: set a kind of default value which is merged Francois Lafont I am sorry, I probably do not understand what it is you are trying to do or why that is desirable. 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 Eric Delaney updated an issue Puppet / PUP-7955 Update puppet to use the rubocop 0.49 or greater Change By: Eric Delaney Sprint: Platform Core Grooming 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 Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-7955 Update puppet to use the rubocop 0.49 or greater Change By: Eric Delaney Assignee: Eric Delaney 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-7970) Acceptance: Automate testing of i18n locale detection
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-7970 Acceptance: Automate testing of i18n locale detection Change By: Eric Delaney Assignee: Eric Delaney 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 Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-7845 Support leaf certificate CRL checking Change By: Eric Delaney Assignee: Eric Delaney 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-7982) pip provider package install loop
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-7982 pip provider package install loop Change By: Charlie Sharpsteen Method Found: Customer Feedback 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-7982) pip provider package install loop
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-7982 pip provider package install loop Change By: Charlie Sharpsteen CS Priority: Major Needs Priority CS Frequency: 1 - 1-5% of Customers 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-7982) pip provider package install loop
Title: Message Title Charlie Sharpsteen commented on PUP-7982 Re: pip provider package install loop Moving to PUP since this affects a core Puppet provider and not software that is only found in Puppet Enterprise. 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-7982) pip provider package install loop
Title: Message Title Charlie Sharpsteen moved an issue Puppet / PUP-7982 pip provider package install loop Change By: Charlie Sharpsteen Affects Version/s: PE 2016.4.0 Affects Version/s: PUP 4.10.8 Key: ENTERPRISE PUP - 1094 7982 Project: Puppet Enterprise 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 Thomas Hallgren 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-6854) OSX: Warning output when using puppet resource service
Title: Message Title Jeremy Green commented on PUP-6854 Re: OSX: Warning output when using puppet resource service This bug means it's not possible to use puppet to manage services on mac OS Sierra without getting an unreadably-large number of warnings in the output of puppet apply. 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 created an issue Puppet / PUP-7981 Puppet extension for Linux disappeared from Azure Issue Type: Bug Assignee: Unassigned Created: 2017/09/22 7:10 AM Priority: Major Reporter: Kevin Reeuwijk It seems there has been some sort of regression around the Puppet extensions in Azure. The Puppet Agent extension for Linux has disappeared altogether, and the Puppet Agent extension for Windows is listed as "(Preview)" and has the following in it's description: "Additionally, you can extend automation to several key Windows functions, including the Windows Registry, IIS and PowerShell using modules available on the Puppet Forge, a repository of over 2,000 modules contributed by the Puppet community." Only 2000?? This looks like a description that's many years old... The main issue however is that for Linux users on Azure it looks like Chef is supported but Puppet is not! Please contact Microsoft and have them fix this! Add Comment
Jira (PUP-7882) lookup() function: set a kind of default value which is merged
Title: Message Title Francois Lafont commented on PUP-7882 Re: lookup() function: set a kind of default value which is merged Hi, @Henrik Lindberg: Ok, but I absolutely don't see how it's possible to do the same with lookup() etc. Is it possible to have explanations? The default value is never merged with the lookup() function, so I don't see any solution. 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-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result
Title: Message Title Jakob commented on FACT-1284 Re: Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result So, what happened here? There's still no reasonable way to get the exit code, $? and $CHILD_STATUS are difficult (impossible?) to stub in tests, and the documentation for :on_fail is misleading. 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-7882) lookup() function: set a kind of default value which is merged
Title: Message Title Henrik Lindberg commented on PUP-7882 Re: lookup() function: set a kind of default value which is merged Closing this because I think you can do the same using existing functions (lookup + deep_merge). 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 created an issue Facter / FACT-1761 Infiniband's mac (hardware) address not provided Issue Type: Bug Affects Versions: FACT 3.6.7 Assignee: Unassigned Created: 2017/09/22 3:04 AM Environment: CentOS 7.4 (but I believe the distro is not relevant) an Infiniband device activated IPoIB Labels: infiniband mac Priority: Normal Reporter: Radosław Piliszek How to reproduce > facter The problem Facter does not include the mac (hardware) address of
Jira (FACT-1760) test for "java_version" fails for "other systems" when java is not installed
Title: Message Title Sebastian Huebner commented on FACT-1760 Re: test for "java_version" fails for "other systems" when java is not installed Pull request: https://github.com/puppetlabs/puppetlabs-java/pull/258 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-1760) test for "java_version" fails for "other systems" when java is not installed
Title: Message Title Sebastian Huebner created an issue Facter / FACT-1760 test for "java_version" fails for "other systems" when java is not installed Issue Type: Bug Affects Versions: FACT 3.9.0 Assignee: Unassigned Created: 2017/09/22 2:27 AM Environment: Tested on Debian 9.1, but should fail on every OS besides OpenBSD and Darwin Priority: Normal Reporter: Sebastian Huebner The test for "java_version" fails for "other systems" (i.e., everything besides OpenBSD and Darwin) when java is not installed: Facter::Util::Fact java_version
Jira (PUP-7979) Add a run_command() function
Title: Message Title Henrik Lindberg moved an issue Puppet / PUP-7979 Add a run_command() function Change By: Henrik Lindberg Key: BOLT PUP - 38 7979 Project: Puppet Task Runner 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-7967) Add a file_upload() function
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7967 Add a file_upload() function Change By: Henrik Lindberg Assignee: Henrik Lindberg 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 Henrik Lindberg updated an issue Puppet / PUP-7979 Add a run_command() function Change By: Henrik Lindberg Sprint: Tasks ELP EUP (PuppetConf) 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 Henrik Lindberg moved an issue Puppet / PUP-7980 Add a run_script() function to enable this bolt feature from the language Change By: Henrik Lindberg Key: BOLT PUP - 92 7980 Project: Puppet Task Runner 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.
