[chef] Re: Re: Node Role isn't updated

[Sascha Bates < >]

I'd like to know if this worked. I thought one of the Chef 11 updates was that they were automatically doing that now.  But I agree this sounds like the classic node data and solr limits.

John E. Vincent (lusis) wrote:

" type="cite">

This. When dealing with windows nodes just be preemptive and bump the solr settings or you're gonna have a bad time.

On Jun 30, 2013 4:26 PM, "Peter Donald" < "> > wrote:

Hi,

On Monday, July 1, 2013, Michael L. wrote:

Hi,
I am deploying a windows node with Chef (for the first time I use windows OS with Chef).
All goes well beside one thing:

1. The windows machine has chef client and successfully runs it.
2. I see the windows node amongst other nodes in chef server.
3. I see that the windows machine has the proper "role" name (converter) in its run list.

The major problem is when I am trying to search the nodes under this role name I get empty list:

$ knife search node "roles:converter"
0 items found

 

My guess is that the windows node is producing too much ohai data and is thus silently failing to be indexed and if that is the case then no search will return the node. To fix this you can disable ohai plugins from the node, remove ohai data explicitly at the end of chef run or update the indexer to handle the larger size.

For the last one search in the sole config file (sole-config.xml iirc) and look for value for maxKeysize or similar - it will be 10000 - add an extra 0 in. Sorry for being less specific but I am away from my laptop.

--
Cheers,

Peter Donald