[Puppet Users] Bad security pratices in manifests

Hello everyone! Recently, I've found an academic research about bad coding practices in manifests which can lead to security issues. I found it interesting, but I notice that the practices that the researchers pointed out aren't specific to Puppet nor even to infrastructure as code applications.

[Puppet Users] Bad security practices in manifests

Hello everyone! Recently, I've found an academic research about bad coding practices in manifests which can lead to security issues. I found it interesting, but I notice that the practices that the researchers pointed out aren't specific to Puppet nor even to infrastructure as code applications.

Re: [Puppet Users] Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'quick_check'

It maybe because of a long environment timeout: https://puppet.com/docs/puppet/5.5/environments_creating.html#task-3930 In PE this is set to unlimited by default when using code management. The code manager will then manually evict the cache after a code deployment to ensure that new code is viewab

[Puppet Users] Fwd: Facter 4.0.30 is now available

Hello, The Facter team is happy to announce the release of Facter 4.0.30 Here is what changed: Added - (FACT-2690) Add Hyper-V fact for Linux #1968 - (FACT-2694) Add linux openvz fact #1

[Puppet Users] Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'quick_check'

I've reviewed sever 500 error posts in here but the answers seem to differ based on the situation. One of our developers modified code to include a parameter available in httpfile 0.1.9 called quick_check. We have two installation of puppetserver one in lab domain and one in production do

Re: [Puppet Users] undefined method platform for nil:NilClass since puppetserver upgrade

Hi Andy, I haven’t seen this before, but I have a thought. Have you tried removing the new line at the end so the closing of the package resource collector isn’t on a new line? Similar to this? if("${rhsmtrue}" and $::operatingsystem == 'RedHat'){ Rhsm_register <| |> -> Yumrepo <| |> -

Re: [Puppet Users] unable to access the puppet status API after upgrade the PE from 2019.1.0 to 2019.5.0

Hi Rebecca, As per the link, issue got resolved in 2019.5 version. But getting the 502 bad gateway error while accessing the status API. wget http://:8123/status/v1/services --2020-07-16 13:35:44-- http://:8123/status/v1/services Resolving ()... 127.0.1.1 Connecting to ()|127.0.1.1|:8123... co

Re: [Puppet Users] unable to access the puppet status API after upgrade the PE from 2019.1.0 to 2019.5.0

Hi Vinay, This might help. https://puppet.com/docs/pe/2019.5/release_notes_pe.html#resolved_issues_pe_x-5 Since this is Puppet Enterprise, you can reach out to support at https://support.puppet.com On Thu, Jul 16, 2020, 7:16 AM Vinay Korrapati wrote: > Hi Rebecca, > > Thanks for your respons

Re: [Puppet Users] unable to access the puppet status API after upgrade the PE from 2019.1.0 to 2019.5.0

Hi Rebecca, Thanks for your response. Do we have any workaround or fix for this issue ? Regards Vinay On Thursday, July 16, 2020 at 5:30:31 PM UTC+5:30, Rebecca Robinson wrote: > > Hi Vinay, > > Since this is PE, I would open a ticket with support. I do believe that > was changed due to the fo

Re: [Puppet Users] unable to access the puppet status API after upgrade the PE from 2019.1.0 to 2019.5.0

Hi Vinay, Since this is PE, I would open a ticket with support. I do believe that was changed due to the following reasons and docs may also need to be updated. https://puppet.com/security/cve/CVE-2020-7943/ Regards, Becca On Thu, Jul 16, 2020, 6:50 AM Vinay Korrapati wrote: > Hi Team, > > w

[Puppet Users] unable to access the puppet status API after upgrade the PE from 2019.1.0 to 2019.5.0

Hi Team, we are unable to access the puppet status API after upgrade the PE from 2019.1.0 to 2019.5.0. uri: http://:8123/status/v1/services getting: 502 bad gateway. Port is opened and In PE Console node group, in the puppet_enterprise::profile::console class, console_services_plaintext_st

[Puppet Users] undefined method platform for nil:NilClass since puppetserver upgrade

hey there I recently update puppetserver to 6.12.1 ( along with puppetdb to 6.11.2 and puppet-agent to 6.17.0 ) and occasionally on some puppet runs ( I cannot determine why it happens sometimes and not others ) we see the following reported... Error while evaluating a Virtual Query, undefined met