Recent commits applied changes to the default scenario, but forgot to
apply them to the 'with-pfcp' subdir.
Fixes: 6de89a5fb5
Fixes: 3736d31fc0
Fixes: 0bdbcd6815
Fixes: 2c22a96355
Fixes: d3711e6710
Change-Id: Ie02a0754a6ca985e60e08f1f171f532b6cc16264
The Asterisk_tests testsuite recently gained initial AMI support.
Configure it with the proper IP address.
Depends: osmo-ttcn3-hacks.git Change-Id I2c570e4d04e7ab8c44962cf484e4bbc946209aee
Change-Id: Ibb6af1cbfb652214b2fdd2a6eb9a4887c9a9cfb0
Also update osmo-hnbgw.cfg to configure statsd, as done in
osmo-ttcn3-hacks.git 904b5f1a56629b84f67807a75d5c0b356cc7d726.
Change-Id: I80c228b7ad4b9fb06b1651f23a2932bf19374297
Copy the block for configuring the build user and disabling man pages
from debian-bookworm-build. This fixes failures on
ttcn3-ggsn-test-kernel-latest* (non-latest worked fine since these use
containers based on debian-bookworm-build).
Fixes: 5a48bfbe ("scripts/kernel-test: build initrd+kernel as user")
Change-Id: Idee29d5b9796e8905bdf822d076f25612cbc77a0
Adjust open5gs-latest and osmo-uecups-latest to not hardcode a UID. This
is in preparation for creating a "build" user in
debian-bookworm-obs-latest, like we have it in debian-bookworm-build.
Change-Id: Icaebf46487056cea745805527fdc545d9a1846cd
Refactor code to build the initramfs and kernel as user, instead of
running related code as root. Put the smoke_test.log into /tmp instead
of the cache dir, so we don't write as root into the cache dir. We cat
it on error anyway, so we don't need to have it in the workspace.
Change-Id: I1670dd86f2670f42eb99e4527d483965d8222402
Ensure the user that runs docker owns files in cache and data dirs
during fix_perms, if an old job created them as root.
Change-Id: I43af48bd87e27abad5ad52e734256d78651f67c3
This dockerized setup allows running the Asterisk_Tests ttcn3 testsuite
against Asterisk from the asterisk-master docker image, in order to test
the IMS UE feature which will be developed soon.
Related: SYS#6782
Depends: osmo-ttcn3-hacks.git Change-Id I66f776d5df6fb5dc488d9e589b84a6b2385406e8
Change-Id: Idd262b9224ea879a6e941792944fe0b0db3e68ba
This Docker image allows building and running Asterisk from git.
Default config is to build the sysmocom fork used to develop new
features (hence pointing to sysmocom/master branch in that repo.
Related: SYS#6782
Change-Id: Iaa3816f8ceefac8956e61e15f79ed708dec55238
As the comment states, the BSC container is not needed for the OML
tests. The testsuite itself "speaks" OML to the IUT in this case.
Change-Id: Iab44b9ed83e917475c9e2e86ad32b303b05b2ace
Fixes: aad045f5 "ttcn3-bts-test: add env var to not run all configs"
Fixes: OS#6421
Don't fail if osmo-ggsn can't be killed at the end of a testsuite
run. This happens currently with ttcn3-ggsn-test-kernel-latest-* jobs,
in the v6_only configurations, because osmo-ggsn latest doesn't support
ipv6 yet and exits. The jenkins.sh should keep going and try other
combinations, and exit without error in the end.
Fixes: d8c51cce ("ttcn3-ggsn-test: run with multiple configurations")
Change-Id: I6f3154a9ef114f31bcb5868ee09d1ebc10f35d07
The kernel ttcn3-ggsn-tests have been failing since the osmo-ggsn
config for kernel-gtp has been adjusted for v4v6 instead of v4 only.
This new configuration caused a regression with:
* linux kernel without Pablo's GTP IPv6 patches
* latest stable release of osmo-ggsn, which does not support IPv6
As the kernel patches aren't merged yet, this caused all tests to fail.
Avoid this by running the ttcn3-ggsn-test with multiple configurations:
* v4_only: one APN with v4
* v6_only: one APN with v6
* v4v6_only: one APN with v4v6
* all: multiple APNs with all of the above
With this change, the tests running in the v4_only configuration will
pass again with the stable versions of osmo-ggsn, libgtpnl and kernel.
And with new versions, most test in the other configurations will pass
too.
As discussed with Harald, this does not only split up the configuration
for osmo-ggsn with kernel gtp-u, but also with the userspace
implementation. The "all" config currently only works with the
userspace gtp implementation (OS#6106).
Related: OS#6096
Depends: osmo-ttcn3-hacks I6d94a8b18200fbb2119406827b74b83e912e3ecc
Fixes: e24442f9 ("ttcn3-ggsn-test: kernel-gtp: add ipv6")
Change-Id: Ia2fe0c3ed4ccf06e72fd258d085e4a79cecd5f26
Prepare to add variations of the configs: move them to subdirs, so we
don't cullter the main directory.
Related: OS#6096
Change-Id: I03a06f9f516922c47e3092ff7d7c2c68b0852c1b
Prepare to run start_ggsn and start_testsuite multiple times with
different configurations in a follow-up patch.
Related: OS#6096
Change-Id: I0754b0df5f1b0b162732c3db0797f65676553ab0
Make it possible to e.g. run only one of the generic/oml/hopping
configurations.
I made a version of this patch a few weeks ago for testing OS#6375,
and I'm submitting it now so I can add multiple configurations for
ttcn3-ggsn-test in the next patch with the same logic.
Change-Id: I1dce5e6aa4b5d67f9f8c96ced611ab2875c353c8
Set the assigned IP address for the UE in the EPDG docker container on
the eth0 interface. This way the emulated UPF (ttcn3) can test
decaps+encaps of osmo-epdg tun by pinging the UE IP address and
expecting a pong back.
Related: OS#6235
Change-Id: Icc5710b42e5a5374aade6b952e1c543565ffad2e
Set the new module parameter added in the test.
Make sure the gtp_u_kmod osmo-epdg.config IP address is updated to the
proper docker network subnet.
Depends: osmo-ttcn3-hacks.git Change-Id I3fd96f212175959cb113d2f6a362c0e77e5ca0d7
Change-Id: I5cd9dcd6188227baed71823b0cbceb77dc771011
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
Pau Espin
Oliver Smith
Vadim Yanitskiy
Harald Welte