[chef] Re: Re: Re: looks_like_ec2? fallback gist

[AJ Christensen < >]

Yo,

On 22 February 2012 09:32, Hedge Hog 
<
 >
 wrote:
> On Wed, Feb 22, 2012 at 2:58 AM, Bryan McLellan 
> <
 >
>  wrote:
>> On Tue, Feb 21, 2012 at 12:05 AM, Hedge Hog 
>> <
 >
>>  wrote:
>>> Ohai `looks_like_ec2?` seems to be on the blink in version 0.6.10 on a
>>> tiny ec2 instance (if the detail helps/matters it was launched via a
>>> stack template).
>>>
>>> Below is the gist I've been resorting to that has proved robust in
>>> these situations (0.6.4 was another occasion):
>>>
>>> https://gist.github.com/1873800
>>
>> I've been poking around that code as I've been discussing OHAI-310
>> [1]. How is it broken?
>
> looks_like_ec2? returns false/nil when it should return true.

I've been working on this bug a bit recently, it's specifically
related to instances launched in VPC -- VPC subnets do not have the
standard AWS ARP table entries.

As always, when helping with Chef diagnostics, it's great to supply
DEBUG level logs and/or the output of related commands, in this case,
I'd love to see the ohai debug output, and the arp table, from the
machine where looks_like_ec2 is failing.. *especially* if it is a
NON-VPC instance; as that would *NOT* be CHEF-310 but ANOTHER ec2
plugin bug.

>
> Given the moving target(s) your trying to hit I wonder if it isn't
> better to just say that people have to target a cloud VM by setting
> some attribute - it is not clear what that convention should be.
>
> looks_like_ec? whould then become looks_cloudy?, check for that
> attribute(s) and compose what information it can for that provider?
>
> This would be quite a change in behavior, but maybe could be
> implemented so that the attribute only need be set once, anywhere?
>
>> What happens?
>
> As above.  It don't see any exception.
>
>> Is there a bug for the issue
>> you're experiencing?
>
> Possibly, apologies for this but I don't really hunt in opscode's bug
> database too much anymore - from memory I do have an account (for a
> different role) I could use.  Simple reason is that, if you are
> serious about participating in squashing a bug, it is too frustrating
> to encounter this sort of thing[0], ironic that there is an example of
> this in the bug you cite.

What's the problem here? Link is dead, I assume it doesn't provide
anything useful to the bug. We know the cause of the problem and the
problematic code, all that remains is to design and develop a fix. The
bug has a valid, thorough description.

Patches to the problematic code in the official code base when tracked
per standard contribution policy is the best way to solve this -- not
gists floating around on a mailing list.

Cheers,

--AJ

>
> For the moment I find it suffices to google for people publishing
> gists/workarounds - just like this :)
>
> [0]: 
> http://tickets.opscode.com/browse/OHAI-310?focusedCommentId=21505&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-21505
>
>>
>> Bryan
>>
>> [1] http://tickets.opscode.com/browse/OHAI-310
>
>
>
> --
> πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
> [The fox knows many things, but the hedgehog knows one big thing.]
>   Archilochus, Greek poet (c. 680 BC – c. 645 BC)
> http://hedgehogshiatus.com