Project

General

Profile

action #33865

action #33859: [sles][functional][saga][s390x][u] Review s390x Bugs found by IBM and see what can be implemented in the future

action #33862: [sles][functional][epic][s390x][yast][y] Review and extend test coverage of YaST2 modules on s390x

[sles][functional][s390x][easy][y] Enable yast2_ncurses testsuite for s390x

Added by mgriessmeier about 2 years ago. Updated 22 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
New test
Target version:
SUSE QA tests - Milestone 18
Start date:
2018-03-27
Due date:
% Done:

0%

Estimated time:
2.00 h
Difficulty:
easy
Duration:

Description

User story

we want to check how yast modules behave on s390x

Acceptance Criteria

AC1: yast2_ncurses testsuite is running on o.s.d in functional

Tasks

  1. yast2_ncurses testsuite is running on o.s.d in test-development job group on a regular base to gather statistics how stable test is
  2. if stable enough, move to functional, if not create new tickets accordingly
  3. Evaluate business value, if used by any of the customers, if yes which modules exactly

Related issues

Blocked by openQA Project - action #34003: [tools] Better logging and error handling in case of remote console connections in consoles or backends, e.g. sshResolved2018-03-29

Blocked by openQA Tests - action #33202: [sle][functional][s390x][zkvm][u][hard] test fails in boot_to_desktop - still insufficient error reporting, black screen with mouse cursor - we all hate it (was: I hate it)Resolved2018-03-132018-08-14

Copied to openQA Tests - action #39329: [sles][functional][s390x][y][epic] FIx yast2_ncurses testsuite for s390xResolved2018-08-082018-11-20

History

#1 Updated by okurz about 2 years ago

  • Subject changed from [sles][functional][s390x][easy] Enable yast2_ncurses testsuite for s390x to [sles][functional][s390x][easy][yast][y] Enable yast2_ncurses testsuite for s390x

#2 Updated by riafarov about 2 years ago

  • Subject changed from [sles][functional][s390x][easy][yast][y] Enable yast2_ncurses testsuite for s390x to [sles][functional][s390x][easy][y] Enable yast2_ncurses testsuite for s390x
  • Description updated (diff)
  • Status changed from New to Workable

#3 Updated by cwh about 2 years ago

  • Difficulty set to easy

#4 Updated by riafarov about 2 years ago

  • Due date changed from 2018-04-10 to 2018-04-24

#5 Updated by okurz about 2 years ago

  • Due date changed from 2018-04-24 to 2018-06-05
  • Target version changed from Milestone 15 to Milestone 16

not enough capacity in S15-S17. We think it's easy but new test can always have an impact on other stuff. So "easy" but not "trivial".

#6 Updated by okurz about 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to okurz

Triggered once to check feasibility

$ openqa_clone_job_osd --skip-chained-deps 1650904 TEST=yast2_ncurses Y2UITEST_NCURSES=1 EXTRATEST= _GROUP=0

-> https://openqa.suse.de/tests/1656222

#7 Updated by okurz about 2 years ago

  • Blocked by action #34003: [tools] Better logging and error handling in case of remote console connections in consoles or backends, e.g. ssh added

#8 Updated by okurz about 2 years ago

  • Status changed from In Progress to Blocked

hmpf, failed in https://openqa.suse.de/tests/1656222#step/boot_to_desktop/22 with a black screen trying to conduct most likely a remote connection but it is not obvious what is the problem here. blocked by #34003

#9 Updated by riafarov almost 2 years ago

  • Due date changed from 2018-06-05 to 2018-07-03
  • Target version changed from Milestone 16 to Milestone 17

Do not expect to get unblocked in S19, moving to S20

#10 Updated by mloviska almost 2 years ago

  • Status changed from Blocked to Workable

https://progress.opensuse.org/issues/34003 has been resolved. Unblocking

#11 Updated by okurz almost 2 years ago

  • Status changed from Workable to In Progress

yes, could be tested against SLE12SP4 or latest SLE15.

$ openqa_clone_job_osd --skip-chained-deps 1749719 TEST=yast2_ncurses Y2UITEST_NCURSES=1 EXTRATEST= _GROUP="Test Development: SLE 15"
Created job #1759484: sle-15-Installer-DVD-s390x-Build665.2-extra_tests_on_gnome@s390x-kvm-sle12 -> https://openqa.suse.de/t1759484

-> https://openqa.suse.de/tests/1759484 failed in https://openqa.suse.de/tests/1759484#step/boot_to_desktop/17

#12 Updated by okurz almost 2 years ago

  • Blocked by action #33202: [sle][functional][s390x][zkvm][u][hard] test fails in boot_to_desktop - still insufficient error reporting, black screen with mouse cursor - we all hate it (was: I hate it) added

#13 Updated by okurz almost 2 years ago

  • Status changed from In Progress to Blocked

#14 Updated by okurz almost 2 years ago

  • Target version changed from Milestone 17 to Milestone 17

#15 Updated by JERiveraMoya almost 2 years ago

  • Estimated time set to 2.00 h

#16 Updated by riafarov almost 2 years ago

  • Due date changed from 2018-07-03 to 2018-08-14

#17 Updated by okurz almost 2 years ago

  • Target version changed from Milestone 17 to Milestone 18

#18 Updated by riafarov almost 2 years ago

  • Description updated (diff)

#19 Updated by mgriessmeier almost 2 years ago

  • Status changed from Blocked to Workable
  • Assignee deleted (okurz)

blockers are resolved afaics, so let's put this back to workable

#20 Updated by riafarov almost 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to riafarov

#22 Updated by riafarov almost 2 years ago

  • Copied to action #39329: [sles][functional][s390x][y][epic] FIx yast2_ncurses testsuite for s390x added

#23 Updated by riafarov almost 2 years ago

https://progress.opensuse.org/issues/39329 follow-up ticket to adjust tests created.

#24 Updated by riafarov almost 2 years ago

  • Status changed from In Progress to Resolved

So, as for business value, I've used bugzilla and http://houtsapps01.us.netiq.corp/siebelmatic2/?page=team&searchterm=12 support ticket system to identify used modules.
We are missing a lot of information about product usage, but what I was able to identify is that 'yast dump' YaST module is used on s390x. Majority of issues address installation, so it seems that servers are rarely configured manually or there are no issues with tooling on s390, or everything is configured without YaST modules.

#25 Updated by SLindoMansilla 22 days ago

  • Due date deleted (2018-08-14)

Also available in: Atom PDF