- From: Daniel DeLeo <
>
- To:
- Subject: [chef] Re: Re: chef-metal and chef search.
- Date: Wed, 22 Oct 2014 08:34:19 -0700
Is it possible that the first run doesn’t complete successfully?
--
Daniel DeLeo
On Wednesday, October 22, 2014 at 8:32 AM, John Keiser wrote:
>
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
>
<
>
>
(mailto:
)>
>
wrote:
>
> 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?
>
>
>
> Doug
Archive powered by MHonArc 2.6.16.