action #121840
closedcoordination #116449: [epic] Manual testing for ALP in Yam squad
Initial manual testing for D-Installer (ALP December prototype) - Part 1
Description
Motivation¶
For this new release of ALP in December we should perform some initial manual testing.
Acceptance criteria¶
AC1: Perform manual testing of D-Installer
Suggestion¶
Read this blog to kick off this process: https://yast.opensuse.org/blog/2022-12-05/d-installer-needs-you
In case of finding bug, check in Slack channel #proj-alp-wg-installation if it is not already reported.
Files
Updated by JERiveraMoya about 2 years ago
- Status changed from New to In Progress
Updated by JRivrain about 2 years ago
Tests on build 3.18:
Some more testing was done by another contirbutor visible here: https://suse.slack.com/archives/C03GL42JKBL/p1670847477743389
He encountered a problem where we get a grub shell after reboot, see discussion here https://suse.slack.com/archives/C03GL42JKBL/p1670838801836239.
I had the same issue but without secure boot, just with standard partitioning. However, it is sporadic. I collected some logs and shared the info on the same thread. See attached log.
I spent some time trying to reproduce it with debug output without success. The outcome of this is:
For debugging of d-installer we must kill the installer and re-launch it with debug, as follow:
open terminal with ctrl-alt-t
"# d-installer -k"
"# Y2DEBUG=1 d-installer"
click reload in d-installer, upload y2log somewhere at the end of install before clicking reboot.
Now switching to newer build.
Updated by szarate about 2 years ago
Updated by JRivrain about 2 years ago
- File y2log-5.1-2disk-2nic y2log-5.1-2disk-2nic added
Issues found in 5.1:
I tried an install with 2 disks, 2 nics, 1 user with auto-login.
- If I create a user, accept, then decide to go back to it to activate auto-login, I have to input passwords again.
- Cannot use more than one disk for partitioning. But this looks obviously like work-in progress as very little options are available for now.
- After reboot, I had to unlock two devices but then ended-up with grub prompt, see log in attachment.
Updated by JRivrain about 2 years ago
So, a summary of isues found by different persons on builds 3.18 and 5.1:
https://suse.slack.com/archives/C03GL42JKBL/p1670847477743389:
- The drop down list offers quite a few languages for which the live image doesn't have fonts, so it shows these 1001 "unicode character" boxes
- The menu appears unsorted, or at least sorted wrt some unusual ordering
- I selected "Deutsch", and the installed system indeed has de_DE.utf-8 in locale.conf. However, the corresponding glibc locale files do not get installed, and the shell prints a pretty prominent warning about that upon login
- I couldn't find a place to select my keyboard layout. Where should I be looking?
https://suse.slack.com/archives/C03GL42JKBL/p1670838801836239:
- System will not boot after install, both with and without encryption, sporadic but frequent.
https://progress.opensuse.org/issues/121837#note-7:
Here are some of the things I found during a quick installation test:
- alt + tab works (shouldn't imo)
- Too much time to start firefox
- Installer should accept urls for the ssh key (will it automount flash drives?)
- Installer should make clear that either root has a password or an ssh public key must be provided
- Disconnecting network cable during the installation breaks the installation
- Installing system without network results in not working system (installation completes in seconds)
- No clear information on how to get logs if something fails, or see the instalation progress
https://progress.opensuse.org/issues/121840#note-8:
I tried an install with 2 disks, 2 nics, 1 user with auto-login.
- If I create a user, accept, then decide to go back to it to activate auto-login, I have to input passwords again.
- Cannot use more than one disk for partitioning. But this looks obviously like work-in progress as very little options are available for now.
- After reboot, I had to unlock two device but then ended-up with grub prompt, see log in attachment.
Updated by JERiveraMoya about 2 years ago
- Status changed from In Progress to Resolved