Set cross-version-config-tests to allow_failure in CI

The December releases suffer from the ns2/managed1.conf file not being
in the mkeys extra_artifacts. This manifests only when pytest is run
with the --setup-only option, which is the case in the
cross-version-config-tests CI job. The original issue is fixed in !9815,
but the fix will be effective only when subsequent releases are out.

(cherry picked from commit 97a9d7287c075b55cd599d98e68e04121b854a1d)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 80aea6716545dd8dfe5061a6fdde69da661bc8e5..2c98fd0947cf6a3d2e1a0f0e21426434399a9a77 100644 (file)
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -763,6 +763,12 @@ cross-version-config-tests:
     untracked: true
     expire_in: "1 day"
     when: always
+  # Changes in the January milestone necessitate allowing this job to fail. The
+  # "soft failure" should be reverted when January releases are published.
+  # - #4261 introduced extra artifacts check but missed a file visible only in
+  #   this job. This is fixed in !9815 but present in December releases.
+  #   System test affected: mkeys.
+  allow_failure: true
 
 # Jobs for regular GCC builds on Alpine Linux 3.21 (amd64)