Project

General

Profile

Actions
Copy link

action #60938

closed

[SLE][Migration][SLE15SP2]test fails in yast2_migration - yast2 migration cannot start up. Just this one always failed.

Added by tinawang123 over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
tinawang123
Category:
Bugs in existing tests
Target version:
-
Start date:
2019-12-12
Due date:
% Done:

100%

Estimated time:
8.00 h
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP2-Regression-on-Migration-from-SLE15-SPX-to-SLE15-SP2-x86_64-online_sles15sp1_pscc_lp-we-basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm_all_full@64bit fails in
yast2_migration

Test suite description

Reproducible

Fails since (at least) Build 104.1 (current job)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by leli over 4 years ago

  • Priority changed from Normal to High
Actions
Copy link
 #2

Updated by tinawang123 over 4 years ago

  • Assignee set to tinawang123
Actions
Copy link
 #3

Updated by tinawang123 over 4 years ago

  • Status changed from New to Rejected
  • % Done changed from 0 to 100

Maybe related with bug: https://bugzilla.suse.com/show_bug.cgi?id=1157926
If still existed, need reopen this one

Actions
Copy link
 #4

Updated by okurz over 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: online_sles15sp1_pscc_lp-we-basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm_all_full
https://openqa.suse.de/tests/3760172

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
Copy link
 #5

Updated by tinawang123 over 4 years ago

  • Status changed from Rejected to New
  • % Done changed from 100 to 0
Actions
Copy link
 #6

Updated by tinawang123 over 4 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 70
  • Estimated time set to 8.00 h
Actions
Copy link
 #7

Updated by tinawang123 over 4 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 70 to 100
Actions
Copy link
 #8

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: online_sles15sp1_pscc_lp-we-basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm_all_full
https://openqa.suse.de/tests/3823740

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
Copy link
 #9

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: online_sles15sp1_pscc_lp-we-basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm_all_full
https://openqa.suse.de/tests/3868516

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
Copy link
 #10

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: online_sles15_pscc_basesys-srv-desk-dev-contm-lgm-wsm_all_full
https://openqa.suse.de/tests/3908743

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
Copy link

Also available in: Atom PDF