After Upgrade Nodes Managed by Chef But Not Present in "STATUS"


#1

Hello List!

I have a situation where I’ve migrated nodes over to an upgraded chef
server. It is managing them properly but the nodes will not show up in the
Status screen:

  • Upgrading from Chef 0.9 (chef1) to 0.10.8 (chef2)

  • I have imported all nodes, roles, cookbooks, data bags to chef2 server

  • client.rb has been reconfigured to use chef2, has new client.pem and is
    talking to and being managed by chef2
    ( I can edit the node, change run list, etc etc from chef2 )

  • BUT no matter what I do, I cannot make the node show up in the status
    screen (knife status -r or
    http://chef2:4040/statushttp://chef2.boats.local:4040/status shows
    no imported nodes, only nodes created originally with chef2)

Did I miss something?? Do I have to actually recreate the node from
scratch??

Appreciate any advice :slight_smile:

Thor



#2

On Tue, Apr 10, 2012 at 7:42 PM, Thor Newman
thor.newman@dominionmarinemedia.com wrote:

Appreciate any advice :slight_smile:

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

Bryan


#3

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 btm@loftninjas.org wrote:

On Tue, Apr 10, 2012 at 7:42 PM, Thor Newman
thor.newman@dominionmarinemedia.com wrote:

Appreciate any advice :slight_smile:

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
thor.newman@dominionmarinemedia.com


#4

Are you getting bit by this?

http://tickets.opscode.com/browse/CHEF-2346

When we went from .9 to .10, that one got us.


#5

Hi Bryan,

Yes that did it exactly. Thank-you very much.

List:

The problem was the new Chef 0.10.8 maxFieldLength default truncating data,
per the link supplied by Bryan: http://tickets.opscode.com/browse/CHEF-2346

Correction:

1) Change maxFieldLength from 10,000 to 100,000

perl -pi -e ‘s/<maxFieldLength>10000/<maxFieldLength>100000/g’
/var/lib/chef/solr/conf/solrconfig.xml

2) Restart Chef-Expander

/etc/init.d/chef-expander restart

This is a hard one to diagnose as there are no warnings that the data is
truncated.

Thor

On Wed, Apr 11, 2012 at 4:32 AM, Brian Akins brian@akins.org wrote:

Are you getting bit by this?

http://tickets.opscode.com/browse/CHEF-2346

When we went from .9 to .10, that one got us.


Thor Newman
Senior Analyst
Dominion Marine Media
(604)692-3206
thor.newman@dominionmarinemedia.com