Installation of aarch64 Tumbleweed and Leap Micro 5.2 ends up on grub> prompt

[ggardet]

Installation of aarch64 Tumbleweed and Leap Micro 5.2 ends up on grub> prompt.

                             GNU GRUB  version 2.06

   Minimal BASH-like line editing is supported. For the first word, TAB   
   lists possible command completions. Anywhere else TAB lists possible   
   device or file completions.                                            


grub>

Note: aarch64 Leap 15.4 installation worked fine.

[imobachgs]

Hi @ggardet,

Would it be possible for you to gather YaST logs? After a failing installation, you might change to a console (ctrl+alt+f1), and log in with "root" (user) and "linux" (password). After that, typing save_y2logs should extract them for you.

Thank you!

[jreidinger]

As it is using qemu, I will try to reproduce it. It is strange as it uses TW code for installation, so it should not fail there

[jreidinger]

I reproduce it and it failed with

2022-11-01 22:21:38 <1> localhost.localdomain(2427) [Ruby] lib/cheetah.rb(record_commands):163 Executing "/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg".
2022-11-01 22:21:52 <3> localhost.localdomain(2427) [Ruby] lib/cheetah.rb(log_stream_line):211 Error output: /usr/sbin/grub2-probe: error: failed to get canonical path of `LiveOS_rootfs'.
2022-11-01 22:21:52 <3> localhost.localdomain(2427) [Ruby] lib/cheetah.rb(record_status):183 Status: 1
2022-11-01 22:21:52 <3> localhost.localdomain(2427) [Ruby] yast2/execute.rb(rescue in popup_error):235 Execution of command "[["/usr/sbin/grub2-mkconfig", "-o", "/boot/grub2/grub.cfg"]]" failed.
Exit code: 1
Error output: /usr/sbin/grub2-probe: error: failed to get canonical path of `LiveOS_rootfs'.

[jreidinger]

the strange path comes from /proc/mounts
LiveOS_rootfs / overlay rw,relatime,lowerdir=/run/overlay/rootfsbase,upperdir=/run/overlay/overlayfs/rw,workdir=/run/overlay/overlayfs/work 0 0

So it is some overlayfs that confuse grub.

[jreidinger]

Another attempt to install failed with different issue that dracut is not available and looks like caused by mocked SpaceCalculation at https://github.com/yast/d-installer/blob/master/service/lib/dinstaller/dbus/y2dir/software/modules/SpaceCalculation.rb

For interested people I attach also y2logs from that attempt ( ignore initial dbus timeouts that is caused by systemd attempt to start service that timeout and then I start it manually )
y2log-utSZfv.tar.gz

Important part of log:

2022-11-25 11:15:30 <1> localhost.localdomain(1322) [Ruby] modules/Packages.rb(AddFailedMounts):494 Proposal summary: $["warning":"Not enough disk space. Remove some packages in the single selection.<br>These packages need to be selected to install: NetworkManager<br>These patterns need to be selected to install: apparmor<br>Please manually select the needed items to install.", "warning_level":`blocker]

[jreidinger]

And after another round of debugging it is now clear what cause this bug. It is repository definition. Only Leap 15.4 has aarch architecture as part of repositories in https://download.opensuse.org/distribution/leap/15.4/repo/oss/
On other hand MicroOS does not have aarch at all. And for TW it needs own repository in ports at
https://download.opensuse.org/ports/aarch64/tumbleweed/repo/oss/

So for fix we will need to be able to define arch specific urls for repositories and also be able to specify products based on architecture as not all products are available on all architectures.

[jreidinger]

OK, just successfully verified that with modified d-installer.yml file that points to ports, TW can be installed and booted.

[jreidinger]

And one more good news. I found that we switch to Micro 5.3 and Micro5.3 has support for aarch64, so I will add it as part of fix for TW.

[ancorgs]

I understand this is fixed with recent images. Is that the case? If so, shouldn't we close this issue?