[chef] Re: Re: Re: Re: knife ssh search results missing

[Cassiano Leal < >]

Seems like ec2.local_ipv4 was the culprit. I changed the attribute to ‘ipaddress’ and now all are accessible.

Thanks for the help!

--

Cassiano Leal

http://cassianoleal.com

http://twitter.com/cassianoleal

On July 22, 2013 at 15:46:01, Kevin Karwaski ( ) wrote:

Also, do all the instances have a valid value for 'ec2.local_ipv4'?
Are the security groups tuned correctly? Just thinking out loud...

On Mon, Jul 22, 2013 at 2:37 PM, Kevin Karwaski < > wrote:
> Hey Cassiano,
>
> Take a look at this:
>
> http://lists.opscode.com/sympa/arc/chef/2013-06/msg00354.html
>
> http://lists.opscode.com/sympa/arc/chef/2013-06/msg00363.html
>
> Andrew had a similar problem and it was related to the way VPCs handle
> address assignment. Maybe this doesn't apply to your particular
> configuration but If you're launching outside of US-EAST perhaps it's
> valid. Regardless, I hope it helps.
>
> -K.
>
> On Mon, Jul 22, 2013 at 2:27 PM, Cassiano Leal < > wrote:
>> Hi Kevin,
>>
>>
>> Neither attributes are set, but they shouldn’t make any difference. Yes, I’m
>> on EC2, inside a VPC (which is probably why both public attributes are
>> null).
>>
>>
>> I have
>>
>>
>> knife[:ssh_attribute] = 'ec2.local_ipv4’
>>
>>
>> on knife.rb so it uses that for connecting to the hosts.
>>
>>
>> I have tried setting it explicitly on the CLI as well:
>>
>>
>> $ knife ssh 'chef_environment:production' 'uptime' -a 'ec2.local_ipv4’
>>
>>
>> but no dice.
>>
>>
>> --
>> Cassiano Leal
>> http://cassianoleal.com
>> http://twitter.com/cassianoleal
>>
>> On July 22, 2013 at 15:12:12, Kevin Karwaski ( ) wrote:
>>
>> knife search 'chef_environment:production' -a ec2.public_hostname
>
>
>
> --
> Kevin Karwaski
> Manager, Cloud Operations @ {Fiksu}



--
Kevin Karwaski
Manager, Cloud Operations @ {Fiksu}