Created attachment 1534942 [details] unable to install bootloader Description of problem: Unable to install bootloader Version-Release number of selected component (if applicable): anacona 30.23-1.fc30 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1534951 [details] liveinst failure
Created attachment 1534952 [details] GTK could not be initialized using setenforce=0 on reboot
(In reply to satellitgo from comment #0) > Created attachment 1534942 [details] > unable to install bootloader > > Description of problem: > Unable to install bootloader > > Version-Release number of selected component (if applicable): > > anacona 30.23-1.fc30 > How reproducible: > > > Steps to Reproduce: > 1. > 2. > 3. > > Actual results: > > > Expected results: > > > Additional info: 2048 memory 8 GB HD Oracle VM fails like this 2048 memory 16 GB HD will test...
still fails with 16 GB HD
I just did one of these with 20190211 Live media, so you need to be more clear which compose you're using, and also need the /tmp/*log files so we can see what's going on. And also reproduce steps - did you use custom or automatic partitioning, etc.
Almost certainly this is https://bugzilla.redhat.com/show_bug.cgi?id=1676357 . openQA tests failed the same way today and the logs point to that. *** This bug has been marked as a duplicate of bug 1676357 ***
Actually wasn't a dupe, there were two bugs. Yay.
For the record, the other bug is that javier added a patch to grub2 intended to make something work better for btrfs BLS installs: https://src.fedoraproject.org/rpms/grub2/c/e3a408a5213b41654d0802bed80fb261d685d7de?branch=master but the 0282 patch there has a bug; it assumes /boot/loader/entries always already exists, which is not a safe assumption. In fact when grub2-mkconfig is run during Fedora live install, /boot/loader/entries does not exist yet. So that was failing.
Created attachment 1535587 [details] Install works in 20190216 in vmm looks fixed in VMM 20190216 soas x86
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.