Description of problem: Using any of the 20 Alpha RC3 install images (32- or 64-bit, DVD or netinst), text install fails after completing all spokes and hitting 'c'. Instead of beginning the install, it reboots. I tested both minimal and default GNOME installs. Minimal GUI install seems to work okay (at least it didn't reboot after hitting the button to begin installation). Version-Release number of selected component (if applicable): anaconda-20.17-1 How reproducible: always Steps to Reproduce: 1. using text install, complete all spokes 2. hit 'c' to begin installation Actual results: reboots Expected results: should install
Proposing as Alpha Blocker according to https://fedoraproject.org/wiki/Fedora_20_Alpha_Release_Criteria#Installation_interfaces : "When using the dedicated installer images, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces."
Should have mentioned that this worked fine in 20 Alpha RC2 (with anaconda-20.15-1).
I can confirm this. It's regression from RC2. +1 blocker
To speed up blocker acceptance process, confirmed, +1 blocker. Vratislav, thanks for quick patch!
+1 blocker
Fix works for me. I'm able to process through the installation with it. We have +3 blocker now. I'm moving it to accepted.
Created attachment 798864 [details] screenshot of netinst install with 20 Alpha RC3 When I was installing from the netinsts, I saw that yum error again (screenshot attached). Don't know if it's related, and upon refreshing the spokes all showed [x], after which I hit 'c' and generated the reboot.
(In reply to Andre Robatino from comment #7) > Created attachment 798864 [details] > screenshot of netinst install with 20 Alpha RC3 > > When I was installing from the netinsts, I saw that yum error again > (screenshot attached). Don't know if it's related, and upon refreshing the > spokes all showed [x], after which I hit 'c' and generated the reboot. I saw it too even with my patch applied byt it seems to be unrelated and not causing any issues.
This also occurs when doing a kickstart installations, the pre-completed spokes appear briefly before the system is rebooted.
This bug seems to be fixed on 20.18-1
Closing since this went to stable.