erlang osmo-epdg is a bit slow starting up, and sometimes the first ttcn3
test may start when osmo-epdg is still not yet listening on the GSUP
socket, specially when the system is on high load.
Give some head time to make sure it is properly started.
Change-Id: I14e39db6548409b203e15fb562e0b44a90bd44cd
Build the kernel with NET_NS and VETH, so libgtpnl's qemu tests can
download the kernel and use it.
Related: OS#1952
Related: libgtpnl Ibf75514b866fffb11e90529e4705f126b23d7415
Change-Id: I6e893b64718f853b8595de36c090a1326db34419
We cannot execute the virtphy based testcases due to the limitations
of Docker (see https://github.com/moby/libnetwork/issues/2397). The
function starting the testsuite was already commented out, but not
the lines starting containers with osmo-bts-virtual and virtphy.
To put it simple, we start and immediately terminate those containers.
And since recently (Feb 1st), we started seeing socket creation errors
in both containers, causing jenkins.sh to abort early. It's yet
unclear what's the cause of those socket errors, but regardless of
that we should still be running other pending testcases.
Change-Id: I7c9ccc9cc400edb7a05e222e51671fd49631a4cd
Fixes: OS#6352
This will be needed since soon osmo-epdg will start creating tunnel
devices througth gtp_u_kmod, which requires CAP_NET_ADMIN, plus it will
need probably need to set up local IP addresses.
Change-Id: I48eea0e8d7969cc0a3ad2ed08f696decf064c474
This way we notice when some dependency update breaks build, and
prevents running against old dependencies if developer forgot to update
rebar.lock.
Change-Id: Ia9112d641e80d1eddcddea1e54e4c135d6efcc5b
These new testcases were added to osmo-ttcn3-hacks.git back in August
2023 (see the related patch), but have never been executed automatically
on Jenkins because the config file was not updated in this repo...
Change-Id: I9ec0a03658ead382eaaef175090cfc3650ffd9b7
Related: osmo-ttcn3-hacks.git I4bbe739ea55ecf9f7ebf9ee413df69f29aa642f8
Old osmo-msc versions do not include the Source Name IE in SMS related
GSUP messages, unless it's set explicitly in the config file ('hlr' /
'ipa-name'). Recent osmo-msc versions (see the related osmo-msc patch)
do include this IE even if it's not set explicitly ('unnamed-MSC').
Because of this, some testcases in ttcn3-msc-test are currently
failing for osmo-msc master, but still passing for the -latest.
Let's set the 'ipa-name' explicitly in osmo-msc.cfg, so that we can
expect both -master and -latest to include the Source Name IE.
Change-Id: I7757aae1d01b679f530b5c0a6c95b224cb9f204f
Related: osmo-ttcn3-hacks.git Ic24d3082fe3dce08e43e8f3ecb6d6132503c55c6
Related: osmo-msc.git I7bacd001b81326c32bc262c7d0c0491ded822fa8
Related: OS#6135
Adapt to the new default value used by ttcn3 tests.
Depends: osmo-ttcn3-hacks.git Change-Id Iaf89228f6f026e04d5f583211959025e6d8d4a1d
Change-Id: Ifefbd9bf2ed1bce8089e3dc4c6f9fe901e72308e
osmo-bts v1.7.2 (recently tagged) now also speaks PCUIFv12.
Take a chance to fix ttcn3-bts-test-2023q1 by setting PCUIFv10.
Change-Id: I70f0c30d6c514614095dcbbcac5d025001861fbc
Unfortunately we had to revert [1] because it worked for current master
but not for latest. The mistake here was to change the PCUIF version
number in PCU_Tests.cfg to PCUIF v12. This is indeed the correct version
for current master, but latest still uses v11. Also the change we made in
jenkins-sns only affected 2023q1 builds, it does not affect latest. This
is the reason why the previous patch broke latest.
This follow up patch now copies the approach we already successfully use
with the normal ttcn3-pcu-test / ttcn3-pcu-test-latest. (see also
jenkins.sh)
[1] I0b37f01f4c7bb829053231339e39ab734f4c8cbc
Change-Id: I1f94a0459e35d7b5632c81d7f7e2e60eb0d0229f
Related: OS#6275
Unfortunately this patch only fixes ttcn3-pcu-test-sns but it breaks
ttcn3-pcu-test-sns-latest, this means a different solution is needed.
This reverts commit c9820d7b36.
Change-Id: I101d27ae8ed7449b199e49795a3561436c2532dd
Related: OS#6275
The current master of OsmoPCU is now using PCUIF version number 12.
However, the configuration file of the the SNS tests still sets it to
11.
Related: OS#6275
Change-Id: I0b37f01f4c7bb829053231339e39ab734f4c8cbc
Adjust open5gs configs to the new formats from:
https://github.com/open5gs/open5gs/pull/2739
This fixes all open5gs programs from crashing on startup with various
errors such as:
11/21 07:39:25.971: [core] FATAL: epoll_init: Assertion `context->epfd >= 0' failed. (../lib/core/ogs-epoll.c:77)
Related: OS#6267
Change-Id: Idf2706f3904eb06e94cee0728faa17e72a6cf1f6
The config format just changed significantly in main/master. Duplicate
the configs, so we can run latest with the old versions.
Related: OS#6267
Change-Id: I2446695172b92ccf75305f878cb932a82e44fdd2
A lot of these comments got outdated with recent config changes
in the related PR. Instead of syncing the comments again and having a
big diff, remove the comments once and then only have diffs of
actual config changes in future patches. This will make it easier to
maintain these configs.
Related: https://github.com/open5gs/open5gs/pull/2739
Change-Id: I67c2a198b9682e15e23a466380e62a976e6236cd
At the moment we use PCUIF v11 in latest and in master. This will now
change (see Depends) so that we will have to use v12 in master. This
patch adds the necessary conditional config changes.
Depends: osmo-pcu.git I48eb75f65ab54fdec41ef913e24c1f18cd4a4047
Change-Id: I5c0914c0bf906b51a500a3b099578700798cf8c0
Related: OS#6191
Fix the TTCN3-centos-pcu-test-2023q1 jenkins job where currently most
tests are failing. This is because 2023q1 is using an older PCUIF
version that is no longer supported by osmo-ttcn3-hacks.git. As
discussed, use a 2023q1 branch of osmo-ttcn3-hacks where the support was
not removed yet.
Fixes: SYS#6638
Change-Id: Id82425aca4a8ff87feb8a130d31712bc62fa27ed
Set X31 to 5s as expected by the testsuite to fix currently failing:
- TC_ranap_cs_mo_disconnect
- TC_ranap_ps_mo_disconnect
It was recently increased to 15s in the related patch.
Related: osmo-hnbgw I24225cfc0addf326c239ec658a27b93b83a3e751
Change-Id: I223d38e9ec2ca0f9f2ce2ac5311932789f328c9a
Configure the newly added S6b interface on both TTCN3 emulation code as
well as osmo-epdg.
Depends: osmo-ttcn3-hacks.git Change-Id Ia50698a3f6f5ed8251486b84c09f84edfd6d3951
Depends: osmo-epdg.git Change-Id Ia2b138317cb291a95882853f5403949c5e6a5a1b
Change-Id: I1145ee1068a2fdd2fe8d3e48b80c8e6c1fcb50ad
Use debian's version of rebar3 instead of downloading a binary. This
was useful when the container was based on debian 11 where rebar3
wasn't in debian's repositories. Debian 12 has version 3.19.0.
This also solves a caching problem on one of the jenkins nodes, which
currently fails at this line:
ADD https://github.com/erlang/rebar3/archive/refs/tags/${REBAR3_VERSION}.tar.gz /tmp/rebar3.tar.gz
with:
ERROR: failed to solve: failed to load cache key: invalid not-modified ETag: "fce57989250a021a2be5fe5eddd655d6d415eef04f769bf1437f3d6dddfa5559"
My understanding is that docker has cached an ETag that is no longer
valid / maybe the format changed - and instead of simply requesting the
file again, it just fails there.
Related: https://en.wikipedia.org/wiki/HTTP_ETag
Change-Id: I69e02d004a0bd6f9d3a462f4e184b3e9361cc7fe
Add DB config for new subscriber required by TC_ulr_ula_subscr_op_det_barring_7.
Depends: osmo-ttcn3-hacks.git I8deea9e284447f8991bdeced982c14fae2f211c5
Related: SYS#6588
Change-Id: I42d6af42bada50c55914ec94c4090fccbe8d1c97
The open5gs Debian_12 is available since today [1]; hence starting using
debian 12 now.
[1] https://github.com/open5gs/open5gs/issues/2669
Related: SYS#6588
Change-Id: Ib11a55294b525e3c3806246b133f8e479554a068
Add ccache, so it can be used when rebuilding the testsuite from source
from a development branch. Ccache is not used by default.
Related: osmo-dev I800062d0379295a6905851db29e820ff16217653
Change-Id: I94d22b8da9f897974c5913b2a8138c653c215446
The open5gs-latest image installs mongodb, but the master one doesn't.
Having a mongodb image is required to run together with open5gs-hssd.
Related: SYS#6588
Change-Id: Id6dde5f54b666279c102eb14fabb87194192c9e4
meson install doesn't install that file because it's aimed at
developers. However, debian package does install it manually in
debian/open5gs-common.install.
Hence, the app is available in open5gs-latest docker image, but not in
open5gs-master. Manually copy it to /usr/bin to have both behave the
same in this aspect.
Related: SYS#6588
Change-Id: I54a760d04e6522d843e6d65b94ef6067e502fbaa
Update the Makefile, so it does not pick the wrong base distribution
when running make in e.g. osmo-bsc-master directly (without going
through ttcn3-*/jenkins.sh as jenkins does).
Change-Id: I31b2a1b8c70b973f4ec0f93d6e9e5e417afec994
Pau Espin
Oliver Smith
Vadim Yanitskiy
Harald Welte
Philipp Maier
Alexander Couzens