[Bug 1257435] Re: Chef does not run with all install types

[Alexander Dupuy]

I'm not sure what the "upstream fix" is, but I am currently using cloud-
init to bootstrap chef-server on a cloud instance, and running chef-
client explicitly at the end of the omnibus installer (rather than
having to run it from runcmd module config) would make a hash of things,
as the chef configuration actually points to the instance itself as its
Chef server.  I need to install and configure the Chef server using the
chef-server-populator cookbook (and chef-solo) first, before I can run
chef-client.

So if the behavior of not running chef-client after the omnibus or
package installer changes, please at least provide some way to disable
that "feature".

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1257435

Title:
  Chef does not run with all install types

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1257435/+subscriptions