[chef] yum cookbook and proxies


Chronological Thread 
  • From: "Geoff O'Callaghan" < >
  • To:
  • Subject: [chef] yum cookbook and proxies
  • Date: Mon, 27 Jan 2014 18:20:41 +1100

Hi All,  

This is probably a newb misunderstanding on my behalf but this is my issue.

I'm using the latest open source chef server / chef-client  on centos 6.5.
I have the latest yum cookbook - version 3.0.4
The cookbook attributes has   default['yum']['main']['proxy'] = nil # /.*/ 
I have a role that sets yum/main/proxy to my http proxy and I can see the attribute for  my node within the webui.   And now for the issue.

proxy doesn't get set in my /etc/yum.conf *unless* I update recipes/default.rb to include
  proxy node['yum']['main']['proxy']   as well

The same applies to any of the attributes appearing in yum.conf.    I was expecting the behavior that if I set the attribute on something that makes it to the node attributes  then  it would make the required change.

Is it meant to work this way?   Feel free to slap me in the right direction

Tks Geoff



Archive powered by MHonArc 2.6.16.

§