docker-playground/ttcn3-ggsn-test
Oliver Smith d2827d91ce network_create: put SUBNET in NET_NAME
Fix the bug that running a test twice on the same host results in the
second test stopping the containers and network of the first test:

* Have the subnet name in the network name, so there's no collision of
  network names when cleaning up the network.

* Don't clean up the network when creating a new network. Rely on the
  clean up trap to clean up the network instead.

* Don't set NET_NAME when sourcing jenkins-common.sh anymore, as
  network_create will set it. There's also network_bridge_create, which
  only gets used by osmo-ran (which we don't run in jenkins). Add a
  check to this function to ensure NET_NAME is set before calling it,
  which osmo-ran is already doing.

Related: OS#5802
Change-Id: Ifcd384272c56d585e220e2588f2186dc110902ed
2023-01-17 09:39:52 +01:00
..
ogs ttcn3-{pgw,ggsn}-test: Update smf.yml with new metrics section location 2022-11-21 11:28:52 +01:00
Dockerfile Use gerrit as osmo-ttcn3-hacks.git git remote 2022-09-20 12:09:32 +02:00
GGSN_Tests.cfg ttcn3-ggsn-test: Use IPv6 address of the tester as "DNS1" 2020-08-16 14:53:36 +02:00
Makefile rename ggsn-test to ttcn3-ggsn-test to align with other naming 2018-03-28 10:37:48 +00:00
fragment.config ttcn3-ggsn-test: add kernel test 2021-02-26 09:32:39 +01:00
initrd-ggsn.sh ttcn3-ggsn-test: add kernel test 2021-02-26 09:32:39 +01:00
jenkins-ogs.sh network_create: put SUBNET in NET_NAME 2023-01-17 09:39:52 +01:00
jenkins.sh network_create: find free subnet automatically 2023-01-16 15:19:29 +00:00
osmo-ggsn-kernel-gtp.cfg ttcn3-ggsn: Modify configs to alloc bigger IPv4 pools 2022-02-25 17:59:22 +01:00
osmo-ggsn.cfg ttcn3-ggsn: Modify configs to alloc bigger IPv4 pools 2022-02-25 17:59:22 +01:00