Started by an SCM change00553833831.0087348734422381e2f3a0e5a5f140f223ed9620579f81dca1e73381e2f3a0e5a5f140f223ed9620579f81dca1e73refs/remotes/origin/master381e2f3a0e5a5f140f223ed9620579f81dca1e73381e2f3a0e5a5f140f223ed9620579f81dca1e73refs/remotes/origin/master381e2f3a0e5a5f140f223ed9620579f81dca1e73381e2f3a0e5a5f140f223ed9620579f81dca1e73refs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundfalse#422383255update-osmo-ci-on-slaves-dp #422422falsefalse422971826SUCCESS1673959869305https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/422/build2-deb11build-ansible- jenkins-common.sh381e2f3a0e5a5f140f223ed9620579f81dca1e731673959289000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.denetwork_create: set NET_NAME after next SUBNET
Put the current SUBNET into NET_NAME, not the previous one. Without this
patch it works too, but this makes more sense.
Related: OS#5802
Change-Id: I6c90505fd6c0ba62244ff67709b0bf31bf44b449
2023-01-17 13:41:29 +0100381e2f3a0e5a5f140f223ed9620579f81dca1e73network_create: set NET_NAME after next SUBNETeditjenkins-common.sh
githttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith