The Chef server takes some time before it indexes a node–it’s not so much
that you need a second run, as that you need your run to wait long enough
for solr to index the node. If you are having this problem with local
mode, that’s a different issue–chef-client -z should have nodes show up in
search results instantly.
On Wed, Oct 22, 2014 at 8:10 AM, Douglas Garstang firstname.lastname@example.org
I’ve been using chef-metal for a few days, and I’ve noticed that after the
initial instance creation, and chef-client run (initiated by chef-metal),
that, in order for the new node to be available in chef search results, I
have to manually log in to the instance and run chef-client a second
time. Waiting a few minutes isn’t a substitute. Why is this required?