action #174673
open[qa-tools][powerVM] netboot failed at loading NBP file sporadically
0%
Description
Description¶
I can see this issue from last Friday. I am not sure if any network or file transfer issue between install server and SUT.
But based on my openQA and manual tests. it can be seen many times when powerVM machines start the netboot even it is a sporadic issue.
May I ask for your kindly help to check this issue?
- Is the NBP file update to date?
- or some network issue between SUT and install server？
- or some performance issue?
Observation¶
openQA test in scenario sle-16.0-agama-installer-ppc64le-agama-powervm@ppc64le-hmc fails in
boot_agama
Test suite description¶
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.
Reproducible¶
Fails since (at least) Build rfan1220
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Files
Updated by dawei_pang 4 days ago
This is a randomly powerpc issue for a long time, probably it is related to powerpc firmware.
Use the followed OFW commands manually to workaround this issue
0 > SET_NVRAM_DEFAULTS
SMS Macro Operation Succeeded.
ok
0 > RESET_PARTITION
Rebooting...
Then nessberry LPAR2 is able to PXE boot into grub successfully
Updated by okurz 4 days ago
- Due date set to 2025-01-06
- Category set to Support
- Status changed from New to Feedback
- Assignee set to okurz
- Target version set to Ready
@rfan1 can it be that the agama test scenario is missing some special test code to call SET_NVRAM_DEFAULTS which other test code already has?
Updated by rfan1 4 days ago
okurz wrote in #note-4:
@rfan1 can it be that the agama test scenario is missing some special test code to call SET_NVRAM_DEFAULTS which other test code already has?
The answer is no, the agama tests use the same net boot process as other sle products. [nbp file, grub.cfg]. the difference is loading different kernel/initrd files to start the installation.
But, I can see below code
# Restore LPAR's NVRAM defaults if SET_NVRAM_DEFAULTS setting is present
if (get_var('SET_NVRAM_DEFAULTS')) {
# Boot into open firmware (of) first to issue a SET_NVRAM_DEFAULTS command
enter_cmd("chsysstate -r lpar -m $hmc_machine_name -o on -b of --id $lpar_id ");
enter_cmd("mkvterm -m $hmc_machine_name --id $lpar_id");
assert_screen 'openfirmware-prompt', 60;
enter_cmd('SET_NVRAM_DEFAULTS');
assert_screen 'openfirmware-prompt';
# Exit from LPAR's console, shutdown LPAR and continue as usual
enter_cmd('~~.');
assert_screen 'terminate-openfirmware-session';
send_key 'y';
assert_screen 'powerhmc-ssh', 60;
enter_cmd("chsysstate -r lpar -m $hmc_machine_name -o shutdown --immed --id $lpar_id ");
check_lpar_is_down($hmc_machine_name, $lpar_id);
}
Let me try if it can help.
Updated by rfan1 4 days ago
Seems the issue is gone with or without the parameter SET_NVRAM_DEFAULTS
http://openqa.suse.de/tests/overview?distri=sle&version=16.0&build=rfan1223_2
Let me monitor it in next few days :)