s390x: add SSH+GUI as frontend to the Installation process
as discussed with Matthias
#1 Updated by mgriessmeier about 4 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 100
#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
#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"?
#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
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.