action #81004
openjobs incomplete with auto_review:"(?s)sol deactivate: Info: SOL payload already de-activated":retry
0%
Description
Observation¶
https://openqa.suse.de/tests/5163091 shows incomplete with
[2020-12-11T20:03:05.533 CET] [debug] tests/installation/reboot_after_installation.pm:118 called power_action_utils::power_action -> lib/power_action_utils.pm:260 called power_action_utils::prepare_system_shutdown -> lib/power_action_utils.pm:52 called backend::console_proxy::__ANON__
[2020-12-11T20:03:05.534 CET] [debug] <<< backend::console_proxy::__ANON__(wrapped_call={
"args" => [],
"console" => "root-ssh",
"function" => "kill_ssh"
})
[37m[2020-12-11T20:03:05.535 CET] [debug] Closing SSH serial connection with scooter-1.qa.suse.de
[0m[37m[2020-12-11T20:03:08.779 CET] [debug] Backend process died, backend errors are reported below in the following lines:
ipmitool -I lanplus -H sp.scooter.qa.suse.de -U ADMIN -P ADMIN sol deactivate: Info: SOL payload already de-activated at /usr/lib/os-autoinst/backend/ipmi.pm line 65.
[0m[37m[2020-12-11T20:03:13.867 CET] [debug] IPMI: Chassis Power Control: Down/Off
[0m[37m[2020-12-11T20:03:13.956 CET] [debug] capture loop failed ipmitool -I lanplus -H sp.scooter.qa.suse.de -U ADMIN -P ADMIN sol deactivate: Info: SOL payload already de-activated at /usr/lib/os-autoinst/backend/ipmi.pm line 65.
Steps to reproduce¶
Find jobs referencing this ticket with the help of
https://raw.githubusercontent.com/os-autoinst/scripts/master/openqa-query-for-job-label ,
for example to look for ticket 12345 call openqa-query-for-job-label poo#12345
Problem¶
We should ignore this kind of error by reason category in our "auto-review" approach.
Workaround¶
Retrigger, might help :)
Updated by okurz about 3 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: sles4sap_gnome_saptune_v2_baremetal@64bit-ipmi-nvdimm
https://openqa.suse.de/tests/5528838
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by mgrifalconi almost 3 years ago
Hello Oliver, something must be wrong with the autoreview/auto takeover since this https://openqa.suse.de/tests/5997075#step/partitioning_firstdisk/6 has nothing to do with it.
I remove it but on new incidents it keeps being added.
Updated by okurz almost 3 years ago
Checking latest results I can see that the ticket label reappears in https://openqa.suse.de/tests/6203786 which is the first failing job in a long row of incompletes. For the "label carry-over" all incompletes are ignored and the label of the last failed job is taken over if there are no jobs of different result or failing in any different test module. To prevent the label carry over we can simply remove the comment from the last failed job and any new failed jobs will not take over the label. I did that now.
Updated by openqa_review almost 3 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qam-sles4sap_online_dvd_gnome_hana_nvdimm@64bit-ipmi-nvdimm
https://openqa.suse.de/tests/6268593
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz almost 3 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qam-sles4sap_online_dvd_gnome_hana_nvdimm@64bit-ipmi-nvdimm
https://openqa.suse.de/tests/6268593
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The label in the openQA scenario is removed
Updated by openqa_review almost 3 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qam-sles4sap_online_dvd_gnome_hana_nvdimm@64bit-ipmi-nvdimm
https://openqa.suse.de/tests/6469323
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The label in the openQA scenario is removed
Updated by openqa_review over 2 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: prj4_guest_upgrade_sles15sp3_on_sles15sp3-kvm
https://openqa.suse.de/tests/6926655
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The label in the openQA scenario is removed
Updated by openqa_review over 2 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qam-sles4sap_online_dvd_gnome_hana_nvdimm@64bit-ipmi-nvdimm
https://openqa.suse.de/tests/7632914
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review over 2 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: btrfs_libstorage-ng@64bit-ipmi
https://openqa.suse.de/tests/7980715
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Updated by openqa_review almost 2 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: gi-guest_developing-on-host_sles12sp5-kvm
https://openqa.suse.de/tests/8751566#step/boot_from_pxe/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 272 days if nothing changes in this ticket.
Updated by openqa_review about 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: uefi-gi-guest_sles12sp5-on-host_developing-kvm@64bit-ipmi-large-mem
https://openqa.suse.de/tests/10691527#step/boot_from_pxe/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 544 days if nothing changes in this ticket.