That's the default value for all BTS, so no need to have it there.
Furthermore, forthcoming osmo-bts patches will drop osmo-bts-trx support
for DSP/HW based MS Power control, which means BTS will reject this
setting. Let's drop it now and let osmo-bts binary to select the
The logging categories cc and mgcp are obsolete for osmo-bsc and will
cause recent versions of osmo-bsc to crash. Lets remove this logging
categories from the config file now.
OsmoGGSN is not able to use the tun4 device from the default config in
docker. Since the more strict config checking in , it does not just
report a warning, but fails to start:
<0002> ggsn.c:189 APN(internet): Opening TUN device tun4
<0001> tun.c:184 errno=2/No such file or directory open() failed
<0002> ggsn.c:191 APN(internet): Failed to configure tun device
Error occurred during reading the below line:
Failed to open config file: '/etc/osmocom/osmo-ggsn.cfg'
Fix the repo install test jenkins job by not checking osmo-ggsn anymore.
In theory, we could probably create the tun device on the host, and
mount it inside the docker container. But that would require some
additional logic to clean it up properly, and it does not seem worth the
effort right now.
 libosmocore Ic9c1b566ec4a459f03e6319cf369691903cf9d00
The logging categories cc and mgcp are obsolete. The tests still contain
logging statements with those categories, which makes osmo-bsc
terminate during startup while parsing the configuration file.
Currently builds from osmo-ttcn3-hacks.git branch laforge/stp instead of
master, since it's only available in the former branch. Once it gets
merged, we can modify Dockerfile as explained in it.
Scripts ttcn3-tcpdump-start.sh and ttcn3-tcpdump-stop.sh, run by
osmo-ttcn3-hacks upon start and end of every test in the suite, starts
and stops tcpdump and netcat each time.
netcat is started in order to have a dummy sink for gsmtap log packets,
to get rid of annoying ICMP messages as well as the kernel deciding to
drop those messages (hence not ending up inside the pcap file of
tcpdump) under some circumstances.
Depends: osmo-ttcn3-hacks.git Id69d98db63f8260067ad6bc1525fb05c936912f2
Have the same amount of bts like in the regular (non-sccplite)
osmo-bsc.cfg, so we can make BSC_Tests.TC_ctrl pass for regular and
Related: Ie2c664ba0f845da644e20e2c919c12d8fc2af6ba (osmo-ttcn3-hacks)
Previous commit was merged without dependent tests from osmo-ttcn3-hacks
being yet present. Let's disable them until they are present.
Enable test of systemd services for osmo-sgsn, osmo-pcu, osmo-hnbgw and
osmo-bts-virtual. Add issue ID to failing osmo-ctrl2cgi and
Depends: Id892e1f4ab2daabbe9824b819b5fed985373b97a (osmo-sgsn)
Depends: Ie8001611756b661ff1871508c6248b2e990ba1d7 (osmo-bsc)
Depends: I354140f014854f1755b649e40a65e5d88b99c0ec (osmo-iuh)
So far the SGSN master image is built without Iu support.
osmo-sgsn-latest is using the built debian packages which enable Iu
support, so it's not an issue there.
Run systemd services of Osmocom programs, to check if any are not
starting properly. Use a whitelist to determine which services must
start up, because some are currently broken.
Modify the docker run command to support changing the CPU scheduling
policy/priority in systemd service files (used by osmo-bts).
The container grows heavily in size as the test runs, so make sure to
always kill existing ones (from stopped jobs) before starting a new
one. In order to do that, do not use $BUILD_TAG as container name,
which changes with every new jenkins run.
Add own container with systemd, so we can (in a follow-up commit) run
the Osmocom systemd services in this test job. Rewrite the
"interactive shell" logic to support the new systemd docker container,
and enable it with an INTERACTIVE environment variable instead of
hardcoding 'interactive="true"' in the script. While at it, move the
Repository.key install to the Dockerfile so it works more like the other
docker containers we have.
Each access list will have their own counters. Have only one in the
config so the script generating the counter documentation doesn't repeat
We can't create the net if it exists, and it can't be removed until all
attached containers are dead, so ensure this is the case upon net
creation. This fixes test failures due to stale nets and half-killed