aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorOliver Smith <osmith@sysmocom.de>2019-10-30 08:49:08 +0100
committerosmith <osmith@sysmocom.de>2019-10-30 13:00:29 +0000
commitb6ab37d9649e5659ea04d9abbd941b1b9074c2a7 (patch)
treed00731e81fe971c0552daed58aa23e88d136d47f
parent436fe0c1438a8915c3fc21ab5bd092bfb369d094 (diff)
repo-install-test: disable osmo-ggsn service
OsmoGGSN is not able to use the tun4 device from the default config in docker. Since the more strict config checking in [1], it does not just report a warning, but fails to start: <0002> ggsn.c:189 APN(internet): Opening TUN device tun4 <0001> tun.c:184 errno=2/No such file or directory open() failed <0002> ggsn.c:191 APN(internet): Failed to configure tun device Error occurred during reading the below line: no shutdown Failed to open config file: '/etc/osmocom/osmo-ggsn.cfg' Fix the repo install test jenkins job by not checking osmo-ggsn anymore. In theory, we could probably create the tun device on the host, and mount it inside the docker container. But that would require some additional logic to clean it up properly, and it does not seem worth the effort right now. [1] libosmocore Ic9c1b566ec4a459f03e6319cf369691903cf9d00 Change-Id: I15c7a2f38a21cd96c9852ad26f4b4a81798e6593
-rwxr-xr-xdebian-repo-install-test/testdata/repo-install-test.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/debian-repo-install-test/testdata/repo-install-test.sh b/debian-repo-install-test/testdata/repo-install-test.sh
index 4fae488..63e1819 100755
--- a/debian-repo-install-test/testdata/repo-install-test.sh
+++ b/debian-repo-install-test/testdata/repo-install-test.sh
@@ -4,10 +4,10 @@
# Disabled services:
# * osmo-ctrl2cgi (missing config: /etc/osmocom/ctrl2cgi.ini, OS#4108)
# * osmo-trap2cgi (missing config: /etc/osmocom/%N.ini, OS#4108)
+# * osmo-ggsn (no tun device in docker)
SERVICES="
osmo-bsc
osmo-gbproxy
- osmo-ggsn
osmo-gtphub
osmo-hlr
osmo-mgw