Project

General

Profile

action #11564

s390x: add SSH+GUI as frontend to the Installation process

Added by maritawerner about 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
New test
Start date:
2016-06-15
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Difficulty:
Duration:

Description

as discussed with Matthias


Subtasks

action #12348: ssh-X has some issues with resizingResolvedokurz


Related issues

Related to openQA Tests - action #7614: sle12 - figure out/impliment ssh+X, ssh+noX, and vnc installationsResolved2015-05-22

History

#1 Updated by mgriessmeier about 4 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 100

#2 Updated by mgriessmeier about 4 years ago

current state:
test fails in reconnect_s390

see e.g. https://openqa.suse.de/tests/392299
investigating

#3 Updated by mgriessmeier about 4 years ago

Since we can not start a vnc server in installation (e.g. VNC=1, it would install via VNC), we don't have a VNC server running after reboot
Due to that, we don't have a x11-console, which is fine because this should be the defined use case for ssh-X installations
I set the DESKTOP variable to textmode, which should turn this red dot to a green dot when the next build shows up

#4 Updated by mgriessmeier about 4 years ago

  • Status changed from In Progress to Resolved

verified test run on local openQA-instance:
http://opeth.suse.de/tests/2087

resolved for now, please reopen if issue occurs again

#5 Updated by mgriessmeier about 4 years ago

  • Status changed from Resolved to In Progress

test is currently failing in change_desktop -> https://openqa.suse.de/tests/398002

But I had an interesting discussion with okurz about this test, whether it is actually necessary to test the full installation process for this installation frontend or if it would be enough to just be sure, that the installer starts - because after that there is nothing different to vnc installation method.
And it is not that easy to implement this whole process on s390 into openQA

so question to marita:
what do you think about narrowing this test down to "test ssh-X until YaST Installation Window shows up and then exit with status=passed"?

#6 Updated by maritawerner about 4 years ago

Discussed that briefly with okurz and mgriessmeier and I am fine with the proposed solution.

#7 Updated by okurz about 4 years ago

Following up on the previous comments the test suite ssh-X was edited in the database to accomodate DESKTOP=textmode and PATTERNS=minimal,base so it should look like http://opeth.suse.de/tests/2087 on osd after the next iso gets triggered. The worker won't be able to connect to the SUT in "first_boot" because there is no vnc server available in the SUT but the result will be regarded as success. An alternative would have been to adjust the needles "gnome-selected" to accomodate the tag "ENV-DESKTOP-textmode" and add a new needle "x11-selected" with same tag.

#8 Updated by okurz about 4 years ago

  • Target version changed from 168 to Milestone 3

#9 Updated by okurz about 4 years ago

  • Status changed from In Progress to Resolved

verified working in sle-12-SP2-Server-DVD-s390x-Build1551-ssh-X@s390x-zVM-vswitch-l3 https://openqa.suse.de/tests/400288
recent jobs fail for other reasons

#10 Updated by okurz about 4 years ago

  • Related to action #7614: sle12 - figure out/impliment ssh+X, ssh+noX, and vnc installations added

Also available in: Atom PDF