Started by an SCM change00114414411.0756775670800875657565604006f3179f9fc9ad95b9bf43bce19d4155163f943006f3179f9fc9ad95b9bf43bce19d4155163f943refs/remotes/origin/master006f3179f9fc9ad95b9bf43bce19d4155163f943006f3179f9fc9ad95b9bf43bce19d4155163f943refs/remotes/origin/master006f3179f9fc9ad95b9bf43bce19d4155163f943006f3179f9fc9ad95b9bf43bce19d4155163f943refs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundhttps://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/604/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/604/https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/604/testReportfalse#604441255update-osmo-ci-on-slaves-dp #604604falsefalse6041605032SUCCESS1720780868230https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/604/build2-deb11build-ansible- ttcn3-asterisk-ims-ue-test/dnsmasq/dnsmasq.confd15697fa0b2094f98cac781ccdb8d01126484af01720780747000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.deasterisk: dnsmasq.conf: Avoid forwarding queries to other DNS servers
This creates problems when requesting resolution of the IPv6 address.
For some reason, dnsmasq was forwarding the request to the non-available
google DNS servers, and Asterisk docker container pre-start commands
checking for DNS resolution would never pass when run in jenkins node.
Change-Id: I0ee7a7b0c307cc83acfb1c4c8f4bdc092133fddb
2024-07-12 10:39:07 +0000d15697fa0b2094f98cac781ccdb8d01126484af0asterisk: dnsmasq.conf: Avoid forwarding queries to other DNS serverseditttcn3-asterisk-ims-ue-test/dnsmasq/dnsmasq.conf
- ttcn3-asterisk-ims-ue-test/asterisk/asterisk.sh6384590ad5ddab812d21ecd5e3622629be3b98911720780747000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.deasterisk: timeout ping DNS validations after 3 seconds
Change-Id: I9f1bcbc2b868cf7c894a57ca77e28b5bfbba0eac
2024-07-12 10:39:07 +00006384590ad5ddab812d21ecd5e3622629be3b9891asterisk: timeout ping DNS validations after 3 secondseditttcn3-asterisk-ims-ue-test/asterisk/asterisk.sh
- ttcn3-asterisk-ims-ue-test/jenkins.shttcn3-asterisk-ims-ue-test/ttcn3/ttcn3.sh006f3179f9fc9ad95b9bf43bce19d4155163f9431720780747000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.deasterisk: Wait for Asterisk ready before starting testsuite
A recent commit made Asterisk wait for dnsmasq to be ready before
starting it. This means Asterisk takes more time now to be ready itself,
hence we need to delay launching the testsuite until it is ready.
Otherwise, the entire set of tests may be run even before Asterisk gets
to answer on the AMI socket.
Change-Id: I337d57f3eb3e6688dbf3c61d55978da10d84b2cb
2024-07-12 10:39:07 +0000006f3179f9fc9ad95b9bf43bce19d4155163f943asterisk: Wait for Asterisk ready before starting testsuiteeditttcn3-asterisk-ims-ue-test/jenkins.sheditttcn3-asterisk-ims-ue-test/ttcn3/ttcn3.sh
githttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin