[chef] Re: Re: Re: Re: Re: Re: toggling yum repos to enabled, disabled

[Joshua Timberman < >]

No worries, thanks for double checking!

On Fri, Apr 6, 2012 at 12:28 PM, John Alberts 
<
 >
 wrote:
> So.... apparently I was mistaken.  Something must have changed in
> these repository files when I was looking at them before, because now
> I can see everything is working like it's supposed to.  The repo files
> are not being regenerated each time like I thought.  Sorry for the
> extra noise on the mailing list.
>
> John
>
>
> On Fri, Apr 6, 2012 at 10:53 AM, John Alberts 
> <
 >
>  wrote:
>> Sure.  Working on that now.
>>
>> John
>>
>>
>> On Fri, Apr 6, 2012 at 10:29 AM, Joshua Timberman 
>> <
 >
>>  wrote:
>>> Hello!
>>>
>>> On Fri, Apr 6, 2012 at 8:07 AM, John Alberts 
>>> <
 >
>>>  wrote:
>>>> Well, I see now why the author of the yum cookbook decided to add that
>>>> unless statement.  If it's not there, the file is update every single
>>>> time, which of course then notifies the execute statement for running
>>>> yum makecache.  This obviously ends up wasting a lot of time for every
>>>> chef run.  I dont really understand why chef thinks the template has
>>>> changed therefore it thinks the file should be updated.
>>>> Is anyone else experiencing this if you have removed the 'unless
>>>> ::File.exists?("/etc/yum.repos.d/#{new_resource.repo_name}.repo")'
>>>> line from yum/providers/repository.rb?
>>>
>>> This smells like a bug. Can you open a ticket with debug log output
>>> from multiple runs? The whole log isn't required, just the relevant
>>> parts of a yum_repo resource getting configured.
>>>
>>> --
>>> Opscode, Inc
>>> Joshua Timberman, Technical Program Manager
>>> IRC, Skype, Twitter, Github: jtimberman
>>
>>
>>
>> --
>> John Alberts
>
>
>
> --
> John Alberts



-- 
Opscode, Inc
Joshua Timberman, Technical Program Manager
IRC, Skype, Twitter, Github: jtimberman