Ronie,
I have some new information see attachment for logging.
It appears traffic gets routed outside and recieves a invalid responce,
version 1.5.6-2ubuntu2 handles this well, version 1.5.6-2ubuntu2.3 breaks.
If I block traffic to 169.254.169.254 with ip tables facter works again.
Thanks!
**
Martijn,
Thanks for your help in getting to the bottom of this. As this appears
to be a network configuration issue on your system, I'm marking this bug
as Invalid. If you disagree, please explain and change back to New.
** Changed in: facter (Ubuntu)
Status: New = Invalid
--
You
I still think this is a bug since the old version doesn't have this
problem.
--
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:
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
root@it175:~# puppetd -t
info: Retrieving plugin
err: /File[/var/lib/puppet/lib]: Failed to retrieve current state of resource:
Could not retrieve information from source(s) puppet://puppet/plugins
err: Could not run Puppet configuration client: Could not retrieve local facts:
bad URI(is not
** Changed in: facter (Ubuntu)
Status: Incomplete = New
--
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
** Changed in: facter (Ubuntu)
Status: Triaged = Incomplete
--
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
Martijn-
The update in question repaired the ec2 fact to working order (it was
previously busted, and consequently skipped by facter+puppet altogether)
Strange though, something is clearly answering requests at that address
for the 'html' string to show up anywhere. The code checks that it
can
Hi,
Nothing running nor responding on 169.254.169.254 ping or wget time-outs.
Not running openstack, not running in a DC not running in a cloud.
Facter use to work until this update.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Martijn-
This is the expected behavior of the ec2 fact that ships with facter.
If it can connect to a webserver at http://169.254.169.254:80 (the
expected location of the meta-data server on Amazon EC2), it will
attempt to traverse the directory structure and populate facts with bits
of meta-data
Hi Martin
As Robie states this may be a regression due to bug 885998.
Please could you try running 'facter' with the updated package installed
and append the output to this bug report.
Hopefully this should allow us to dig into this issue futher.
Marking 'Incomplete' pending your response.
/usr/lib/ruby/1.8/uri/common.rb:436:in `split': bad URI(is not URI?):
http://169.254.169.254/2008-02-01/meta-data/html (URI::InvalidURIError)
from /usr/lib/ruby/1.8/uri/common.rb:485:in `parse'
from /usr/lib/ruby/1.8/open-uri.rb:29:in `open'
from
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This looks like a version of the regression introduced in bug 732953 and
fixed in bug 885998. However, others reported the regression fixed in
bug 885998.
** Changed in: facter (Ubuntu)
Importance: Undecided =
13 matches
Mail list logo
