Cellular Network Infrastructure » Radio Access Network » OsmoBTS

The reason for the failure was that trxcon and fake-trx were not present. Both containers did not run. That caused the error messages on TTCN3:

MTC@lobotron: Test case TC_meas_res_sign_sdcch4 started.
MTC@lobotron: Test case TC_meas_res_sign_sdcch4 finished. Verdict: fail reason: Timeout waiting for { rsp := { verb := "FAKE_TOA", status := ?, params := * } } on port BB_TRXC

The the problem was that jenkins still was trying to cd to osmocom-bb-trxcon, even though it was renamed to osmocom-bb-host-master and all scripts were were also updated as well. So the containers for trcxon and fake-trx were not build.

+ cd /home/osmocom-build/jenkins/docker-playground/osmocom-bb-trxcon
/tmp/jenkins107667062836676929.sh: 12: cd: can't cd to /home/osmocom-build/jenkins/docker-playground/osmocom-bb-trxcon

Starting container with fake_trx
+ docker run --rm --network ttcn3-bts-test --ip 172.18.9.21 --name jenkins-ttcn3-bts-test-204-fake_trx -d osmocom-build/osmocom-bb-host-master /tmp/osmocom-bb/src/target/trx_toolkit/fake_trx.py -R 172.18.9.20 -r 172.18.9.22
Unable to find image 'osmocom-build/osmocom-bb-host-master:latest' locally

docker: Error response from daemon: pull access denied for osmocom-build/osmocom-bb-host-master, repository does not exist or may require 'docker login'.
See 'docker run --help'.
+ echo Starting container with trxcon
Starting container with trxcon
+ docker run --rm --network ttcn3-bts-test --ip 172.18.9.22 -v /home/osmocom-build/jenkins/workspace/ttcn3-bts-test/logs/unix:/data/unix --name jenkins-ttcn3-bts-test-204-trxcon -d osmocom-build/osmocom-bb-host-master /usr/local/bin/trxcon -i 172.18.9.21 -s /data/unix/osmocom_l2
Unable to find image 'osmocom-build/osmocom-bb-host-master:latest' locally

docker: Error response from daemon: pull access denied for osmocom-build/osmocom-bb-host-master, repository does not exist or may require 'docker login'.
See 'docker run --help'.

The problem turned out to be in the jenkins job configuration. The configuration was updated to use osmocom-bb-host-master as well and now the TTCN3 tests are fine again.

Ah, my bad. I had to update the Jenkins job... Thanks!