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
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Looks like this has been fixed up stream, but there is no updated deb
for trusty
As a workaround, I have the cloud-init runcmd module executing chef-
client with cloud-init-per only running once per instance:
runcmd:
- [ cloud-init-per, instance, chef-bootstrap, chef-client ]
--
You received
This bug still exists, and is extremely frustrating!
--
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
+1 2C does not work here is the snippet im trying to make it work on
AWS EC2 with 2014.03 Amazon linux or on 2014.09 Amazon AMI linux (aka.
CentOS customized)
chef:
install_type: omnibus
force_install: false
omnibus_url: https://www.opscode.com/chef/install.sh;
environment: production
I'm yet
** Also affects: cloud-init
Importance: Undecided
Status: New
--
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
Sorry I missed the update to this issue.
In these listed cases, it would be 2C that does not run chef-client. By
default, the omnibus installer is simply there to install and setup
chef, not to execute it. It's still up to the user to do an initial
execution once everything has been configured
[Expired for cloud-init (Ubuntu) because there has been no activity for
60 days.]
** Changed in: cloud-init (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
It does seem that the bug you're reporting is valid. I'm not very familiar at
all with chef, though.
Had I looked at this code, I would have just expected that something would run
that automatically in the other install paths (packages or omnibus).
It really looks like we're expecting for the
10 matches
Mail list logo
