Started by an SCM change87873f496d2b4048253da8d3cdb4fdd084017b094b873f496d2b4048253da8d3cdb4fdd084017b094brefs/remotes/origin/master873f496d2b4048253da8d3cdb4fdd084017b094b873f496d2b4048253da8d3cdb4fdd084017b094brefs/remotes/origin/master873f496d2b4048253da8d3cdb4fdd084017b094b873f496d2b4048253da8d3cdb4fdd084017b094brefs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundhttps://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/87/artifacthttps://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/changeshttps://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/87/https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/87/testReportfalse#87478255update-osmo-ci-on-slaves-dp #8787falsefalse87245218SUCCESS1597386636454https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/87/build2-deb9build-ansible- ttcn3-msc-test/osmo-msc.cfgttcn3-msc-test/jenkins.shttcn3-msc-test/osmo-stp.cfgttcn3-msc-test/Makefilettcn3-msc-test/MSC_Tests.cfg873f496d2b4048253da8d3cdb4fdd084017b094b1597385021000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgmigrate ttcn3-msc-test from 172.18.1.0/24 to 172.18.20.0/24
When introducing IPv6 support, we map the third digit of the IPv4
address (X) to the 6th byte of an IPv6 prefix "fd02:db8:X::/64"
However, the docker daemon seems to use "fd02:db8:1::/64" internally
for its default network, so creating a docker network with the same
IP address is failing.
Let's move the MSC test suite to another sub-net (1->20) to avoid
related problems.
Change-Id: I9c5f9b96d5523eae09f3f2e6c813e9e0d047f9ab
2020-08-14 08:03:41 +0200873f496d2b4048253da8d3cdb4fdd084017b094bmigrate ttcn3-msc-test from 172.18.1.0/24 to 172.18.20.0/24editttcn3-msc-test/osmo-msc.cfgeditttcn3-msc-test/MSC_Tests.cfgeditttcn3-msc-test/Makefileeditttcn3-msc-test/jenkins.sheditttcn3-msc-test/osmo-stp.cfg
githttps://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge