Project

General

Profile

coordination #66394

[epic][y] Enable VNC+SSH Installations on aarch64

Added by ggardet_arm 12 months ago. Updated 6 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
2020-07-07
Due date:
2020-10-20
% Done:

100%

Estimated time:
(Total: 28.00 h)

Description

On https://progress.opensuse.org/issues/9576 VNC+SSH Installations have been enabled for x86_64 only.

I tried to enable them for aarch64 on 'Development Tumbleweed' project, but the x86 test uses support_server_tumbleweed@64bit.qcow2. But there is no support_server_tumbleweed@aarch64.qcow2 available for aarch64.

How is built this support_server_tumbleweed@64bit.qcow2 and why a proper image created from current Tumbleweed snapshot is not used instead?

Image names in the fixed directory:

  • openqa_support_server_sles15sp2_aarch64_gnome.qcow2
  • openqa_support_server_sles15sp2_aarch64_textmode.qcow2

Subtasks

action #68708: [functional][y] Generate support_server image for SLES on aarch64Resolvedybonatakis

action #68711: [functional][y] Generate support_server image for openSUSE on aarch64Closedriafarov

action #68714: [functional][y] Enable ssh MM installations on aarch64 for SLESResolvedJRivrain

action #68717: [functional][y] Enable vnc MM installation on aarch64 for TWClosedriafarov

action #69142: [y] Adjust bootloader for MM on aarch64Resolvedybonatakis

action #69865: [functional][y] Enable vnc MM installations on aarch64 for SLESResolvedriafarov

action #73081: [functional][y] Enable ssh MM installation on aarch64 for TWClosedriafarov


Related issues

Related to openQA Tests - coordination #9576: [epic][opensuse][sle][functional][y] VNC+SSH InstallationsResolved2019-05-292020-03-24

History

#1 Updated by ggardet_arm 12 months ago

  • Related to coordination #9576: [epic][opensuse][sle][functional][y] VNC+SSH Installations added

#2 Updated by ggardet_arm 12 months ago

  • Description updated (diff)

#3 Updated by ggardet_arm 9 months ago

  • Priority changed from Normal to High

How support_server_tumbleweed*.qcow2 image is built? Could we use opensuse-Tumbleweed-*-gnome@*.qcow2 image instead to be arch agnostic?

#4 Updated by ggardet_arm 9 months ago

I tried to use opensuse-Tumbleweed-*-gnome@*.qcow2 image instead of the fixed image, but it fails for both aarch64 and x86_64:

#5 Updated by riafarov 9 months ago

  • Subject changed from VNC+SSH Installations broken on aarch64 to [epic][y] Enable VNC+SSH Installations on aarch64
  • Category set to New test
  • Assignee set to riafarov
  • Target version set to future

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

  • Get latest qcow2 from TW 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

#6 Updated by ggardet_arm 9 months ago

Note: we can also use create_hdd_gnome_wicked as a base image instead of create_hdd_gnome.

#7 Updated by riafarov 9 months ago

  • Due date set to 2020-07-28
  • Start date changed from 2020-05-04 to 2020-07-07

due to changes in a related task: #68708

#8 Updated by riafarov 9 months ago

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

due to changes in a related task: #69142

#9 Updated by riafarov 8 months ago

  • Due date changed from 2020-08-11 to 2020-08-25

due to changes in a related task: #68714

#10 Updated by riafarov 8 months ago

  • Description updated (diff)

#11 Updated by riafarov 8 months ago

  • Due date changed from 2020-08-25 to 2020-09-08

due to changes in a related task: #69865

#12 Updated by riafarov 8 months ago

  • Due date changed from 2020-09-08 to 2020-09-22

due to changes in a related task: #68711

#13 Updated by riafarov 8 months ago

  • Due date changed from 2020-09-22 to 2020-10-06

due to changes in a related task: #68717

#14 Updated by ggardet_arm 7 months ago

Could we move forward for openSUSE tasks, please?

#15 Updated by riafarov 7 months ago

ggardet_arm wrote:

Could we move forward for openSUSE tasks, please?

It is already scheduled for this sprint and the next one. And I also tried to make it clear, that our priority is SLES, where we have this scenario enabled.

#16 Updated by ggardet_arm 7 months ago

riafarov wrote:

ggardet_arm wrote:

Could we move forward for openSUSE tasks, please?

It is already scheduled for this sprint and the next one. And I also tried to make it clear, that our priority is SLES, where we have this scenario enabled.

Yes, that's well understood that SLE is the priority and you wanted to enable those scenarios in SLE first, but I asked because SLE tests are now done, so openSUSE tests are ready to be worked on. ;)
Thanks for scheduling them on the next sprints.

#17 Updated by riafarov 7 months ago

  • Project changed from openQA Tests to qe-yast
  • Category deleted (New test)

#18 Updated by riafarov 6 months ago

  • Project changed from qe-yast to openQA Tests
  • Category set to New test

#19 Updated by szarate 6 months ago

  • Tracker changed from action to coordination

#21 Updated by riafarov 6 months ago

  • Project changed from openQA Tests to qe-yast
  • Category deleted (New test)
  • Status changed from New to In Progress

#22 Updated by riafarov 6 months ago

  • Status changed from In Progress to Closed

Also available in: Atom PDF