Project

General

Profile

Actions

action #70828

closed

[y][opensuse] test fails in yast2_vnc when verifying service listening

Added by JERiveraMoya over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - SLE 15 SP3
Start date:
2020-09-02
Due date:
2020-09-22
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-ppc64le-yast2_ncurses@ppc64le fails in
yast2_vnc

We could try to isolate the test module (it doesn't have yaml schedule) and investigate. We don't have this module schedule for SLE.

Test suite description

Maintainer: qsf-y Test for yast2 UI, ncurses only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests.
riafarov set TIMEOUT_SCALE to improve stability of the test.

Reproducible

Fails since (at least) Build 20200801

Expected result

Last good: 20200730 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by JERiveraMoya over 3 years ago

  • Subject changed from [y] test fails in yast2_vnc when verifying service listening to [y][opensuse] test fails in yast2_vnc when verifying service listening
  • Priority changed from Normal to Low
Actions #2

Updated by riafarov over 3 years ago

  • Priority changed from Low to High
  • Target version set to SLE 15 SP3

This also fails for TW: https://openqa.opensuse.org/tests/1380615#step/yast2_vnc/28

Seems to be a bug:
[ 1286.678076] systemd[1]: Started VNC manager.
[ 1286.697026] systemd[1]: Reached target System VNC service.
[ 1286.704508] systemd[6573]: vncmanager.service: Failed to execute command: No such file or directory
[ 1286.706344] systemd[6573]: vncmanager.service: Failed at step EXEC spawning /usr/lib/vnc/with-vnc-key.sh: No such file or directory
[ 1286.715499] systemd[1]: vncmanager.service: Main process exited, code=exited, status=203/EXEC
[ 1286.717089] systemd[1]: vncmanager.service: Failed with result 'exit-code'.

Actions #3

Updated by riafarov over 3 years ago

  • Assignee set to JERiveraMoya

@Joaquin will file a bug and we can resolve it, unless there is something else to do here.

Actions #5

Updated by JERiveraMoya over 3 years ago

  • Status changed from New to Blocked
Actions #6

Updated by JERiveraMoya over 3 years ago

  • Status changed from Blocked to Resolved

Fixed in TW

Actions

Also available in: Atom PDF