Red Hat Bugzilla – Bug 986511
remove rsyslog dependency
Last modified: 2015-07-27 06:39:01 EDT
All of this talk of removing rsyslog from the cloud image is moot when cloud-init is pulling it in. There's bug #953530 for EPEL; this one is for Fedora. I kinda think cloud-init's crazy-verbose multi-line logging is an example of something that would be better handled by the journal anyway.
The situation is the same as it is for EPEL: cloud-init depends on rsyslog for its /etc/rsyslog.d directory, per the packaging guidelines. It does not require rsyslog to be running, and as such, a spin may disable rsyslog if needed. Are we still doing conditional entries in comps? If so, then perhaps it might make sense to add a single-file cloud-init-rsyslog subpackage to @standard, contingent on cloud-init being installed. Then installs that pull in cloud-init and the rsyslog-using @standard will get the currently-expected behavior.
I don't know if that works in comps anymore. I'll check. I think it's kind of silly for a package to rely on an abstracted log interface (like syslog) and then also provide the configuration for that service in the same package. If the intent is to get cloud-init messages right into a specific file and nowhere else (which is the shipped config), why bother with going through syslog?
(In reply to Matthew Miller from comment #2) > I think it's kind of silly for a package to rely on an abstracted log > interface (like syslog) and then also provide the configuration for that > service in the same package. If the intent is to get cloud-init messages > right into a specific file and nowhere else (which is the shipped config), > why bother with going through syslog? The intent is the converse: to provide a default configuration when rsyslog happens to be the running syslog daemon. Unlike a built-in logging setup, this results in a setup that people can tweak to their liking with all of rsyslog's considerable power. Of course, the side effect of this is that if you're using a different syslog daemon you might experience different results. In that case, feel free to file a bug or submit a patch to add support for another syslogd.
(In reply to Garrett Holmstrom from comment #3) > The intent is the converse: to provide a default configuration when rsyslog > happens to be the running syslog daemon. Unlike a built-in logging setup, > this results in a setup that people can tweak to their liking with all of In that case, the conditional package makes sense. Or, alternately, actually getting this put into _rsyslog's_ default configuration.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
*** Bug 953530 has been marked as a duplicate of this bug. ***
cloud-init-0.7.5-8.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/cloud-init-0.7.5-8.fc21
Package cloud-init-0.7.5-8.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing cloud-init-0.7.5-8.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-14597/cloud-init-0.7.5-8.fc21 then log in and leave karma (feedback).
cloud-init-0.7.5-8.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1181844 has been marked as a duplicate of this bug. ***