[chef] Re: Re: Re: Re: Re: ohai 6.18 and 6.20 failing on ec2 hi1.xlarge

[Daniel DeLeo < >]

On Friday, December 13, 2013 at 11:38 AM, wrote:

After talking with AWS support, that URL now returns 200, and ohai and chef

works again (because node['ec2']['userdata'] no longer returns nil).

I'm wondering, if just one URI returns 404 to ohai, but all others don't, why is

the ohai result an empty Hash? By querying ec2 metadata by hand, I could see

all of what my recipes cared about. Is ohai all or nothing?

kallen

Most ohai plugins are written such that a single exception will fail the whole plugin, and ohai is currently designed to let plugins fail. Upcoming changes in ohai 7.0 will support specifying a set of required attributes, so if a plugin that provides those attributes fails, ohai will expose the error instead of swallowing it. This feature may not make it into 7.0.0, but the internal changes are in place for it already, so if the feature isn’t finished for 7.0.0 we’ll add it during the 7.x series.

-- 

Daniel DeLeo