Project

General

Profile

Actions

action #38423

closed

[sle][functional][u][hard] Refactor first_boot to unify duplicated behavior for remote backend

Added by SLindoMansilla over 5 years ago. Updated about 4 years ago.

Status:
Rejected
Priority:
High
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 31
Start date:
2018-07-16
Due date:
% Done:

0%

Estimated time:
Difficulty:
hard

Description

There are a few machines that use remote backend

  • IPMI
  • s390x
  • XEN
  • PPC

The test module first_boot is becoming less maintainable since specific code are added without paying attention to duplicated code.

Acceptance criteria

  • AC: There is no duplicate code for remote backends

Latest results

SLE 12-SP4


Related issues 6 (1 open5 closed)

Related to openQA Tests - action #37820: [functional][sle][u][hard][ipmi][sporadic] test fails in first_boot - Lost connection to SUT on SLE12-SP4Resolvedzluo2018-06-262018-07-17

Actions
Related to openQA Tests - action #33388: [functional][u][easy][pvm] Implement proper split from other backendsResolvedmgriessmeier2019-02-17

Actions
Related to openQA Tests - action #31375: [sle][functional][ipmi][u][hard] test fails in first_boot - VNC installation on SLE 15 failed because of various issues (ipmi worker, first_boot, boot_from_pxe, await_install)RejectedSLindoMansilla2018-02-05

Actions
Related to openQA Tests - action #56777: [functional][u] test fails in installation - openSUSE Welcome not handled in installation module after autoyastResolvedzluo2019-09-11

Actions
Blocks openQA Tests - action #41207: [qe-core][functional][ipmi] test fails in reboot_gnome - seems we call some code which we are not allowed to do, need to "reset_consoles" or something? nearly there to a complete run again :)Workable2018-09-18

Actions
Copied to openQA Tests - action #60401: [tools] DRY aka. "reduce duplication" in method wait_boot and tests/installation/first_bootResolvedokurz2018-07-16

Actions
Actions #1

Updated by SLindoMansilla over 5 years ago

  • Description updated (diff)
Actions #2

Updated by SLindoMansilla over 5 years ago

  • Description updated (diff)
Actions #3

Updated by SLindoMansilla over 5 years ago

  • Related to action #37820: [functional][sle][u][hard][ipmi][sporadic] test fails in first_boot - Lost connection to SUT on SLE12-SP4 added
Actions #4

Updated by SLindoMansilla over 5 years ago

  • Description updated (diff)
Actions #5

Updated by SLindoMansilla over 5 years ago

  • Description updated (diff)
Actions #6

Updated by SLindoMansilla over 5 years ago

  • Description updated (diff)
Actions #7

Updated by okurz over 5 years ago

  • Subject changed from [sle][functional] Refactor first_boot to unify duplicated behavior for remote backend to [sle][functional][u] Refactor first_boot to unify duplicated behavior for remote backend
  • Due date set to 2018-09-11
  • Target version set to Milestone 19
Actions #8

Updated by okurz over 5 years ago

  • Related to action #33388: [functional][u][easy][pvm] Implement proper split from other backends added
Actions #9

Updated by SLindoMansilla over 5 years ago

  • Subject changed from [sle][functional][u] Refactor first_boot to unify duplicated behavior for remote backend to [sle][functional][u][hard] Refactor first_boot to unify duplicated behavior for remote backend
  • Estimated time set to 8.00 h
Actions #10

Updated by okurz over 5 years ago

  • Status changed from New to Workable
Actions #11

Updated by mgriessmeier over 5 years ago

  • Related to action #31375: [sle][functional][ipmi][u][hard] test fails in first_boot - VNC installation on SLE 15 failed because of various issues (ipmi worker, first_boot, boot_from_pxe, await_install) added
Actions #12

Updated by mgriessmeier over 5 years ago

  • Due date changed from 2018-09-11 to 2018-09-25
Actions #13

Updated by mgriessmeier over 5 years ago

  • Due date changed from 2018-09-25 to 2018-10-09

let's do it after #33388

Actions #14

Updated by okurz over 5 years ago

  • Due date changed from 2018-10-09 to 2018-10-23
  • Target version changed from Milestone 19 to Milestone 20
Actions #15

Updated by okurz over 5 years ago

  • Due date deleted (2018-10-23)
  • Target version changed from Milestone 20 to Milestone 22
Actions #16

Updated by szarate about 5 years ago

  • Status changed from Workable to Blocked

IMO this task needs grooming, but with #33388 not being clearly defined, there's no reason to have this in workable

Actions #17

Updated by okurz about 5 years ago

  • Assignee set to okurz
  • Target version changed from Milestone 22 to Milestone 23

I will track it then.

Actions #18

Updated by okurz almost 5 years ago

  • Target version changed from Milestone 23 to Milestone 25
Actions #19

Updated by okurz almost 5 years ago

  • Assignee changed from okurz to mgriessmeier

Move to new QSF-u PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-u. Feel free to discuss with me or reassign to me or someone else in this case. Thanks.

Actions #20

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 25 to Milestone 26
Actions #21

Updated by mgriessmeier over 4 years ago

  • Status changed from Blocked to Workable
  • Assignee deleted (mgriessmeier)
  • Target version changed from Milestone 26 to Milestone 27

for grooming

Actions #22

Updated by SLindoMansilla over 4 years ago

  • Blocks action #41207: [qe-core][functional][ipmi] test fails in reboot_gnome - seems we call some code which we are not allowed to do, need to "reset_consoles" or something? nearly there to a complete run again :) added
Actions #23

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: default@64bit-ipmi
https://openqa.suse.de/tests/3341271

Actions #24

Updated by SLindoMansilla over 4 years ago

  • Related to action #56777: [functional][u] test fails in installation - openSUSE Welcome not handled in installation module after autoyast added
Actions #25

Updated by mgriessmeier over 4 years ago

  • Priority changed from Normal to High
  • Target version changed from Milestone 27 to Milestone 28
  • Estimated time deleted (8.00 h)
Actions #26

Updated by okurz about 4 years ago

  • Copied to action #60401: [tools] DRY aka. "reduce duplication" in method wait_boot and tests/installation/first_boot added
Actions #27

Updated by mgriessmeier about 4 years ago

  • Target version changed from Milestone 28 to Milestone 31

needs to be discussed offline

Actions #28

Updated by zluo about 4 years ago

  • Status changed from Workable to Rejected
  • Assignee set to zluo
Actions

Also available in: Atom PDF