Project

General

Profile

Actions

action #66961

closed

[SLE][Migration][SLE15SP2][Regression] test fails in zypper_lifecycle - timeout, need further investigation

Added by coolgw about 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2020-05-18
Due date:
% Done:

100%

Estimated time:
12.00 h
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP2-Regression-on-Migration-from-SLE15-SPX-to-SLE15-SP2-aarch64-offline_sles15_pscc_basesys-srv-desk-dev-contm-lgm-wsm_all_full@aarch64 fails in
zypper_lifecycle

Test suite description

Reproducible

Fails since (at least) Build 105.4

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest


Files

Actions #1

Updated by leli about 4 years ago

  • Assignee set to tinawang123
Actions #2

Updated by leli about 4 years ago

  • Estimated time set to 12.00 h
Actions #3

Updated by hjluo about 4 years ago

  • Status changed from New to In Progress
  • Assignee changed from tinawang123 to hjluo
  • % Done changed from 0 to 20

check this out while tracking the bug of "zypper lifecycle failed to build cache"
https://bugzilla.suse.com/show_bug.cgi?id=1166549

Actions #4

Updated by hjluo about 4 years ago

To fast up the time consumed, we exclude some of the modules to just focus on zypper_lfiecycle.

openqa-clone-custom-git-refspec https://github.com/hjluo/os-autoinst-distri-opensuse/tree/zypper_lifecycle
http://openqa.suse.de/tests/4312792 EXCLUDE_MODULES=install_service,check_upgraded_service,apache,supportutils,check_package_version,force_scheduled_tasks,yast2_lan,salt,yast2_i,yast2_bootloader,firewall_enabled,mtab

https://openqa.nue.suse.com/tests/4315513
https://openqa.nue.suse.com/tests/4315513#step/zypper_lifecycle/11
and it PASSED.

Actions #5

Updated by hjluo about 4 years ago

  • % Done changed from 20 to 50
Actions #6

Updated by hjluo about 4 years ago

  • % Done changed from 50 to 60

rerun with
EXCLUDE_MODULES=install_service,check_upgraded_service,apache,supportutils,check_package_version,force_scheduled_tasks,yast2_lan,salt,yast2_i,yast2_bootloader,firewall_enabled,mtab
http://openqa.suse.de/t4322537
http://openqa.suse.de/t4322538
http://openqa.suse.de/t4322539
http://openqa.suse.de/t4322540
http://openqa.suse.de/t4322541

ALL PASSED

Actions #9

Updated by hjluo about 4 years ago

  • % Done changed from 80 to 90
Actions #10

Updated by hjluo about 4 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

PR merged.

Actions #11

Updated by tinawang123 about 4 years ago

  • Status changed from Resolved to Workable
Actions #13

Updated by hjluo about 4 years ago

  • % Done changed from 100 to 70

Failed case: https://openqa.nue.suse.com/tests/4344404
rerun with EXCLUDE_MODULE: install_service,check_upgraded_service,apache,supportutils,check_package_version,force_scheduled_tasks,yast2_lan,salt,yast2_i,yast2_bootloader,firewall_enabled,mtab

https://openqa.nue.suse.com/tests/4348935 PASSED

Actions #14

Updated by hjluo about 4 years ago

add pkcon_quit before zypper lifecycle and rerun:
barry:~/:[130]# for i in 4343217 4343188 4343202 4344404 4343575 4343569; do openqa-clone-custom-git-refspec https://github.com/hjluo/os-autoinst-distri-opensuse/tree/zypper_lifecycle_timeout http://openqa.suse.de/tests/$i -c "--apikey XXX --apisecret XXXX"; done
http://openqa.suse.de/t4357892
http://openqa.suse.de/t4357893
http://openqa.suse.de/t4357894
http://openqa.suse.de/t4357895
http://openqa.suse.de/t4357896
http://openqa.suse.de/t4357897

STILL TIMEOUT, need check out.

Actions #15

Updated by hjluo about 4 years ago

Afer dived into the developer mode to check the command on the VM and found this is actually a known bug of
bsc#1166549. the script_out 'zypper lifecycle' will block the I/O for lots of error message before it shows
the right output. I've uploaded the screenshots to prove this.

Updated by hjluo about 4 years ago

Attached the error screenshot on the vm. you can see the errors in the attached pictures.

Actions #17

Updated by hjluo about 4 years ago

  • Status changed from Workable to Resolved
  • % Done changed from 70 to 100

close this as it's a bug of bsc#1166549.

Actions #18

Updated by okurz about 4 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: offline_sles12sp5_pscc_sdk-tcm-wsm_all_full
https://openqa.suse.de/tests/4343569

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #19

Updated by okurz almost 4 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: offline_sles12sp5_pscc_sdk-tcm-wsm_all_full
https://openqa.suse.de/tests/4343569

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #20

Updated by openqa_review almost 4 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: offline_sles12sp5_pscc_sdk-tcm-wsm_all_full
https://openqa.suse.de/tests/4343569

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions

Also available in: Atom PDF