This message was deleted.
# puppet-enterprise
s
This message was deleted.
b
did you check if your primary has the class?
grep pe_repo /opt/puppetlabs/puppet/cache/state/classes.txt
on the primary
m
[root@puppet 2021.7.1]# grep pe_repo /opt/puppetlabs/puppet/cache/state/classes.txt pe_repo pe_repo:platform:debian_10_amd64 pe_repo:platform:debian_11_amd64 pe_repo:platform:el_8_x86_64 pe_repo:platform:ubuntu_2004_amd64 pe_repo:platform:windows_x86_64 pe_repo:platform:windowsfips_x86_64 pe_repo pe_repo::bulk_pluginsync pe_repo:platform:debian_10_amd64 pe_repo:platform:debian_11_amd64 pe_repo:platform:el_8_x86_64 pe_repo:platform:ubuntu_2004_amd64 pe_repo:platform:windows_x86_64 pe_repo:platform:windowsfips_x86_64
Yes the class is there, i can even see the files for el_8_x86_64 in /opt/puppetlabs/server/data/packages/public/2021.7.1
b
mhm
does the puppet agent run without errors on the primary?
and did you download the install script from the primary or a compiler?
m
Puppet agent on primary runs without errors, and the download was from primary, there is no compiler yet
We had to download it ignoring the proxy so we added --noproxy '*' to the curl
c
You'll need to fix the proxy so that it forwards traffic properly, or unset proxy configuration while
install.bash
runs. The
install.bash
script figures out which *NIX operating system it is running on, then calls
curl
again to download an OS-specific script that does most of the heavy lifting. If that download fails,
install.bash
assumes the reason is that the Puppet Server doesn't have the
pe_repo::platform
available.
m
Top! worked fine, unsetting proxy from root env and from /etc/environment was needed. Thanks alot. The removing from /etc/environment was the critical part which was used internally from the script