[Bug 997641] Re: Could not run Puppet configuration client: Could not retrieve local facts: bad URI

[Robie Basak]

Martijn,

When I run the command, I get:

$ ruby -e "require 'open-uri'; require 'timeout'; Timeout::timeout(2) { open('http://169.254.169.254') }"
/usr/lib/ruby/1.8/timeout.rb:64:in `open': execution expired (Timeout::Error)
	from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'
	from /usr/lib/ruby/1.8/timeout.rb:53:in `timeout'
	from /usr/lib/ruby/1.8/timeout.rb:101:in `timeout'
	from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'
	from /usr/lib/ruby/1.8/net/http.rb:553:in `do_start'
	from /usr/lib/ruby/1.8/net/http.rb:542:in `start'
	from /usr/lib/ruby/1.8/open-uri.rb:242:in `open_http'
	from /usr/lib/ruby/1.8/open-uri.rb:616:in `buffer_open'
	from /usr/lib/ruby/1.8/open-uri.rb:164:in `open_loop'
	from /usr/lib/ruby/1.8/open-uri.rb:162:in `catch'
	from /usr/lib/ruby/1.8/open-uri.rb:162:in `open_loop'
	from /usr/lib/ruby/1.8/open-uri.rb:132:in `open_uri'
	from /usr/lib/ruby/1.8/open-uri.rb:518:in `open'
	from /usr/lib/ruby/1.8/open-uri.rb:30:in `open'
	from -e:1
	from -e:1

Evidently there's something different about your network environment
which is causing that URL to return something instead of timing out, and
this difference is the cause of your problem.

I don't think it is clear yet if this is a local configuration problem
or a genuine bug. To be able to determine this, we need to understand
exactly what this difference is.

I'm not sure what I can do to help at this stage, but I'll leave the bug
open in case anyone else has any ideas.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/997641

Title:
  Could not run Puppet configuration client: Could not retrieve local
  facts: bad URI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/997641/+subscriptions