Try setting the [:omnibus_updater][:cache_dir] to be different
(separate to where the Chef Server stuff is ending up.) Downloading to
/opt/chef*.deb seems bunk anyway.
IMNSHO, Do not use the Omnibus Updater cookbook and the included
attempt at porting the Omnitruck Client API Shell Script Installer to
Ruby. You’re only asking for trouble.
Use the ‘install.sh’ helper script from Opscode/ChefCo or ship and
install the packages directly (maybe an internal company repository).
I know Noah recently started hosting APT packages repository.
Do you love Chef? Do you hate curl | bash installations? Good news!
$ sudo apt-add-repository 'http://apt.poise.io chef-11'
$ sudo apt-key adv --keyserver hkp://pgp.mit.edu --recv 594F6D7656399B5C
$ sudo apt-get update
$ sudo apt-get install chef
$ chef-client --version
On Fri, Aug 15, 2014 at 9:04 PM, Steffen Gebert email@example.com wrote:
during the upgrade of our chef-server, I noticed a weird behavior: The
.deb file for the chef-server is downloaded during every chef run.
This is caused by omnibus_updater::old_package_cleaner removing all
chef*.deb files in the cache_dir .
The chef-server download also matches this pattern.
Can anybody recommend me a solution to avoid downloading the chef-server
over and over again?