From f40111fdc8f961ead211a5b0186bef2ea88b4c91 Mon Sep 17 00:00:00 2001
From: Julien Leduc <julien.leduc@cern.ch>
Date: Mon, 28 Mar 2022 22:43:58 +0200
Subject: [PATCH] Resolve "CTA CI crashing for some k8 configurations": CTA CI
 can now run with hostNetwork configuration for ctaeos pod.

---
 .../docker/ctafrontend/cc7/opt/run/bin/ctaeos-mgm.sh         | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/continuousintegration/docker/ctafrontend/cc7/opt/run/bin/ctaeos-mgm.sh b/continuousintegration/docker/ctafrontend/cc7/opt/run/bin/ctaeos-mgm.sh
index 70fceb9185..bfbd5ff3af 100755
--- a/continuousintegration/docker/ctafrontend/cc7/opt/run/bin/ctaeos-mgm.sh
+++ b/continuousintegration/docker/ctafrontend/cc7/opt/run/bin/ctaeos-mgm.sh
@@ -69,7 +69,10 @@ yes | cp -r /opt/ci/ctaeos/etc /
 
 eoshost=`hostname -f`
 
-EOS_INSTANCE=`hostname -s`
+# All our scripts are set to exclusively use ctaeos instance name:
+# notably the following directory: `/eos/ctaeos` is hardcoded almost everywhere
+#EOS_INSTANCE=`hostname -s`
+EOS_INSTANCE=ctaeos
 TAPE_FS_ID=65535
 CTA_BIN=/usr/bin/eoscta_stub
 CTA_XrdSecPROTOCOL=sss
-- 
GitLab