Filing this bug on behalf of a presales email. Given the following information:
[root@enxi0003 ~]# head /etc/puppetlabs/puppet/puppet.conf
|
[main]
|
vardir = /var/opt/lib/pe-puppet
|
logdir = /var/log/pe-puppet
|
rundir = /var/run/pe-puppet
|
modulepath = /etc/puppetlabs/puppet/modules:/opt/puppet/share/puppet/modules
|
user = pe-puppet
|
group = pe-puppet
|
archive_files = true
|
archive_file_server = enxi0003.eagleaccess.com
|
http_proxy_host = proxy.domain.com
|
|
[root@enxi0003 ~]# puppet module install --verbose --debug puppetlabs-ntp
|
Preparing to install into /etc/puppetlabs/puppet/modules ...
|
Downloading from http://forge.puppetlabs.com ...
|
Error: Connection timed out - connect(2)
|
Error: Try 'puppet help module install' for usage
|
|
[root@proxy ~]# tail /var/log/squid/access.log
|
1341935727.031 122 10.60.99.93 TCP_MISS/200 1947 GET http://forge.puppetlabs.com/api/v1/releases.json? - DIRECT/74.207.228.89 application/json
|
It would appear that the PMT doesn't respect the http_proxy_host setting in puppet.conf. The customer also reported setting the HTTP_PROXY environment variable, but the PMT doesn't respect that either.