action #126044
closed
- Copied from action #126041: Manual testing of D-Installer for ALP Bedrock (March Prototype) added
- Subject changed from Perform manual testing of D-Installer for both ALP Micro to Manual testing of D-Installer for both ALP Micro (March Prototype)
- Subject changed from Manual testing of D-Installer for both ALP Micro (March Prototype) to Manual testing of D-Installer for ALP Micro (March Prototype)
- Description updated (diff)
- Due date set to 2023-03-30
- Start date deleted (
2023-03-30)
- Status changed from Workable to In Progress
- Assignee set to JRivrain
- Description updated (diff)
iscsiadm,dmraid and multipath command-not-found seen in logs:
2023-03-15 18:03:28 localhost.localdomain(1327) [Ruby] modules/IscsiClientLib.rb(readSessions):628 reading current settings
2023-03-15 18:03:28 localhost.localdomain(1327) [Ruby] modules/IscsiClientLib.rb(GetAdmCmd):273 GetAdmCmd: LC_ALL=POSIX iscsiadm -m session -P 1
2023-03-15 18:03:28 localhost.localdomain(1327) [bash] ShellCommand.cc(shellcommand):78 sh: line 1: iscsiadm: command not found
2023-03-15 18:03:14 localhost.localdomain(1327) [libstorage] SystemCmd.cc(SystemCmd):80 constructor SystemCmd("/sbin/dmraid --sets=active -ccc")
2023-03-15 18:03:14 localhost.localdomain(1327) [libstorage] SystemCmd.cc(execute):203 SystemCmd Executing:"/sbin/dmraid --sets=active -ccc"
2023-03-15 18:03:14 localhost.localdomain(1327) [libstorage] SystemCmd.cc(execute):204 timestamp [31.869466], 2023-03-15 17:03:14 GMT, 2023-03-15 18:03:14 CET
2023-03-15 18:03:14 localhost.localdomain(1327) [libstorage] SystemCmd.cc(addLine):569 Adding Line 1 "/bin/sh: line 1: /sbin/dmraid: No such file or directory"
logs cannot be downloaded from options (upper right menu) even though the save_y2logs is exectuted, looks like the feature is un-finished as it looks like this already in the PR
2023-03-15 18:22:01 localhost.localdomain(1325) [Ruby] lib/cheetah.rb(record_commands):163 Executing "save_y2logs".
2023-03-15 18:22:01 localhost.localdomain(1325) [Ruby] lib/cheetah.rb(log_stream_line):211 Error output: Saving YaST logs to /tmp/y2log-V4xhEJ.tar.xz
2023-03-15 18:22:02 localhost.localdomain(1325) [Ruby] lib/cheetah.rb(record_status):183 Status: 0
2023-03-15 18:22:02 localhost.localdomain(1325) [Ruby] lib/cheetah.rb(record_commands):163 Executing "chown root: /tmp/y2log-V4xhEJ.tar.xz".
2023-03-15 18:22:02 localhost.localdomain(1325) [Ruby] lib/cheetah.rb(record_status):183 Status: 0
- Description updated (diff)
- Description updated (diff)
- Changing language in d-installer has no effect, except for setting locale, even after install, I assume devs know about it.
- Occasionally, firefox fails to render the page resulting in a blank page, pressing f5 to refresh fixes it.
Apart from the things I already signaled, everything works pretty well. Tested:
qemu with 2 disks, 2 NICs, user config, lvm, encryption. System installed with or without encryption. I also played around in the installed system and could not find any problem, rather lots of things I wish were present, but it's early stage.
- Description updated (diff)
- Description updated (diff)
- Description updated (diff)
Problems on latest build, 0.8-ALP-Build2.3:
- page never finishes loading if we try to load with two disks with one encrypted disk.
In build x86_64-0.8.1-ALP-Build5.2, iscsi does not work, as it seems like open-iscsi is still missing in the iso, also ibft does not seem to work at all, no disks are detected. we are also getting an error regarding missing packages.
ISCSI testing:
These instruction work on x86_64-0.8.1-ALP-Build6.2, but the UI may change anytime.
Here are 2 scenarios that can be used. In both cases we need to set-up an iscsi target (server). We can need step one from IBFT how-to but it could be nice to also cover a setup with authentication.
Simple use of iscsi disk in the setup
- Scenario 1
Once an iscsi target was created, simply start d-installer then click "devices" To get to the iscsi menu, you must click the 3 bars at the upper right corner "configure iscsi". Put the IP of you iscsi target and click ok, then you should see some iscsi volumes appear.
Scenario 2
set-up an ibft environment,then install the system on the disks that should be detected. Normally the disks are seen as normal disks. You can still go to iscsi configuration connect more isci volumes, but last time I checked only the one which is used for ibft can be used for install.
On x86_64-0.8.3-ALP-Build9.1:
auto-installation and dinstaller-cli work as expected .
but problems found during and after install:
- d-installer lets you create a user but not set root password, but does not add the user to sudoers. So we can't become root at all.
- lots of packages are missing
- so many packages are missing that system is not bootable.
- Status changed from In Progress to Resolved
Also available in: Atom
PDF
