- From: Zac Stevens <
>
- To:
- Cc:
- Subject: [chef] Re: search returns for nodes sometimes reduced or empty
- Date: Wed, 6 Jun 2012 15:30:28 +0100
Hi Dan,
On Wed, Jun 6, 2012 at 12:34 PM, Dan Adams
<
>
wrote:
>
1) Scenario 1 - Nodes vanish from search when I update chef via knife.
>
I make updates to files in the git repo and then import them to chef
>
couch/solr using:
>
"knife cookbook upload", "knife environment from file", "knife node from
>
file, "knife role from file"
>
It appears as though running at least some of these commands *re-creates*
>
the nodes as new objects with no roles (rather than updates the existing
>
objects) so that the nodes have no roles until the chef-client is
>
successfully run on the client host.
On this point, are you referring to the "roles" and "recipes" attributes?
These are updated during a chef-client run, in the process of taking
the run_list on the node and expanding it into the full set of recipes
and roles that will be applied.
So it's expected that the contents of those attributes will only
reflect a changed run_list after the next successful chef-client run.
I'm not sure whether it is considered correct for those attributes to
be blanked during "knife node from file" (if that is what's
happening).
Zac
Archive powered by MHonArc 2.6.16.