[chef] Re: Re: After Upgrade Nodes Managed by Chef But Not Present in "STATUS"

[Thor Newman < >]

Hi Bryan

Thanks for your time.

Yep absolutely I have, and not only that:

 - I can see it talking to chef2 in the server log

 - if I cancel it's Client key in chef2 it can't authenticate (more proof its talking to right server)

 - I can run commands against it from chef2 like this:

knife ssh name:client1 'uptime'  or knife node edit client1 and change its runlist.

So its 100% certain talking to and being managed by the upgraded 'chef2' but is not showing up in Status

I'm worried it may be some kind of bug/issue migrating nodes from  0.9.16 to 0.10.8...

On Tue, Apr 10, 2012 at 5:04 PM, Bryan McLellan < "> > wrote:

On Tue, Apr 10, 2012 at 7:42 PM, Thor Newman
< "> > wrote:
> Appreciate any advice :)

Have you run chef-client on the node yet? This is needed to trigger
the indexer to index it.

Bryan

--

Thor Newman

Senior Analyst

Dominion Marine Media

(604)692-3206

" target="_blank">