action #44468
open
[qe-core][functional][tools] Proper handling of assets for svirt workers
Added by SLindoMansilla over 5 years ago.
Updated 6 months ago.
Target version:
SUSE QA - Milestone 30
Description
Motivation / Observation¶
Trying to verify a SR to fix the systemd-testsuite, I was blocked because OSD workers and QSF shared workers were malfunctioning.
The problem with QSF shared workers is that the needed qcow2 image was missing:
Because
- openqa.suse.de:/var/lib/openqa/share/factory
was NFS-mounted into
- s390p8.suse.de:/var/lib/openqa/share/factory
And the image were already cleaned up from openqa.suse.de:/var/lib/openqa/share/factory.
QSF shared-workers (shared-workers.qa.suse.de) have CACHEDIRECTORY configured, but this directory is ignored by the svirt backend.
Only some changes in the test code are necessary to take CACHEDIRECTORY into account, but some configuration is needed at infrastructure level.
- shared-workers.qa.suse.de:/var/lib/openqa/cache
needs to be made available from
- s390p8.suse.de:/var/lib/openqa/cache
Acceptance criteria¶
- AC: SUT's host machine on svirt backends (ie. s390p8.suse.de), which have a jump host (ie. shared-workers.qa.suse.de) with configured CACHEDIRECTORY, have available assets from that CACHEDIRECTORY.
Suggestions¶
Files
- Related to action #36754: [qe-core][functional][systemd][medium] test fails in systemd_testsuite - needs further investigation added
- Related to deleted (action #36754: [qe-core][functional][systemd][medium] test fails in systemd_testsuite - needs further investigation)
- Blocks action #36754: [qe-core][functional][systemd][medium] test fails in systemd_testsuite - needs further investigation added
In the attached draft can be seen the current status (black, blue, green) and the expected status (red).
- Status changed from New to In Progress
- Assignee set to SLindoMansilla
- Status changed from In Progress to New
What was done¶
The already merged fix was to look for assets in the right machine. Before, the test was looking for assets on the worker machine. On OSD it was working because the assets were NFS mounted from the webui across the worker and the SUT's host.
On shared-workers.qa.suse.de we don't have the NFS share mounted, which caused the test to not find the assets.
This is fixed now in this PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6191
What is still missing?¶
The worker cache is not propagated to the svirt remote machine, so the assets are missing there.
We need to discuss how to resolve this problem.
My proposal is to NFS-mount the cache directory from the worker into the SUT's host.
After that, some changes in the test code are needed: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6253
- Target version set to Milestone 22
- Target version changed from Milestone 22 to Milestone 24
- Assignee deleted (
SLindoMansilla)
- Target version changed from Milestone 24 to Milestone 25
Let's delay the work on this one a bit further.
- Priority changed from Normal to High
- Status changed from New to Workable
- Assignee set to mgriessmeier
As spoken in the grooming meeting, we want to NFS mount the directory
from shared-workers.qa.suse.de:/var/lib/openqa/cache
into [zVM|zKVM|sKVM|XEN]:/var/lib/openqa/cache
- Status changed from Workable to In Progress
- Target version changed from Milestone 25 to Milestone 26
- Status changed from In Progress to Feedback
- Target version changed from Milestone 26 to Milestone 27
SLindoMansilla wrote:
As spoken in the grooming meeting, we want to NFS mount the directory
from shared-workers.qa.suse.de:/var/lib/openqa/cache
into [zVM|zKVM|sKVM|XEN]:/var/lib/openqa/cache
mounted on s390p8 - please check if it's working as expected, then I will do the rest
- Target version changed from Milestone 27 to Milestone 28
let's rediscuss in grooming
- Target version changed from Milestone 28 to Milestone 30
needs to be discussed offline
- Status changed from Feedback to Workable
- Assignee changed from mgriessmeier to SLindoMansilla
Tasks¶
- Look what was done since 8 months regarding NFS on shared-workers
- Refine the ticket in a grooming meeting if more work has to be done
Sergio, do you really plan to work on this ticket?
Also: xen and hyperv are also part of the svirt thing, i guess all this could be unified, as the directories where things are copied, is the same.
szarate wrote:
Sergio, do you really plan to work on this ticket?
Also: xen and hyperv are also part of the svirt thing, i guess all this could be unified, as the directories where things are copied, is the same.
Yes, I "plan" (have the intention) to look into all tickets I have assigned, but I cannot promise any date...
So, if you feel like doing it, please take over. If not, be sure that "some day" I will continue working on this.
- Assignee deleted (
SLindoMansilla)
- Priority changed from High to Normal
- Subject changed from [functional][u][labs] Proper handling of assets for svirt workers to [functional][u][tools] Proper handling of assets for svirt workers
- Subject changed from [functional][u][tools] Proper handling of assets for svirt workers to [qe-core][functional][tools] Proper handling of assets for svirt workers
- Blocks deleted (action #36754: [qe-core][functional][systemd][medium] test fails in systemd_testsuite - needs further investigation)
- Related to action #36754: [qe-core][functional][systemd][medium] test fails in systemd_testsuite - needs further investigation added
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
- Description updated (diff)
Also available in: Atom
PDF
