Issue #15453 has been updated by Gary Larizza.
I'm going on his word as I've not setup a proxy to test this - so I'm
definitely interested in information to the contrary.
Having said that, I took a host with Puppet Enterprise running and tried a
`puppet module search apache` - everything worked properly. Then I set the
following in /etc/puppetlabs/puppet.conf:
<pre>
http_proxy_host = proxy.nobody.com
http_proxy_port = 1024
</pre>
Doing another search for the apache module shows this:
<pre>
[root@animal-centos ~]# puppet module search apache --debug --trace
Searching http://forge.puppetlabs.com ...
/opt/puppet/lib/ruby/1.8/net/http.rb:560:in `initialize'
/opt/puppet/lib/ruby/1.8/net/http.rb:560:in `open'
/opt/puppet/lib/ruby/1.8/net/http.rb:560:in `connect'
/opt/puppet/lib/ruby/1.8/timeout.rb:53:in `timeout'
/opt/puppet/lib/ruby/1.8/timeout.rb:101:in `timeout'
/opt/puppet/lib/ruby/1.8/net/http.rb:560:in `connect'
/opt/puppet/lib/ruby/1.8/net/http.rb:553:in `do_start'
/opt/puppet/lib/ruby/1.8/net/http.rb:542:in `start'
/opt/puppet/lib/ruby/1.8/net/http.rb:440:in `start'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/forge/repository.rb:67:in
`read_response'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/forge/repository.rb:61:in
`make_http_request'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/forge.rb:30:in `search'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/module_tool/applications/searcher.rb:11:in
`run'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/module_tool/applications/application.rb:11:in
`run'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/face/module/search.rb:26:in `search
implementation, required on Ruby 1.8'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/interface/action.rb+eval[wrapper]:207:in
`__send__'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/interface/action.rb+eval[wrapper]:207:in
`search'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/application/face_base.rb:242:in `send'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/application/face_base.rb:242:in `main'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/application.rb:317:in `run_command'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/application.rb:416:in `hook'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/application.rb:407:in `exit_on_fail'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'
/opt/puppet/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:69:in `execute'
/usr/local/bin/puppet:4
Error: Connection timed out - connect(2)
Error: Try 'puppet help module search' for usage
</pre>
So it looks like Ken is right here. I'll reach out to the customer again and
see if I can get a bit more information about his case.
----------------------------------------
Bug #15453: Puppet Module Tool should respect http proxies
https://projects.puppetlabs.com/issues/15453#change-66651
Author: Gary Larizza
Status: Needs More Information
Priority: Normal
Assignee:
Category: module tool
Target version:
Affected Puppet version:
Keywords: puppet module tool PMT proxy http_proxy
Branch:
Filing this bug on behalf of a presales email. Given the following information:
<pre>
> [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
</pre>
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.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
