Started by an SCM change00443623621.0059715971420d2827d91ce8e1a3c751ecde82f9318ce20e007ecd2827d91ce8e1a3c751ecde82f9318ce20e007ecrefs/remotes/origin/masterd2827d91ce8e1a3c751ecde82f9318ce20e007ecd2827d91ce8e1a3c751ecde82f9318ce20e007ecrefs/remotes/origin/masterd2827d91ce8e1a3c751ecde82f9318ce20e007ecd2827d91ce8e1a3c751ecde82f9318ce20e007ecrefs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundfalse#420362255update-osmo-ci-on-slaves-dp #420420falsefalse420971438SUCCESS1673946966570https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/420/build2-deb11build-ansiblettcn3-ggsn-test/jenkins-ogs.shjenkins-common.shttcn3-bsc-test/jenkins-sccplite.shd2827d91ce8e1a3c751ecde82f9318ce20e007ec1673944792000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.denetwork_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 +0100d2827d91ce8e1a3c751ecde82f9318ce20e007ecnetwork_create: put SUBNET in NET_NAMEeditttcn3-ggsn-test/jenkins-ogs.sheditttcn3-bsc-test/jenkins-sccplite.sheditjenkins-common.shgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith