General discussion about Chef

[chef] Re: Re: Re: Re: Re: Re: Overriding node attributes


Chronological Thread 
  • From: Yonah Russ < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Re: Re: Overriding node attributes
  • Date: Tue, 19 Feb 2013 12:31:14 +0200
I don't know but I downgraded to 10.22 and the recipe worked as planned.
I've filed a bug report on chef client 11.2
FYI
Yonah

On Mon, Feb 18, 2013 at 10:19 PM, Jesse Campbell < " target="_blank"> > wrote:
Undefined node attribute makes me think perhaps the order of execution isn't what you're expecting, like maybe the ipfilter recipe is running first.

also double check what is inside blocks and what isn't (compile vs converge)... maybe put the ipfilter recipe stuff inside ruby_blocks


On Mon, Feb 18, 2013 at 2:36 PM, Sascha Bates < " target="_blank"> > wrote:
Is it possible that node.set is no longer an alias for node.default.set in a recipe?  I've been having some of my own struggles recently with attributes but I've always operated on the idea that you have to use .set in a recipe if the attr is not previously defined.

So the next thing I'd try is just node.default.set if you have not previously defined the attribute elsewhere.

Ok- no go on either suggestion.
Using .default had no effect and the second idea resulted in:
FATAL: NoMethodError: Undefined node attribute or method `push' on `node'

Any other ideas?
Yonah


could try this also perhaps:

node.set['ipf_rules'][i]['src_nets'].delete(src_net)




which chef version?

try node.default instead of node.set or node.override?

i think there is more to it but thats' what came to mind first.



Hi,




Archive powered by MHonArc 2.6.16.

§