http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c15
--- Comment #15 from Jiri Srain
(In reply to comment #11 and #12)
I dont think so. The system-setup was already quite old and stable, based on Leap 15.0. The issue occured after I did an online-update to Leap 15.1. So it is _not_ an image-issue
Did you run the YaST bootloader module also before upgrade from 15.0 to 15.1? I can imagine that the problem did not show up if you did not. I'm aware of at least one issue, where a bootloader was not configured correctly in the initial image, but the bug was revealed after upgrade first. While it is hardly any related to this particular bug (back then it was only about the label), especially if you did not run YaST bootloader module at all before upgrade it sounds likely that the bug was there from the beginning (or could have been introduced any time before you performed upgrade).
A fix for the error message could be a potential solution as well :-)
Axel: Given the explanation, the error message is pretty accurate. Sure we can improve it, but do you have a suggestion?
Good question - I understand that EFI was disabled somehow? So instead of Caller: /usr/share/YaST2/lib/bootloader/grub_install.rb:141:in `target' the root cause of the problem: unsupported combination of architecture aarch64 and disabled EFI - please enable EFI
Not necessarily: The point is: YaST stores the information in sysconfig. If the information there is wrong from the beginning, it does not prevent system from booting and in many cases even update of the bootloader itself will not result in failure.
The JeOS images are usually maitnained by Fabian; before reassigning it, it would be useful to know whether most recent images are affected too (I've already seen images which had similar bugs fixed in later versions)
I did a full setup with a recent image and did not encounter the issue. As written above, it seemed to be related to the upgrade process
-- You are receiving this mail because: You are on the CC list for the bug.