Apparently the "upstream fix" is here, made in 1024.1.16 (http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/1024.1.16), which creates a new chef module config key 'exec' that can be explicitly set to true to enable Chef run after install (defaults to true for gem installs only). So my concern in previous comment is fully addressed, and I won't have any problems.
-- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
