coordination #66394
closed
[epic][y] Enable VNC+SSH Installations on aarch64
Added by ggardet_arm over 4 years ago.
Updated about 4 years ago.
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
- Related to coordination #9576: [epic][opensuse][sle][functional][y] VNC+SSH Installations added
- Description updated (diff)
- 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?
I tried to use opensuse-Tumbleweed-*-gnome@*.qcow2 image instead of the fixed image, but it fails for both aarch64 and x86_64:
- 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
Note: we can also use create_hdd_gnome_wicked as a base image instead of create_hdd_gnome.
- 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
- Due date changed from 2020-07-28 to 2020-08-11
due to changes in a related task: #69142
- Due date changed from 2020-08-11 to 2020-08-25
due to changes in a related task: #68714
- Description updated (diff)
- Due date changed from 2020-08-25 to 2020-09-08
due to changes in a related task: #69865
- Due date changed from 2020-09-08 to 2020-09-22
due to changes in a related task: #68711
- Due date changed from 2020-09-22 to 2020-10-06
due to changes in a related task: #68717
Could we move forward for openSUSE tasks, please?
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.
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.
- Project changed from openQA Tests (public) to qe-yam
- Category deleted (
New test)
- Project changed from qe-yam to openQA Tests (public)
- Category set to New test
- Tracker changed from action to coordination
- Project changed from openQA Tests (public) to qe-yam
- Category deleted (
New test)
- Status changed from New to In Progress
- Status changed from In Progress to Closed
Also available in: Atom
PDF