Started by an SCM change253d2014603a736a17d6b92006b25aa41482365ef3dd2014603a736a17d6b92006b25aa41482365ef3drefs/remotes/origin/masterd2014603a736a17d6b92006b25aa41482365ef3dd2014603a736a17d6b92006b25aa41482365ef3drefs/remotes/origin/masterd2014603a736a17d6b92006b25aa41482365ef3dd2014603a736a17d6b92006b25aa41482365ef3drefs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundfalse#253449255update-osmo-ci-on-slaves-dp #253253falsefalse253526414SUCCESS1627479966102https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/253/build2-deb9build-ansibledebian-stretch-titan/ttcn3-docker-run.shd2014603a736a17d6b92006b25aa41482365ef3d1627465572000https://jenkins.osmocom.org/jenkins/user/dwillmanndwillmanndwillmann@sysmocom.dedebian-stretch-titan: Wait for interface to be _up_ not just its existance I've seen at least one instance where -EIFDOWN was returned when the test suite was coming up. This is a race condition, as we first have to move the netdev into the namespace and only then can configure it. "pipework wait" only waits for its existence, not until it is up. We cannot revert the order, as the netdev looses its state when it is moved to a different netns. Change-Id: I1bfb6eb925bca4e4e1901e06eed831152cddbbe2 2021-07-28 11:46:12 +0200d2014603a736a17d6b92006b25aa41482365ef3ddebian-stretch-titan: Wait for interface to be _up_ not just itseditdebian-stretch-titan/ttcn3-docker-run.shgithttps://jenkins.osmocom.org/jenkins/user/dwillmanndwillmann