Project

General

Profile

Actions
Copy link

action #166583

open

coordination #169657: [epic] Handle test fixes and adjustments

Need click 'ok' after press next when yast2_lan_bond_slave_tab_selected via libyui

Added by leli 2 months ago. Updated 7 days ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
2024-09-10
Due date:
% Done:

0%

Estimated time:
Tags:
qe-yam-nov-sprint

Description

Motivation

Failed job: https://openqa.suse.de/tests/15355275#step/yast2_lan_restart_bond/54
The process changed on SLE15SP7, need click 'ok' after press next when yast2_lan_bond_slave_tab_selected via libyui.

Acceptance criteria

AC1: Need click 'ok' after press next when yast2_lan_bond_slave_tab_selected via libyui

Actions
Copy link
 #1

Updated by leli 2 months ago

  • Tags set to qe-yam-sep-sprint
  • Status changed from New to Workable
Actions
Copy link
 #2

Updated by leli 2 months ago

  • Status changed from Workable to In Progress
  • Assignee set to leli
Actions
Copy link
 #3

Updated by leli 2 months ago ยท Edited

Compared the passed job : https://openqa.suse.de/tests/14611766#step/yast2_lan_restart_bond/44, the root cause for this issue may for the bondport hasn't shown as br1, https://openqa.suse.de/tests/15355275#step/yast2_lan_restart_bond/53
I will try to download the iso: http://openqa.suse.de/tests/15398123/asset/iso/SLE-15-SP7-Online-x86_64-Build14.1-Media1.iso to manually reproduce it.

Actions
Copy link
 #4

Updated by leli 2 months ago

Still can't fix the issue through add more waittime before send next key, https://openqa.suse.de/tests/15424608#step/yast2_lan_restart_bond/47

I think this may related with the edit the bonding while not wait and send next key which caused yast2 vlan still run something in backend which caused later send cancel key but no response. But I can't reproduce the issue manually. I will try to simulate the steps as openQA in manual test(edit bonding and click next quickly).

Actions
Copy link
 #5

Updated by leli 2 months ago

  • Tags deleted (qe-yam-sep-sprint)
  • Status changed from In Progress to New
  • Assignee deleted (leli)

As discussed in stand-up meeting, 15SP7 issues is not high priority task for us now, so put it in backlog.

Actions
Copy link
 #6

Updated by openqa_review about 2 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: yast2_gui
https://openqa.suse.de/tests/15547046#step/yast2_security/1

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #7

Updated by openqa_review 27 days ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: yast2_gui
https://openqa.suse.de/tests/15749904#step/yast2_lan_restart_bond/1

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.

Actions
Copy link
 #8

Updated by JERiveraMoya 15 days ago

  • Tags set to qe-yam-nov-sprint
  • Status changed from New to Workable
  • Parent task set to #151816
Actions
Copy link
 #9

Updated by JERiveraMoya 10 days ago

  • Parent task changed from #151816 to #169657
Actions
Copy link

Also available in: Atom PDF