Started by an SCM change00113743741.05756575606130575457545652b9c8e3db8cf77c5ce5c3f888365f983f3ee8d762b9c8e3db8cf77c5ce5c3f888365f983f3ee8d76refs/remotes/origin/master2b9c8e3db8cf77c5ce5c3f888365f983f3ee8d762b9c8e3db8cf77c5ce5c3f888365f983f3ee8d76refs/remotes/origin/master2b9c8e3db8cf77c5ce5c3f888365f983f3ee8d762b9c8e3db8cf77c5ce5c3f888365f983f3ee8d76refs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundhttps://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/565/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/565/https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/565/testReportfalse#565374255update-osmo-ci-on-slaves-dp #565565falsefalse5651549463SUCCESS1715848566603https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/565/build2-deb11build-ansiblettcn3-asterisk-ims-ue-test/asterisk/pjsip.confttcn3-asterisk-ims-ue-test/Asterisk_Tests.cfgf9c8ed8de78b7f6641c9802be2d0cdd2488295fb1715774999000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dettcn3-asterisk: Configure asterisk for initial SIP register on IMS side This set of pjsip config requires work done by jolly in our fork of asterisk adding IMS features. Depends: osmo-ttcn3-hacks.git Change-Id Idb3b19ccd82cad25948106b2c72aa424d7f79cd8 Change-Id: I66d128192146ad600203ea2a41b8bf019311d603 2024-05-15 14:09:59 +0200f9c8ed8de78b7f6641c9802be2d0cdd2488295fbttcn3-asterisk: Configure asterisk for initial SIP register on IMS sideeditttcn3-asterisk-ims-ue-test/Asterisk_Tests.cfgeditttcn3-asterisk-ims-ue-test/asterisk/pjsip.confcommon/ttcn3-docker-run.sh2b9c8e3db8cf77c5ce5c3f888365f983f3ee8d761715797501000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dettcn3-docker-run.sh: Fix dumpcap failing to access /data inside docker In docker, the /data dir is mapped to $VOL_BASE_DIR, which is created by docker-playground.git jenkins-common.sh, hence as the user running jenkins.sh in the host system. As a result, when the dir is mapped to /data, inside the container it will have the UID:GID of the outter user, not the one inside docker. Before this patch, if a ttcn3 container was started in jenkins.sh with --cap-add=NET_ADMIN, then osmo-ttcn3-hacks.git/ttcn3-tcpdump-start.sh would select dumpcap instead of tcpdump, to attempt to record a pcap file to /data/$testcase.pcap. Due to some unknown way of dropping privileges done by dumpcap though, it was unable to open the /data/$testcase.pcap due to /data being owned to another user (tcpdump doesn't have this problem). This patch fixes the above scenario by making sure /data is chowned to the user running stuff inside docker. This is already kinda expected since there's a fix_perms() script in jenkins-common.sh reverting files created during the test so that they can be accessible by outter user once everything is finished. Change-Id: I1229a91cdbb1aa73fd94f1bf7e26f34086f06b25 2024-05-15 20:25:01 +02002b9c8e3db8cf77c5ce5c3f888365f983f3ee8d76ttcn3-docker-run.sh: Fix dumpcap failing to access /data inside dockereditcommon/ttcn3-docker-run.shgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin