Project

General

Profile

action #68708

action #66394: [epic][y] Enable VNC+SSH Installations on aarch64

[functional][y] Generate support_server image for SLES on aarch64

Added by riafarov about 1 month ago. Updated 1 day ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
2020-07-07
Due date:
2020-08-11
% Done:

0%

Estimated time:
8.00 h
Difficulty:
Duration: 26

Description

openQA doesn't support cross-platform MM tests, so we cannot use 64bit support server.

See parent ticket for motivation.

Some hints for SLES image generation:
https://gitlab.suse.de/hsehic/qa-css-docs/blob/master/openqa/README.md#creating-a-supportserver-image

64bit jobs using support server: https://openqa.suse.de/tests/4428137 and https://openqa.suse.de/tests/4428135

Acceptance criteria

  1. support_server image generation is trivial in case we need update or image for other architectures
  2. support_server image provides all functionality for multimachine ssh and vnc remote installations on aarch64

Hints

So from the previous ticket (#9576) some points for image generation on TW:

  • Get latest qcow2 from TW/SLES create_hdd_gnome
  • Install pattern dhcp_dns_server
  • Switch from Network Manager to Wicked
  • Disable firewall
  • To avoid dimming of the screen, turn off gnome screensaver gsettings set org.gnome.desktop.session idle-delay 0 and turn off gnome suspend gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'
  • In job conf delete QEMUVGA and use VIRTIO_CONSOLE=1

Related issues

Related to openQA Tests - action #69349: [functional][y] setting QEMUVGA=cirrus invalid for aarch64 on remote_vnc_controller: auto_review:"qemu-system-aarch64: Cirrus VGA not available"Rejected2020-07-25

History

#1 Updated by riafarov 22 days ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Estimated time set to 8.00 h

#2 Updated by ybonatakis 22 days ago

  • Status changed from Workable to In Progress
  • Assignee set to ybonatakis

#4 Updated by ybonatakis 17 days ago

  • Status changed from In Progress to Feedback

I provide a script in the PR that use autoyast to generate the supportserver. i expect this will make it easier in the future to generate a qcow for aarch and x86_64. We need to edit the script for other archs.

I tried to verify that this would work with the remote_ssh but apparently the test needs adjustment. i created https://progress.opensuse.org/issues/69142. i have modified the yaml to use the bootloader_start module but uefi+MM does not work because of missing parameters.

We (with @joaquin) test the qcow in the remote ssh. The results here. I used Full media as i had network issues on the target machine in the Online media.

However i expect the qcow to be suitable for remote_vnc as well. If not, we can easily regenerate an image with the provided xml or use the script with another xml to get another qcow if we want.

The supportserver is using SLE15-SP2 as base image (GMC)

#5 Updated by ybonatakis 16 days ago

  • Status changed from Feedback to In Progress

#6 Updated by ybonatakis 16 days ago

Notes from experiments we wanted to explore:

#7 Updated by riafarov 10 days ago

FYI: https://progress.opensuse.org/issues/69349 I guess we can revert changes made to the dev job group for now.

#8 Updated by ybonatakis 9 days ago

The alternative is to use create_hdd_gnome adding one module that already exists to do the configuration. The image that it is created by this job contains all the necessary patters(base minimal_base x11 x11_enhanced and gnome_basic). So nothing to do with it.
Although we need to install some packages

apache2 tftp dhcp-server bind yast2-iscsi-lio-server xrdp

openssh, nfs-client is already installed.

I was thinking if you could provide them with test_data or some other way but for now i have defined it as a list in the module.
wicked is used and i use setup_static_mm_network to ensure that.
there is no requirement to disable the firewall for MM test so it remains enabled.

remote_ssh seems to be able to boot and connect.
remote_vnc can also boot but i havent test the connectivity so far. I dont know why we use QEMUVGA with cirrus but it does not work

#9 Updated by riafarov 9 days ago

  • Due date changed from 2020-07-28 to 2020-08-11

#10 Updated by okurz 9 days ago

  • Related to action #69349: [functional][y] setting QEMUVGA=cirrus invalid for aarch64 on remote_vnc_controller: auto_review:"qemu-system-aarch64: Cirrus VGA not available" added

#11 Updated by ybonatakis 2 days ago

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10780 i have created another PR to not messed up with the changes that i am asked (to avoid a bug mess).
Next step is to see where to run the job

#12 Updated by ybonatakis 1 day ago

  • Status changed from In Progress to Feedback

remains to setup the jobs in the development group

Also available in: Atom PDF