This message was deleted.
# puppet-enterprises
Slackbot
02/07/2023, 11:33 AMThis message was deleted.
g
Gareth McGrillan
02/07/2023, 11:38 AMI had a case a while back whereby the umask was set at 0077 at some point causing a very similar error.
n
n3snah
02/07/2023, 11:39 AMinteresting you say that. We set the umask to 022, for CIS compliance.
n3snah
02/07/2023, 11:41 AMI don't believe I have a token issue because I have tried with an invalid token and it gives a different error
n3snah
02/07/2023, 11:50 AMThink I fixed it.
n3snah
02/07/2023, 11:51 AMit was a Umask issue 😠, There was 4 files in this directory
/opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/specifications/👍 1
c
csharpsteen
02/07/2023, 3:12 PM022 should be fine, but 027 or higher might cause problems.
👍 1
n
n3snah
02/07/2023, 4:15 PMThis isn't the first time CIS has broken Puppet upgrades for me though 😞
6 Views