Red Hat Bugzilla – Full Text Bug Listing
|Summary:||initial-setup-text.service does not run on console|
|Product:||[Fedora] Fedora||Reporter:||Paul Whalen <pwhalen>|
|Component:||initial-setup||Assignee:||Vratislav Podzimek <vpodzime>|
|Status:||CLOSED ERRATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||20||CC:||awilliam, dennis, greearb, kparal, pschindl, robatino, vpodzime|
|Fixed In Version:||initial-setup-0.3.7-1||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2013-09-18 11:12:15 EDT||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
|Bug Blocks:||245418, 980650, 980651|
Description Paul Whalen 2013-06-27 16:02:13 EDT
Description of problem: ARM uses various consoles for each hardware platform, currently initial-setup-text is only run on ttys0 Version-Release number of selected component (if applicable): initial-setup-0.3.6-2.fc19 How reproducible: Everytime. Steps to Reproduce: 1. Attempt to boot hw that uses tty02 - OMAP hw Actual results: initial-setup does not run. Expected results: initial-setup is run at boot on whatever console is in use. Additional info:
Comment 1 Dennis Gilmore 2013-06-27 16:43:23 EDT
on investigation /usr/lib/systemd/system/initial-setup-text.service has in it Before=display-manager.service firstname.lastname@example.org serial-getty@ttyS0.service at the least we need to add serial-getty@ttyO0.service serial-getty@ttyO2.service serial-getty@ttyAMA0.service probably should be getty@ttyUSB0.service also off the top of my head are different serial console devices in use out there. it seems like systemd perhaps should provide a serial-console.service or some such that would provide for all serial console device names out there.
Comment 2 Dennis Gilmore 2013-06-29 09:45:21 EDT
ttymxc0 is another valid serial console device
Comment 3 Dennis Gilmore 2013-08-06 23:11:18 EDT
Ping, we really need a good answer for f20, time is already short
Comment 4 Dennis Gilmore 2013-08-06 23:19:27 EDT
Setting to block F20 Alpha, While the image effected is the minimal image it is probably the most commonly deployed image. The criteria I'm citing is "A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility." If your serial device is not ttyS0 which is common initial-setup does not run and you can not get into the install at all as root is locked and no account is created.
Comment 5 Vratislav Podzimek 2013-08-12 10:04:07 EDT
Adding all the console devices revealed and suggested here so far would be an easy patch, but in the same time a step on an endless road. I've been discussing this problem with systemd guys and the only real solution seems to be having a special initial-setup.target, that would run the i-s services and once they are finished, boot to the basic.target and so forth where the getty@* services would run. However, I'm not 100% sure the clean solution would be so idylic as it seems. If it doesn't work or requires huge and problematic changes, we could simply keep adding console devices.
Comment 6 Kamil Páral 2013-08-21 12:58:05 EDT
Discussed at 2013-08-21 blocker review meeting . This is rejected as an Alpha blocker, but accepted as Alpha Freeze Exception and also accepted as a Beta blocker, because it violates the following F20 beta release criterion for many headless minimal arm installs: "The installer must be able to complete an installation using the serial console interface."  This should be affecting only minimal installs on headless ARM devices. If somebody believes this is serious enough to block Alpha, we can consider adjusting our release criteria.  http://meetbot.fedoraproject.org/fedora-blocker-review/2013-08-21/  https://fedoraproject.org/wiki/Fedora_20_Beta_Release_Criteria#Installation_interfaces
Comment 7 Adam Williamson 2013-08-21 14:12:56 EDT
We kinda handwaved this in the blocker meeting on the basis it's an easy fix and not worth wasting a lot of time arguing about changing the criteria. So: vpodzime, can you please put the 'simple' fix (list more known serial console devices in the Before= line) into initial-setup just for now, and quickly? That way we can be sure this will be OK for Alpha and we can work on the proper fix (a special systemd target for initial-setup). Once we're happy with the proper fix we can implement that and drop the simple fix. I do like the special target approach, but it's obviously a bit more work than the other one.
Comment 8 Ben Greear 2013-08-21 17:15:23 EDT
I hit this problem on Fedora 19. I am running a script after logging into the GUI that installs Mate, twiddles this and that, and also enables the serial console in grub and the kernel boot command line. The script then changes the systemd target to the equivalent of 'runlevel 3', and I reboot the machine. The end result of this is that there is no way to log in on the default console (VGA, keyboard, mouse). You can eventually get a console login on 'alt F2', but it takes a few tries and I'm not sure why that works or doesn't anyway. If you do connect to the serial console, then you get the prompt: Please make your choice from above ['q' to quit | 'c' to continue | 'r' to refresh]: Please make your choice from above ['q' to quit | 'c' to continue | 'r' to refresh]: r ================================================================================ ================================================================================ Initial setup of Fedora Please make your choice from above ['q' to quit | 'c' to continue | 'r' to refresh]: I have no idea what, if anything, it is doing, but if you type 'c' then you get normal login prompts on all the consoles as expected. You also get prompt back if you 'yum erase initial-setup'. It seems to me that if this prompt exists anywhere, it should exist on ALL console logins. For now, just erasing the initial-setup package seems a decent work-around. If someone knows a better work-around, please post it.
Comment 9 Adam Williamson 2013-08-21 18:28:25 EDT
ben: you can make the appropriate edit to initial-setup.service somehow before booting the installed system.
Comment 10 Vratislav Podzimek 2013-08-22 06:02:56 EDT
(In reply to Adam Williamson from comment #7) > We kinda handwaved this in the blocker meeting on the basis it's an easy fix > and not worth wasting a lot of time arguing about changing the criteria. > > So: vpodzime, can you please put the 'simple' fix (list more known serial > console devices in the Before= line) into initial-setup just for now, and > quickly? That way we can be sure this will be OK for Alpha and we can work > on the proper fix (a special systemd target for initial-setup). Once we're > happy with the proper fix we can implement that and drop the simple fix. I > do like the special target approach, but it's obviously a bit more work than > the other one. Patch posted to anaconda-patches.
Comment 11 Fedora End Of Life 2013-09-16 13:12:47 EDT
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
Comment 12 Petr Schindler 2013-09-18 11:12:15 EDT
Fix is verified to work and initial-setup-0.3.7-1 is in stable. Closing this bug.
Comment 13 Adam Williamson 2013-09-19 04:50:19 EDT
This does not appear to work for me with Alpha RC4 on a Trimslice :( I write the minimal image to my USB stick and boot; tty1 displays only a flashing cursor at top left. ctrl-alt-f2 gives me a login prompt on tty2, but I have no usable account to log in as...
Comment 14 Adam Williamson 2013-09-19 04:54:19 EDT
oh, that's probably not this bug. forgot this was about serial consoles.