[gnome-build-meta/sam/openqa-container-workaround] openqa: Use custom openqa_worker container to workaround virtio issue




commit 11fd52474cadb3ddcb67fb5abbe47106f77496c3
Author: Sam Thursfield <sam thursfield codethink co uk>
Date:   Tue Sep 13 16:09:52 2022 +0100

    openqa: 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 fcf8d8c0d..7e951da27 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -434,7 +434,10 @@ cve_report:
 test-iso-installer-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"]
   when: manual
   variables:


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]