I had a longer discussion with Ryan today on the "efibootmgr not found" issue that we hit after getting rid of the subiquity crash which caused /target to be unmounted. The conclusion is that curtin should *not* need efibootmgr to be present in the ephemeral system after all, so we didn't actually get to the bottom of the problem.
For the moment having subiquity stage efibootmgr is fine as a workaround, but before releasing Focal I want to fully understand what's going on and get this done right. I'm not opening a separate bug report for the "efibootmgr not found" problem because a stray umount of /target could be the reason why efibootmgr is not found. IIUC curtin can fallback to run commands on the host system if they are not found in the /target chroot, and this could be why we observe it failing to call efibootmgr in the host. Did we only delay the subiquity crash/respawn/umount? Further investigation is needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865027 Title: focal-arm64 install fails. No space left on device on /target To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1865027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
