Bug 1040536 - cloud kickstart: switch order of console kernel command line params to make log show up in openstack.
Summary: cloud kickstart: switch order of console kernel command line params to make l...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: spin-kickstarts
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeroen van Meeuwen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F20FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2013-12-11 15:22 UTC by Matthew Miller
Modified: 2013-12-13 05:35 UTC (History)
5 users (show)

Fixed In Version: spin-kickstarts-0.20.24-1.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-13 05:35:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Matthew Miller 2013-12-11 15:22:11 UTC
Right now, the system console goes to the virtual tty, not to the serial port. For openstack, it's desirable for this to be the other way around, so that the API calls which get the serial console give useful information rather than just initial boot output.

This change makes that happen:

diff --git a/fedora-cloud-base.ks b/fedora-cloud-base.ks
index 5e847e2..756b097 100644
--- a/fedora-cloud-base.ks
+++ b/fedora-cloud-base.ks
@@ -21,7 +21,7 @@ rootpw --lock --iscrypted locked
 
 firewall --disabled
 
-bootloader --timeout=1 --append="console=ttyS0,115200n8 console=tty0" extlinux
+bootloader --timeout=1 --append="console=tty1 console=ttyS0,115200n8" extlinux
 
 network --bootproto=dhcp --device=eth0 --onboot=on
 services --enabled=network,sshd,rsyslog,cloud-init,cloud-init-local,cloud-config,cloud-final

Comment 1 Matthew Miller 2013-12-11 15:47:11 UTC
I've tested this by editing the nightly F20 koji build with guestfish, and it works as desired with no bad effects. Also note that this _only_ affects environments which are booting with extlinux; Amazon EC2 uses pvgrub and therefore a different boot configuration.

Comment 2 Matthew Miller 2013-12-11 15:48:02 UTC
Asking permission to make this as a last-minute change. Sorry for being slow/late with this.

Comment 3 Mike Ruckman 2013-12-11 18:34:08 UTC
Discussed in 2013-12-11 Blocker Review Meeting [1]. Voted as an AcceptedFreezeException. This improves situation for cloud deployments and presents no risk to other products.

[1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-11/

Comment 4 Bruno Wolff III 2013-12-11 18:39:18 UTC
Matt can you tell me when your changes are all in the f20 branch? (I suspect they are already as I just saw a commit, but want to make sure before I start up the new spin-kickstarts build.)

Comment 5 Bruno Wolff III 2013-12-11 18:44:34 UTC
Nevermind, Adam did a cherry-pick and this should be ready for the next s-k build.

Comment 6 Fedora Update System 2013-12-11 19:17:25 UTC
spin-kickstarts-0.20.24-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/spin-kickstarts-0.20.24-1.fc20

Comment 7 Fedora Update System 2013-12-12 16:30:29 UTC
Package spin-kickstarts-0.20.24-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing spin-kickstarts-0.20.24-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-23254/spin-kickstarts-0.20.24-1.fc20
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2013-12-13 05:35:15 UTC
spin-kickstarts-0.20.24-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.