Yes, I did execute the client run on the respective node. The output is after the successful execution of command.
‘role[mongodb]’ is the output of command.
From: Julian C. Dunn [mailto:email@example.com]
Sent: 06 May 2014 20:22
Subject: [chef] Re: RE: Re: knife node shows empty role
The roles attribute is only updated after a successful Chef Client run as it reflects the current state of the node. Did you run Chef between commands one and two?
Also, I believe you just need “knife node show xxxx -a roles” - don’t need the ‘role[mongodb]’ in there.
On Tue, May 6, 2014 at 9:24 AM, Aniket Sharad firstname.lastname@example.org wrote:
C:\Users\asharad\chef-repo>knife node run_list add xxxx ‘role[mongodb]’
C:\Users\asharad\chef-repo>knife node show xxxx ‘role[mongodb]’ -a
From: Aniket Sharad
Sent: 06 May 2014 18:40
Subject: RE: [chef] Re: knife node shows empty role
That’s what shows empty.
I had specified the roles in run list of the node and I see it empty
with the command you suggested. Do I need to update the role against
From: David Petzel [mailto:email@example.com]
Sent: 05 May 2014 18:19
Subject: [chef] Re: knife node shows empty role
I believe you want knife node show -a roles (lower case and plural)
On Sun, May 4, 2014 at 4:20 PM, firstname.lastname@example.org wrote:
A knife node show -a Role shows Roles attribute as empty, even though
a particular node has a role specified in its run list.
The funny thing is even after executing chef-client on the server;
still its node shows empty role.
Can someone please suggest if I am missing anything.
[ Julian C. Dunn email@example.com * Sorry, I’m ]
[ WWW: http://www.aquezada.com/staff/julian * only Web 1.0 ]
[ gopher://sdf.org/1/users/keymaker/ * compliant! ]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ]