I want to get a node list with role[os-controller] in it’s run list, so I
tried “knife search” command at my chef server CML however I got a weird
result as follow:
In my understanding, chef server should only return one node info with role[os-controller] (here is centos-10-145-88-152), but it return two
nodes. I have no idea how to figure it out.
If someone can point it out, it will be much appreciated.
chef saves a two computed attributes, aka recipes and roles as part of run
list expansion. so, you want to search against 'roles:foo' (plural).
also some thing in your recipes sets an attribute (may be nested) 'role' ,
which might explains the first hit.
something like:
node[:a][:role] = 1,
I want to get a node list with role[os-controller] in it's run list, so I
tried "knife search" command at my chef server CML however I got a weird
result as follow:
In my understanding, chef server should only return one node info with role[os-controller] (here is centos-10-145-88-152), but it return two
nodes. I have no idea how to figure it out.
If someone can point it out, it will be much appreciated.
chef saves a two computed attributes, aka recipes and roles as part of run
list expansion. so, you want to search against 'roles:foo' (plural).
also some thing in your recipes sets an attribute (may be nested) 'role' ,
which might explains the first hit.
something like:
node[:a][:role] = 1,
I want to get a node list with role[os-controller] in it's run list, so I
tried "knife search" command at my chef server CML however I got a weird
result as follow:
In my understanding, chef server should only return one node info with role[os-controller] (here is centos-10-145-88-152), but it return
two nodes. I have no idea how to figure it out.
If someone can point it out, it will be much appreciated.
chef saves a two computed attributes, aka recipes and roles as part of
run list expansion. so, you want to search against 'roles:foo' (plural).
also some thing in your recipes sets an attribute (may be nested) 'role'
, which might explains the first hit.
something like:
node[:a][:role] = 1,
I want to get a node list with role[os-controller] in it's run list, so
I tried "knife search" command at my chef server CML however I got a weird
result as follow:
In my understanding, chef server should only return one node info with role[os-controller] (here is centos-10-145-88-152), but it return
two nodes. I have no idea how to figure it out.
If someone can point it out, it will be much appreciated.
chef saves a two computed attributes, aka recipes and roles as part of
run list expansion. so, you want to search against 'roles:foo' (plural).
also some thing in your recipes sets an attribute (may be nested) 'role'
, which might explains the first hit.
something like:
node[:a][:role] = 1,
I want to get a node list with role[os-controller] in it's run list, so
I tried "knife search" command at my chef server CML however I got a weird
result as follow:
In my understanding, chef server should only return one node info with role[os-controller] (here is centos-10-145-88-152), but it return
two nodes. I have no idea how to figure it out.
If someone can point it out, it will be much appreciated.
*[root@chefsrv ~]# knife search node 'roles:os-controller'0 items
found[root@chefsrv ~]# *
When I tried the command as below, I can get my ideal result:
chef saves a two computed attributes, aka recipes and roles as part of
run list expansion. so, you want to search against 'roles:foo' (plural).
also some thing in your recipes sets an attribute (may be nested)
'role' , which might explains the first hit.
something like:
node[:a][:role] = 1,
I want to get a node list with role[os-controller] in it's run list,
so I tried "knife search" command at my chef server CML however I got a
weird result as follow:
In my understanding, chef server should only return one node info with role[os-controller] (here is centos-10-145-88-152), but it return
two nodes. I have no idea how to figure it out.
If someone can point it out, it will be much appreciated.
*[root@chefsrv ~]# knife search node 'roles:os-controller' 0 items
found[root@chefsrv ~]# *
When I tried the command as below, I can get my ideal result:
chef saves a two computed attributes, aka recipes and roles as part of
run list expansion. so, you want to search against 'roles:foo' (plural).
also some thing in your recipes sets an attribute (may be nested)
'role' , which might explains the first hit.
something like:
node[:a][:role] = 1,
I want to get a node list with role[os-controller] in it's run list,
so I tried "knife search" command at my chef server CML however I got a
weird result as follow:
In my understanding, chef server should only return one node info
with role[os-controller] (here is centos-10-145-88-152), but it
return two nodes. I have no idea how to figure it out.
If someone can point it out, it will be much appreciated.