Project

General

Profile

Actions

action #39332

closed

coordination #39329: [sles][functional][s390x][y][epic] FIx yast2_ncurses testsuite for s390x

[functional][y][easy] adjust or disable yast2_vnc for s390x

Added by riafarov over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 19
Start date:
2018-08-08
Due date:
2018-10-09
% Done:

0%

Estimated time:
2.00 h
Difficulty:
easy

Description

Observation

on zKVM we have VNC port opened by default: https://openqa.suse.de/tests/1907206#step/yast2_vnc/10
Which is not the case on x86: https://openqa.suse.de/tests/1903782#step/yast2_vnc/7

Therefore we need to adjust the test for s390x for the defined behavior, or disable it, as we use vnc and cannot close ports, as it will kill test run.

openQA test in scenario sle-12-SP4-Server-DVD-s390x-yast2_ncurses@s390x-kvm-sle12 fails in
yast2_vnc

Acceptance criteria

  • AC1: yast2_vnc does not fail on s390x in the yast2_ncurses scenario

Suggestions

  • As for s390x remote administration is actually important we should try to fix the test module. If that is not feasible with a reasonable effort exclude the module from the test plan on s390x with a good comment why.
  • As VNC access is enabled by default on the s390x backend as for other remote backends we have to accept a different starting situation in the test module and also must not disable the remote administration. It is recommended to simply exit the test module early on the remote backends that have VNC administration enabled, e.g. instead of the send_key 'alt-a' to enable the remote administration return from the test module

Further details

Always latest result in this scenario: latest


Related issues 1 (0 open1 closed)

Related to qe-yam - action #41546: [functional][y] Change architecture checks with functionality of the #33388 to detect VNC installationResolvedsyrianidou_sofia2018-09-25

Actions
Actions

Also available in: Atom PDF