-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest agama produces unbootable Leap16 #1446
Comments
I get the same result in a KVM VM, no exotic options WRT partitioning. |
logs from TW based installation done by agama-installer-openSUSE.x86_64-9.0.0-openSUSE-Build5.3.iso (downloaded from :Devel) today in the morning). All kept as default just changed root password. |
Hmmm that system indeed booted. Seems like ball is on my playground. |
I have reproduced the problem with Leap 16.0. Here are the YaST2 logs. |
I do not whether it is a red herring, but Agama cannot umount the target system at the end of the installation because of this:
And the processes look like this:
Bear in mind that |
ah that could be it! |
uploading recent logs after fixing the product fine in 000release-packages |
Mount strikes again: and in de y2log-1 file: |
Hi @stacheldrahtje, Which version are you trying? It was reported to work in a previous comment. |
I sifted through Lubos latest attachment. |
It looks like these logs are old. The good ones are here: #1447 (comment). |
No problem, it wasn't clear. I can confirm that it works, hence I am closing the bug. |
tested now and worked to install with: https://download.opensuse.org/repositories/systemsmanagement:/Agama:/Devel/images/iso/agama-installer-openSUSE.x86_64-9.0.0-openSUSE-Build9.21.iso but could not install any packages but i guess not much is packaged yet |
Tested with latest agama in :Devel. Neither TW nor Leap16 can boot to grub2 after installation. Screen is stuck at loading bootloader.
The text was updated successfully, but these errors were encountered: