Project

General

Profile

action #30106

coordination #27074: [sle][functional][epic][sle15][opensuse][y] Update yast2 ui (gui & ncurses) tests for SLE15 and Leap 15

[sle][functional][sle15][yast][y][easy] yast2_vnc failed - update to current behaviour

Added by zluo about 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Start date:
2018-01-10
Due date:
2018-04-10
% Done:

0%

Estimated time:
Difficulty:
easy

Description

Observation

I found yast2 vnc failed:

https://openqa.suse.de/tests/1372272#step/yast2_vnc/9

Need to investigate and provide fix for it. Wait until https://bugzilla.suse.com/show_bug.cgi?id=1085672 is resolved.
Then manually verify if warning is missing and file a bug in these regards, introducing soft-failure.

Acceptance criteria

  1. Test passes on SLE 15

Expected result

Further details

Link to latest


Related issues

Related to openQA Tests - action #30766: [opensuse][functional][yast][medium] test fails in yast2_vnc - because of firewall issueResolved2018-01-242018-02-27

Related to openQA Tests - action #34015: [functional][y][easy] yast2/vnc doesn't have rules for firewalld -> workaround for bsc#1088647Resolved2018-03-292018-05-08

History

#1 Updated by zluo about 5 years ago

  • Category set to Bugs in existing tests

#2 Updated by okurz about 5 years ago

  • Related to action #30766: [opensuse][functional][yast][medium] test fails in yast2_vnc - because of firewall issue added

#3 Updated by okurz about 5 years ago

  • Description updated (diff)
  • Due date set to 2018-03-27
  • Target version set to Milestone 15

#4 Updated by okurz almost 5 years ago

  • Due date deleted (2018-03-27)
  • Target version changed from Milestone 15 to Milestone 17

sprint13 too full, just as well as M15 and M16

#5 Updated by okurz almost 5 years ago

  • Subject changed from [sle][functional][sle15] yast2_vnc failed to [sle][functional][sle15][yast][y] yast2_vnc failed
  • Due date set to 2018-04-10
  • Target version changed from Milestone 17 to Milestone 15

"y" team has some capacity so plan for more "[yast]" related test fixes earlier.

#6 Updated by okurz almost 5 years ago

  • Due date changed from 2018-04-10 to 2018-03-27

we can even shift to current sprint S13 as it seems there are no [yast] tasks pending there

#7 Updated by riafarov almost 5 years ago

  • Description updated (diff)
  • Due date deleted (2018-03-27)
  • Status changed from New to Blocked
  • Assignee set to okurz

Blocked by https://bugzilla.suse.com/show_bug.cgi?id=1085672 please tarck and reschedule once

#8 Updated by okurz almost 5 years ago

  • Subject changed from [sle][functional][sle15][yast][y] yast2_vnc failed to [sle][functional][sle15][yast][y][easy] yast2_vnc failed - update to current behaviour
  • Due date set to 2018-04-10
  • Status changed from Blocked to Workable
  • Assignee deleted (okurz)
  • Priority changed from Normal to High

bug is VERIFIED FIXED, current test failure: https://openqa.suse.de/tests/1564287#step/yast2_vnc/9 We are down to two failed yast2 ncurses module so we should regard this with high prio

#9 Updated by okurz almost 5 years ago

  • Parent task set to #27074

#10 Updated by cwh almost 5 years ago

  • Difficulty set to easy

#11 Updated by JERiveraMoya almost 5 years ago

  • Assignee set to JERiveraMoya

#13 Updated by JERiveraMoya almost 5 years ago

  • Status changed from Workable to Feedback

#14 Updated by okurz almost 5 years ago

  • Related to action #34015: [functional][y][easy] yast2/vnc doesn't have rules for firewalld -> workaround for bsc#1088647 added

#15 Updated by okurz almost 5 years ago

PR merged.

I triggered yast2_ncurses jobs, please monitor:

please check the sle12sp4 job that was still scheduled on the time of writing. I checked and we have one other ticket for openSUSE yast2_vnc, that is #34015 . Feel free to fix the TW and Leap 15.0 tests as long as it is just the same kind of needles as for SLE15 in this ticket or the other ticket.

#16 Updated by JERiveraMoya almost 5 years ago

  • Status changed from Feedback to Resolved

Thanks for providing the check list. sle12sp4 looks good. leap required a couple of needles, now fixed leap and regarding tw, it is a different error and better to continue in #34015. Resolving this ticket.

Also available in: Atom PDF