Project

General

Profile

Actions
Copy link

action #54251

closed

[functional][u][s390x] test fails in welcome: Installer can not start in Xvnc version which is installed on worker - broken connection

Added by mgriessmeier almost 5 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
mgriessmeier
Category:
Infrastructure
Target version:
-
Start date:
2019-07-15
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-12-SP5-Server-DVD-s390x-ssh-X@s390x-zVM-vswitch-l3 fails in
welcome

Test suite description

Maintainer: okurz, mgriessmeier

Conduct an installation using ssh with X-Forwarding. Might only be effective for s390x and spvm

Reproducible

Fails since (at least) Build 0211

Expected result

Last good: 0211 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by mgriessmeier almost 5 years ago

  • Subject changed from [functional][u][s390x] test fails in welcome, ssh installer seems to die - but not reproducible manually so assumed openQA issue to [functional][u][s390x] test fails in welcome, ssh installer seems to die - but not reproducible manually so assumed openQA issue
  • Category changed from Bugs in existing tests to Infrastructure
  • Status changed from New to In Progress
  • Assignee changed from mgriessmeier to nicksinger

works with Xvnc Version 1.6.0 - X server release 11803000

does not work with

Xvnc TigerVNC 1.9.0 - built ??? ?? ???? ??:??:??
Copyright (C) 1999-2018 TigerVNC Team and many others (see README.rst)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12003000, The X.Org Foundation
Actions
Copy link
 #2

Updated by mgriessmeier almost 5 years ago

  • Subject changed from [functional][u][s390x] test fails in welcome, ssh installer seems to die - but not reproducible manually so assumed openQA issue to [functional][u][s390x] test fails in welcome: Installer can not start in Xvnc version which is installed on worker - broken connection
Actions
Copy link
 #3

Updated by nicksinger almost 5 years ago

I was able to reproduce this on several machines running the newer XVnc version.

  1. Start XVnc like the worker does: Xvnc -depth 16 -SecurityTypes None -ac :1337
  2. Start a console in there: DISPLAY=:1337 xterm
  3. Connect over vnc to this display: vncviewer localhost:7237
  4. Connect to the SUT over ssh with X-forwarding inside the VNC display: ssh root@s390vsw157 -X
  5. Start yast with yast.ssh and observe how it crashes/does not start

Until now I was unable to find any logs to pinpoint the component which is responsible for this. I guess since other X applications (glxgears, firefox, etc) work just fine this is a combination issue with libyui and X/Xvnc.

Actions
Copy link
 #4

Updated by coolo almost 5 years ago

As discussed with Nick: I rather suspect the openssh client, not so much Xvnc. Please try if you can start ssh -X installations when coming from 15.

Actions
Copy link
 #6

Updated by okurz over 4 years ago

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

This bug is still referenced in a failing openQA test: ssh-X@s390x-zVM-vswitch-l3
https://openqa.suse.de/tests/3204907

Actions
Copy link
 #7

Updated by okurz over 4 years ago

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

This bug is still referenced in a failing openQA test: ssh-X@s390x-zVM-vswitch-l3
https://openqa.suse.de/tests/3262572

Actions
Copy link
 #8

Updated by SLindoMansilla over 4 years ago

PR with workaround suggested in bug ticket: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8287
Merged.

We should use this ticket to re-needle the test suite, since the workaround causes different window borders: https://openqa.suse.de/tests/3288459#step/welcome/2

Should this land into U-Team product backlog?

Actions
Copy link
 #9

Updated by nicksinger over 4 years ago

  • Status changed from In Progress to Feedback
  • Assignee changed from nicksinger to mgriessmeier

SLindoMansilla wrote:

PR with workaround suggested in bug ticket: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8287
Merged.

Nice. I'll assign the ticket to @mgriessmeier and set it to feedback since there is not much we can do from the tools-team and a workaround is already merged.

SLindoMansilla wrote:

We should use this ticket to re-needle the test suite, since the workaround causes different window borders: https://openqa.suse.de/tests/3288459#step/welcome/2

Should this land into U-Team product backlog?

I'd not pollute this bug here too much and better offload the re-needling-task into a related ticket.

Actions
Copy link
 #10

Updated by SLindoMansilla about 4 years ago

Should this ticket be marked as resolved?

Actions
Copy link
 #11

Updated by SLindoMansilla almost 4 years ago

  • Status changed from Feedback to Resolved

Was verified on OSD and no new complaint

Actions
Copy link

Also available in: Atom PDF