@ellayararwhy you can workaround this by setting the service provider to
systemd, like:
service 'example_service' do
provider Chef::Provider::Service::Systemd
action [:enable, :start]
end
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Easier said than done, seeing as AWS ubuntu 18.04 currently only has
support up to Chef 12.18.31. IOW, it's impossible to do an OpsWorks run
command that tries to do a update-rc.d -n ... (so much for no-ops)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
@jjudd
Consider using upstream Chef >= 14.1.1 instead of the Chef package from
the Ubuntu repository. Upstream Chef has Ubuntu 18.04 support.
https://docs.chef.io/release_notes.html#what-s-new-in-14-1-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
This issue was fixed in this commit in Chef. It's a 6 character diff.
https://github.com/chef/chef/commit/5320cbf9b41789a46a5c5c0a2d818966c9716405?diff=unified
#diff-8561ad40ccb208ff3c3f12bf88746df2
I'm not sure how to go about submitting a patch to a package in Ubuntu,
but I'll look into it.
--
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chef (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766786
Title:
chef
