-
Notifications
You must be signed in to change notification settings - Fork 671
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
Remove support for upstart init system #9452
Remove support for upstart init system #9452
Conversation
None of the current products use upstart as the init system.
None of the current products use upstart as the init system.
Jinja conditionals on init_system were removed.
Jinja conditionals on init_system were removed.
This datastream diff is auto generated by the check Click here to see the full diffbash remediation for rule 'xccdf_org.ssgproject.content_rule_rsyslog_cron_logging' differs:
--- old datastream
+++ new datastream
@@ -6,7 +6,6 @@
echo "cron.* /var/log/cron" >> /etc/rsyslog.d/cron.conf
fi
-
systemctl restart rsyslog.service
else |
Code Climate has analyzed commit 399f578 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 42.3% (0.0% change). View more on Code Climate. |
The Automatus errors happen because the service enabled/disabled rules are not fit for testing in containers. |
/retest |
@yuumasato: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
I confirmed the failed tests were due to the test environment. Locally, in VMs, the rules passed. |
Description:
upstart
.Rationale:
upstart
at the moment.