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