** Description changed:
Binary package hint: facter
the can_connect function in ec2.rb always return false.
I modified the code as follows and it seems to have fixed the issue:
Before (Line 9 in ec2.rb): Timeout::timeout(wait_sec) {open(ip, port)}
After: Timeout::timeout(wait_sec)
{open("http://#{ip}:#{port}/latest/meta-data";)}
After that change, the module seems to work properly in EC2 instances.
+
+ ======
+ IMPACT:
+ * Any puppet configuration that relies on EC2 related facts will fail
entirely or fail to propagate the correct configuration on nodes running lucid,
maverick, and natty.
+
+ ADDRESSED:
+ * This was fixed upstream and in ubuntu as of oneiric. The proposed patch
fixes argument handling in a test of the ec2 metadata service.
+
+ REPRODUCE:
+ * Launch any AMI of an affected series, 'apt-get install facter' and 'facter
| grep ec2' should report none of the ec2 related facts.
+
+ REGRESSION POTENTIAL:
+ * The potential regression is minimal as the fix enables functionality that
was previously broken.
+ ======
--
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/732953
Title:
can_connect function inside ec2.rb always return false
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/732953/+subscriptions
--
Ubuntu-server-bugs mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
