Do not set up the Osmocom repository inside osmocom-bb-host-master, it
is done in debian-bullseye-build. Without this patch, we actually
installed the debian 9 version of libosmocore-dev in the debian 11
container.
This is part 1/2 of fixing TTCN3-centos-bts-test, which has been failing
since OSMOCOM_REPO_MIRROR was changed in osmo-ci.git. Part 2 is in
osmo-ci I8201f34a0f9747eea78c358a626cc3981d7407c4.
Change-Id: I78e0445a1b82e5cd72ecaa86e8fe25516b19f485
As required by libosmocore, e.g. when building programs directly in this
container with osmo-dev.git/ttcn3/ttcn3.sh.
Change-Id: I4cd05ef2c164dfb765ee365ab38b8dfd4f955ac6
Add arguments to osmo-bts-omldummy to properly report the features that
were previously assumed for osmo-bts even without reporting them, until
this was changed in osmo-bsc I7fca42a39a4bc98a6ea8b9cfab28c4bad3a6a0aa.
Related: SYS#5922, OS#5538
Change-Id: Ib22f25431330676d59900de7bfb3d89e7872baf1
The SO_BINDTODEVICE feature (used for VRF) requires CAP_NET_RAW. Since
we run open5gs-upfd as user "osmocom", that seems to be causing some
permission problems under some systems (like jenkins). Let's make sure
we add the capabilitites to the binary before launching it as user
"osmocom".
Change-Id: I51ee6954a6c019a41cfcd50b2d99166316989d9b
Add libelf-dev to be able to build kernel modules with
defconfig_x86_64.
This is an update to commit d6c5c7a034,
which should have not just modified the stretch but also the buster
Docker image
Change-Id: I4c442d86688278ff634a286b98637189eef88bfb
Related: OS#5407
This reverts commit 029c8df999.
I actually meant to change osmo-bsc.cfg in ttcn3-bsc-test.
Change-Id: I85c577cbc608a77d6d6a5816f1fb7205361f7b4a
Related: SYS#5917
The default AMR link adaptation parameters have been changed in
the recent osmo-bsc, so set the old expected default explicitly.
Change-Id: Ic1c46d54ef97278100bd52156ad5627418ef5c97
Related: osmo-bsc.git Ic5f8d55d250976d8d4c9cae2d89480fd52326717
Related: SYS#5917
Since recently, curl fails to download the key from www.mongodb.org:
'''
$ curl --verbose https://www.mongodb.org/static/pgp/server-4.2.asc
GET /static/pgp/server-4.2.asc HTTP/1.1
Host: www.mongodb.org
User-Agent: curl/7.82.0
Accept: */*
Mark bundle as not supporting multiuse
HTTP/1.1 301 Moved Permanently
Content-Type: text/html
Date: Wed, 13 Apr 2022 20:50:19 GMT
Location: https://pgp.mongodb.com/server-4.2.asc
Connection: Keep-Alive
Content-Length: 0
'''
By default, curl would not follow redirects unless '-L' is specified.
Let's use Docker's 'ADD' command instead, like many Dockerfiles do.
Also, update the address as suggested in the server's response.
Change-Id: I9757fcce084595341b1a68822bad454b64941eb1
Related: SYS#5602
Bind to specific container IP address.
Use more uniform logging config settings as most of the other osmocom processes.
Change-Id: I36bb04a388ab65aaa03a82c159a1b258886ec0d0
Stopping all the containers takes quite a lot of time. Let's stop them
all in parallel to gain some time.
Change-Id: Iabf63ebdee9d1bf13a364ea3eb530ed9dae9b2a5
We already log stdout/stderr to a file, so there's no need to log a file
internally. We prefer logging that through stdout/stderr in order to
catch more stuff, like segfaults.
Change-Id: Ifdc010f26abdc8cefeec0c72a1f617911ec375d7
This approach has several benefits:
* We end up with ip/tun setup output in the same log file as
open5gs-upfd process output.
* We configure all ip/tun *before* the open5gs-upfd process starts.
Furthermore, we have same procedure as in ttcn3-ggsn-tests-ogs, which
simplifies maintainment/use.
The IP address pool for UEs is still different in pgw-tests and
ggsn-tests-ogs. We can make them the same in subsequent patches.
Change-Id: I94219abbeb5e004ce707407b5aa5ee8ad6c3a80e
Some specific gdb commands need to be run in open5gs-smfd to get the
desired result (some signals need to be ignored).
gdb use is not enabled by default. Furthermore, if one wants to use it,
editing the Dockerfile to install gdb is required.
Change-Id: I1ac8b77e84d57040fc09964356bc8a01e5d721e3
Let's make names similar to what's used in PGW_Tests. Also, in
open5gs.git, config files don't contain the "d" at the end.
Change-Id: If56d1a890a4f1b80b4f04ae22644f9cb9cdd35f4
Arch Linux ships gnuradio-3.9.4.0, while gr-gsm has not been migrated
to 3.9 yet. Let's use debian:bullseye, which ships gnuradio-3.8.2.0.
Change-Id: I9900addf152fd254283ef340cea16583ee5ac1c5
This way we validate the feature is run and open5gs-smfd/upfd don't fail
when applying it.
Related: SYS#5846
Change-Id: Ie23db8ffb4868e4bc75783e2f6eb7a725b376ea7
This better identifies the peer, specially since we'll also connect to
an OCS in the future.
Depends: osmo-ttcn3-hacks.git Change- Id I1eb03d907b46c4bb24491f390ef468e831190e08
Change-Id: I4c9f90de1456cf1515c9a0608b44a44fa8acb311
Move cleaning up logic to clean_up(), so it runs as part of the
clean_up_trap if any command in the previous code fails.
For example, if the first docker container started properly, but the
second docker container failed to start: without this patch, it would
just stop the script without running the clean up code.
Change-Id: I4624e37d5d2fa90b71b32d72067b3645f69805da
Revert the change of adding a --rm to the "docker run" commands done in
I48b01c43fedf379b8a565eaab0369806d7831bd8.
This script runs the containers in the background, waits until they are
done, copies the logs and then removes them afterwards.
Fix for:
+ docker kill jenkins-ttcn3-fr-test-384-frnet
jenkins-ttcn3-fr-test-384-frnet
+ docker logs --timestamps jenkins-ttcn3-fr-test-384-ttcn3-fr-test
Error: No such container: jenkins-ttcn3-fr-test-384-ttcn3-fr-test
Change-Id: I56dc07820ccfa8ad6936764262a7c6c272e59c37
Copied from debian-buster-erlang, references to debian 10 and buster
modified to debian11 and bullseye.
Change-Id: I5c13eedcbfa721b7e1939e571470ea7044c00211
Add "--rm" to each "docker run" command, so they don't continuously fill
up disk space.
Fix this even in the pipework script. We don't use the code path there,
but by always having --rm after "docker run" (same line or next line),
a new lint script in osmo-ci I8ab9c291504475d670bdefc50c4524c5bdd4c880
can help us avoid this in the future.
In ttcn3-ggsn-test/jenkins.sh, move one existing --rm in a later line
upwards so the linter can find it.
Related: SYS#5827, OS#5099
Related: https://github.com/jpetazzo/pipework/pull/248
Change-Id: I48b01c43fedf379b8a565eaab0369806d7831bd8
The DNS address provided is used by the test to ping. In osmo-ggsn, we
configured the DNS to be the shared address between GTPC and GTPU. In
open5gs, the addresses are different. Hence, let's pass the GTPU address
instead of the GTPC address to make the setup easier (no need to have
proper routing working between UPFD and SMFD containers).
Change-Id: I2a452ad871612d1c88b94579dadbe62b718b1475
Allocating a pseudo-TTY (-t, --tty) fails when 'run' is executed
inside of a Jenkins or cron script. This change fixes
ttcn3-bts-test, which invokes 'run' to fetch the config files.
Change-Id: If22f682be4f004c5bb43e65098079a4f4fe6158d
Fixes: If15461240f3037c142c176fc7da745a1701ae3f8
This uses the config files from osmo-ttcn3-hacks.git instead of keeping
local copies around here, which has shown many times will get out of
sync. Extract the original files (*.src.cfg) from the testsuite image
(ttcn3-bts-test) and merge them with the local *.confmerge files using
osmo-config-merge. Use the resulting files (*.gen.cfg).
Unfortunately, osmo-config-merge is not capable of removing text blocks
or substituting specific parts, so we fall-back to using sed where it's
needed. A good example is 'log gsmtap 127.0.0.1', as there is no
command for removing a logging target of such type.
Co-Authored-By: Vadim Yanitskiy <vyanitskiy@sysmocom.de>
Co-Authored-By: Oliver Smith <osmith@sysmocom.de>
Change-Id: If15461240f3037c142c176fc7da745a1701ae3f8
Oliver Smith
Vadim Yanitskiy
Pau Espin
Harald Welte
Daniel Willmann