[Bug 997641] Re: Could not run Puppet configuration client: Could not retrieve local facts: bad URI
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! ** Attachment added: facter logging https://bugs.launchpad.net/ubuntu/+source/facter/+bug/997641/+attachment/3245632/+files/facterissue -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997641] Re: Could not run Puppet configuration client: Could not retrieve local facts: bad URI
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 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997641] Re: Could not run Puppet configuration client: Could not retrieve local facts: bad URI
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: 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997641] Re: Could not run Puppet configuration client: Could not retrieve local facts: bad URI
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
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997641] Re: Could not run Puppet configuration client: Could not retrieve local facts: bad URI
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 URI?): http://169.254.169.254/2008-02-01/meta-data/html
root@it175:~# ruby -e require 'open-uri'; require 'timeout';
Timeout::timeout(2) { open('http://169.254.169.254') }
and it returns nothing so problem still excists.
--
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
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997641] Re: Could not run Puppet configuration client: Could not retrieve local facts: bad URI
** 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 retrieve local facts: bad URI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/997641/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997641] Re: Could not run Puppet configuration client: Could not retrieve local facts: bad URI
** 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 retrieve local facts: bad URI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/997641/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997641] Re: Could not run Puppet configuration client: Could not retrieve local facts: bad URI
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 connect to 169.254.169.254:80 before attempting to collect any data
from the server. I'm curious what the output is (if any) of running the
following command from one of the affected Puppet client nodes:
ruby -e require 'open-uri'; require 'timeout'; Timeout::timeout(2) {
open('http://169.254.169.254') }
Thanks
--
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
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997641] Re: Could not run Puppet configuration client: Could not retrieve local facts: bad URI
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 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997641] Re: Could not run Puppet configuration client: Could not retrieve local facts: bad URI
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 related to the instance. It seems like, in your case, there is something else serving requests at http://169.254.169.254/2008-02-01/meta-data, but instead of serving a directory structure its serving a HTML file. Facter is using each line of this file as possible directories to query, hence the InvalidURI exception from ruby when trying to connect to http://169.254.169.254/2008-02-01/meta-data/html (which is probably the first line of the HTML file being served) I'm curious to know about the environment you're running this in. Is this cloud infrastructure or a data center? Perhaps your firewall is redirecting all requests to 169.254.169.254 somewhere else? If this is Openstack. perhaps nova network is not properly forwarding requests to the meta-data service and they instead hit a webserver on the compute node? In any case, there is unfortunately no way to have puppet or facter avoid running certain facts contained within its configured fact library. One work around, if you do not need access to the related EC2 facts, is to remove that specific fact from your facter library directory: /usr/lib/ruby/1.8/facter/ec2.rb. Another option is to block outbound requests to 169.254.169.254 in a way that would cause an initial probe of port 80 to fail. ** Changed in: facter (Ubuntu) Status: New = Triaged -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997641] Re: Could not run Puppet configuration client: Could not retrieve local facts: bad URI
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. Please set back to 'New' once you have provided the requested information. Thanks ** Changed in: facter (Ubuntu) Status: New = 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 retrieve local facts: bad URI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/997641/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997641] Re: Could not run Puppet configuration client: Could not retrieve local facts: bad URI
/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 /usr/lib/ruby/1.8/facter/ec2.rb:24:in `metadata' from /usr/lib/ruby/1.8/facter/ec2.rb:20:in `each' from /usr/lib/ruby/1.8/facter/ec2.rb:20:in `metadata' from /usr/lib/ruby/1.8/facter/ec2.rb:36 from /usr/lib/ruby/1.8/facter/util/loader.rb:72:in `load' from /usr/lib/ruby/1.8/facter/util/loader.rb:72:in `load_file' from /usr/lib/ruby/1.8/facter/util/loader.rb:38:in `load_all' from /usr/lib/ruby/1.8/facter/util/loader.rb:33:in `each' from /usr/lib/ruby/1.8/facter/util/loader.rb:33:in `load_all' from /usr/lib/ruby/1.8/facter/util/loader.rb:30:in `each' from /usr/lib/ruby/1.8/facter/util/loader.rb:30:in `load_all' from /usr/lib/ruby/1.8/facter/util/collection.rb:94:in `load_all' from /usr/lib/ruby/1.8/facter.rb:91:in `to_hash' from /usr/bin/facter:138 ** 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 retrieve local facts: bad URI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/997641/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997641] Re: Could not run Puppet configuration client: Could not retrieve local facts: bad URI
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 = High -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
