Hi,
Is there any chance you can backport your fix to lucid or integrate my patch
into lucid?
Please advise me.
David Lowes
On Mon, Oct 17, 2011 at 11:44 PM, Adam Gandelman
<email address hidden>wrote:
> Confirming that this bug still exists in natty (facter 1.5.8-2ubuntu2)
> but has since been fixed upstream. The issue exists in the
> "can_connect?" method and has little to do with the actual URL
> elsewhere, though changing the meta-data URL to use "/latest" instead of
> "/2008-02-01" provides a few more additional facts about network
> interfaces, security group and host names (as of today, at least).
>
> ** Changed in: facter (Ubuntu)
> Status: Fix Released => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/732953
>
> Title:
> can_connect function inside ec2.rb always return false
>
> Status in “facter” package in Ubuntu:
> Confirmed
>
> Bug description:
> 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.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/facter/+bug/732953/+subscriptions
>
Hi,
Is there any chance you can backport your fix to lucid or integrate my patch
into lucid?
Please advise me.
David Lowes
On Mon, Oct 17, 2011 at 11:44 PM, Adam Gandelman
<email address hidden>wrote:
> Confirming that this bug still exists in natty (facter 1.5.8-2ubuntu2) /bugs.launchpad .net/bugs/ 732953 :timeout( wait_sec) {open(ip, port)} :timeout( wait_sec) {open("http:// {port}/ latest/ meta-data" )} /bugs.launchpad .net/ubuntu/ +source/ facter/ +bug/732953/ +subscriptions
> but has since been fixed upstream. The issue exists in the
> "can_connect?" method and has little to do with the actual URL
> elsewhere, though changing the meta-data URL to use "/latest" instead of
> "/2008-02-01" provides a few more additional facts about network
> interfaces, security group and host names (as of today, at least).
>
> ** Changed in: facter (Ubuntu)
> Status: Fix Released => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> can_connect function inside ec2.rb always return false
>
> Status in “facter” package in Ubuntu:
> Confirmed
>
> Bug description:
> 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:
> After: Timeout:
> #{ip}:#
>
> After that change, the module seems to work properly in EC2 instances.
>
> To manage notifications about this bug go to:
> https:/
>