[openqa-tests/sam/ci] Use custom openqa_worker container to workaround virtio issue

[Sam Thursfield <sthursfield src gnome org>]

commit af99ec2391e9b60af08b3fb7e090694ef13a79bc
Author: Sam Thursfield <sam thursfield codethink co uk>
Date:   Wed Sep 14 11:28:40 2022 +0100

    Use custom openqa_worker container to workaround virtio issue
    
    Hopefully we can stick with upstream images once the necessary QEMU
    virtio support is added back to the openqa_worker container:
    https://github.com/os-autoinst/openQA/pull/4804
    
    Related: https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/517

 .gitlab-ci.yml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)
---
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index d408fbf..e88de80 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -14,7 +14,10 @@ stages:
 test-s3-image-x86_64:
   stage: test
   image:
-    name: registry.opensuse.org/devel/openqa/containers15.4/openqa_worker:latest
+    # We must use this custom image until upstream merges and releases
+    # https://github.com/os-autoinst/openQA/pull/4804.
+    name: quay.io/ssssam0/openqa_worker:15.4-virtio-vga
+    #name: registry.opensuse.org/devel/openqa/containers15.4/openqa_worker:latest
     entrypoint: ["/bin/bash", "-c"]
   variables:
     IMAGE: installer.iso