Found something about it (which hopefully solves my direct problem)
In my recipe I was passing variables { var => node["var"] } to the template.
It seems the mess appeared at this moment, using node attributes directly inside the template instead of converting to a var did solve my "nesting" problem.
Tensibai
Le 2012-11-22 09:22, Tensibai a écrit :
No one to help me about it ?
Forgot to say: chef server and client are in version 10.16.2-1
This nesting loop is quite annoying as it ends up that I can't edit node with webui and that I found incorrect entries in templates.
One more thing I don't understand: I'm not saving attributes within my recipe, so I can't see why it does "set" attributes on node.
Regards,
Tensibai
Le 2012-11-20 15:33, Tensibai a écrit :
Hi there,
I'm facing something strange and not understanding what's going on.I've attributes in cookbook, role and environment, when running the node attributes ends up with a "loop"where attributes are child in loop where they should not.
Here https://gist.github.com/4118081 is the gist of my env, role, cookbook attribute file and what a knife node edit looks like after a run.
Each run adds levels to the "loop".I'm not setting attributes within my recipes and I can't pinpoint where the problem resides.
I've tried to set env and role attributes in override instead of default with the same behavior.
If someone can help me :)
Regards,Tensibai
Archive powered by MHonArc 2.6.16.