To elaborate on Noah's
point, 11.0 introduced an Erlang based depsolver for cookbooks. The
thinking was that this depsolver, while less robust, would be faster and
allow for easier installs of the server, since it didn't rely on
gecode. It was thought that the edge cases that gecode handled that the
Erlang depsolver didn't would only affect a few people. That was a bad
assumption. It turns out that many cookbooks have dependencies that are
hard to solve for and the Erlang depsolver wasn't up to the task, where
as gecode was. With the 11.1 release the server switched back to using
gecode. Noah is right that upgrade to at least 11.1 should help you out.
If you don't want to jump straight to 12, which is a more involved
upgrade process, you can upgrade to 11.1+ by installing the package and
then using the chef-server-ctl upgrade. http://docs.chef.io/open_source/upgrade_server_open_source.html Upgrading to 11.1+ will also help when you transition to 12, since the upgrade process to get to 12 is designed for 11.1+ and is known to not currently work with older versions of the server. The release notes for the 11.1 release are found here, for reference: http://docs.chef.io/release/osc_11-1/release_notes.html Also note I've assumed you're running the open source version of the server and that we're not talking about the enterprise version (with 12, these versions are one and the same). - Mark Mzyk " type="cite"> |
Archive powered by MHonArc 2.6.16.