Description of problem: Cloudinit has a requirement on rsyslog while it should be agnostic to the local syslog solution. Additional info: The specfile requires rsyslog and copy's a file to /etc/rsyslog.d/ so logging ends up in /var/log/cloud-init.log if you use syslog. I think configuring syslog should be up to the sysadmin, especially since there is more then one syslog implementation (we are using syslog-ng).
Note that while the cloud-init package requires the rsyslog package for its /etc/rsyslog.d directory, per the packaging guidelines, it does not require rsyslog to actually be running.
Although I'm not sure that we're ready to go to an all systemd-journal approach, some people might want to, and if they want to do that, they might want to not have rsyslog on their cloud images. Or, as above, use syslog-ng. Honestly I personally find a separate /var/log/cloud-init.log to be annoying, so I may not be speaking from the most unbiased place here. :)
I'm going to move this to Fedora, because I think we'll make the more "aggressive" changes there first, and it will trickle back to EPEL. One suggestion would be to make a cloud-init-rsyslog subpackage.
Let me try look into this and advice . Thanks.
I have tried to tinker around with this on my spare time. My opinion is we should probably try and keep it, but then also allow the admin to keep another copy where they please. That way we do not break it. What do you guys think?
*** This bug has been marked as a duplicate of bug 986511 ***