Bug 854654
Summary: | cloud-final systemd service missing console output | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Sergio Rubio <rubiojr> |
Component: | cloud-init | Assignee: | Garrett Holmstrom <gholms> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | gholms, Jan.van.Eldik |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-09-25 06:20:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sergio Rubio
2012-09-05 13:47:57 UTC
At first glance "syslog+console" doesn't seem like the right setting for this, given that cloud-init already logs to /var/log/cloud-init.log, so I'm leaning toward making it just "tty" instead. But then again perhaps it would make more sense to use "syslog+console", tweak cloud-init's own logging configuration so it logs only to syslog, and then ensure that the included rsyslog config file works properly. Would the latter break the way you're using cloud-init? Hey Garret, thanks for the input. It won't break anything for me (I can easily patch it in any case). The thing is that being able to see cloud-init messages while booting is a good thing IMO. You can easily fetch console output from AWS and OpenStack (nova console-log, ec2-get-console-output) and debug instance boot, monitor boot time, etc. I'd say it's a minor issue but a handy feature to have. The bug is about the cloud-final systemd service, but every cloud-init module that wants to print something while booting should be able to do that I guess. What do you think? Thanks! cloud-init-0.6.3-0.5.bzr532.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/cloud-init-0.6.3-0.5.bzr532.fc16 cloud-init-0.6.3-0.5.bzr532.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/cloud-init-0.6.3-0.5.bzr532.fc17 cloud-init-0.6.3-0.5.bzr532.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/cloud-init-0.6.3-0.5.bzr532.fc18 I think that's exactly what it's supposed to do. ;-) Feel free to give it a try now or when it hits testing. Package cloud-init-0.6.3-0.5.bzr532.fc18: * should fix your issue, * was pushed to the Fedora 18 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.6.3-0.5.bzr532.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-13972/cloud-init-0.6.3-0.5.bzr532.fc18 then log in and leave karma (feedback). cloud-init-0.6.3-0.5.bzr532.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. cloud-init-0.6.3-0.5.bzr532.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. cloud-init-0.6.3-0.5.bzr532.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |