-
-
Notifications
You must be signed in to change notification settings - Fork 637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not use dpkg_autostart
for preventing Jenkins post install autostart
#594
Comments
Same here on Debian 8. This was added by @cheeseplus in commit: 36df55f. It's not clear to me from the commit message, what the actual issue was. I assume this avoids Jenkins starting up without our config / an additional restart of the |
The dkpg_autostart cookbook is broken on Chef 16, which in turn makes this one unusable on Chef 16 as well:
|
Hi. I know it's a bit overkill but we step into the following issue a couple of days ago:
Cookbook version
5.0
Chef-client version
Chef: 12.17.44
Platform Details
Ubuntu 16.04.2 LTS
Scenario:
Current version of Jenkins cookbook is using a
dpkg_autostart
cookbook that, in fact, creates a/usr/sbin/policy-rc.d
which breaks a default configuration of logrotate producing output to STDERR and makes cron ti send to us an alert each night when apostrotate
occur (e.g.rsyslog
)The
dpkg_autostart
cookbook wasn't updated for about 2 years. I'm not sure if it still compatible with e.g. Ubuntu 16.04Steps to Reproduce:
After installation from packages on ubuntu 16.04:
Expected Result:
Find another way to prevent Jenkins to autostart after installation or manually control
/usr/sbin/policy-rc.d
file with compatibility for Ubuntu 16.04.The text was updated successfully, but these errors were encountered: