Problem bootstrapping with chef vault

Chef Infra (archive)
1

Hi,

I am currently using knife bootstrap with the --bootstrap-vault-json
option. The problem I am having is that it intermittently (actually, quite
often) fails to add the new node to the vault, due to the delay in indexing
nodes, and then the run fails.

I am trying to think of ways around this. Previously an option would have
been bootstrapping with an empty runlist, then refreshing the vault, then
re-bootstrapping with the desired runlist (as in Joshua’s blog
http://jtimberman.housepub.org/blog/2013/09/10/managing-secrets-with-chef-vault/).
However, that won’t work because the second bootstrap (with recent chef
clients) resets the client pem.

Ideally I could add the specific node/client being bootstrapped to the
vault.

Any ideas?

Regards,
Christine

ThirdWave Insights, LLC I (512) 971-8727 <%28512%29%20656-7724> I
www.ThirdWaveInsights.com I P.O. Box 500134 I Austin, TX 78750

2

What version of the server are you on?

If you’re on CS 12.x, search uses Solr4 with a soft commit every 1s (by default). If you’re on CS 11.x, you can tune the solr commit time, but it might be worth upgrading so you can take advantage of the soft commit feature in Solr 4.

3

I’m using Hosted Chef, and chef client 12.5.1.

Regards,
Christine

4

Probably worth contacting Chef support for this one. I’d expect service degradation resulting in (drastic) index time increases to be more infrequent than what you apparently are experiencing.