Add libnftables-dev, which is needed for osmo-upf. This is required to
move the coverity jenkins job to use this docker container.
Order the list alphabetically again while at it.
Change-Id: I25862a7e3c8a73e13fd4a9237ab57500d8dfc95c
Remove the container, as the job has been rewritten to not require its
own docker container anymore, see the osmo-ci patch.
Depends: osmo-ci I9f8b671b9780da500637a64fc4dbc72b450f9d11
Change-Id: Ic35a28a386170b85d32aab8f2bd33e48e6d45392
* Remove code that is in debian-bookworm-build already (all packages
that get installed, creating the build user, installing osmo-ci and
osmo-gsm-manuals).
* Put toolchain installations in single RUN commands, so the unextracted
tarballs are not stored in image layers.
Related: OS#6057
Change-Id: Iaaca6367b76a6ec860c63d57c767954f82edfee5
Merge at the same time as the osmo-gsm-manuals patch.
Depends: osmo-gsm-manuals I0d132f8f6fd73fbe14b5bfa10a8659acaddf38f7
Change-Id: I012c61eb777e6dc267dd4a52500da98c01ac1438
Add new containers based on debian-bookworm. Make some improvements
over the bullseye containers while at it:
* Remove sed for cversion.h, as the #error it is trying to replace is a
warning now so it is a no-op, and we use our own eclipse-titan package
instead of debian's package.
* Make apt commands consistent
* Move commands around to make better use of the cache
* Clone osmo-python-tests from gerrit instead of gitea and invalidate
cache when master changes
* Tweak comments
Related: OS#6057
Change-Id: I4415fcde6518bd26d1e2cb5785ddaf84ac2116b3
Config changes matching cnpool tests added in osmo-ttcn3-hacks, see
'Related'.
Keep a copy of the old config files named "-legacy", to not break the
'latest' tests, because osmo-hnbgw 'latest' does not yet support the new
config options.
Depends: osmo-ttcn3-hacks I027a059faed3f140f8801f84338956cd004043b5
Change-Id: I94aa0b2adfc48b98cb4b1efe595c2432fc603d6c
iCurrently we install inetutils-ping in some docker images and
iputils-ping in others; let's make it more uniform to avoid running
different implementations in different images.
The iputils-ping provides further linux-specific features, such as the
"-I interface" param, which is used by some images, so let's pick that
one everywhere.
Change-Id: If11a1c2ae1115b585b6a44a45e9569c16856d8c4
Bring back the osmocom user that was removed earlier to fix a UID
conflict with the build user.
The osmocom user is being used after all, the TTCN-3 PGW tests use it to
start commands as "osmocom" user in osmo-uecups-master. This lead to e.g.
PGW_Tests.TC_createSession_ping4 failing.
Rename the user instead of adding a new one, so it can write log files
to the log dir as the same UID as the user that runs docker.
Fixes: 94f8a8 ("osmo-uecups-master: remove useradd")
Related: OS#6057
Change-Id: I2b29d7fedcf3e0a4c17bfbad16077098f94c529b
Older commit disabled the talloc report checks but forgot to add the
same line to the with-pfcp/ variant, and as a result the sed command in
jenkins.sh won't work there.
Fixes: cb4897e4c0
Change-Id: Id4eed548b3a552747e95784be3654952e10e96ab
Use $DOCKER_ARGS in the docker run call to kernel-test/prepare.sh, which
builds the initramfs. I use this to make a local build of osmo-ggsn +
depends available in the docker container in /usr/local with the
ttcn3.sh script in osmo-dev.git.
Change-Id: Ie2500fa1bd9d57e2531463ce93fdd9930ad829d3
The metrics_impl option has been dropped in the related commit as
prometheus is now the default in open5gs. With newer meson, unknown
options are treated as errors (used to be warnings before).
Fix for:
ERROR: Unknown options: "metrics_impl"
Related: OS#6057
Related: 982ac61894
Change-Id: Ib859ef7389928019addecae08df2011eecda80ad
Give the user that runs open5gs a different UID than the build user from
the debian-bookworm-build container.
Fix for:
useradd: UID 1000 is not unique
Related: OS#6057
Change-Id: I49051e038740cfccbb11ad33a1884bb7de318710
Instead of hardcoding bullseye, use the DISTRO variable so it now
defaults to bookworm.
Related: OS#6057
Change-Id: Ia392de80ee1f0844563f08a6dc775678ef6b263f
Prepare to add more kernel related env vars. Instead of duplicating the
descriptions here, point to the README file.
Change-Id: I324f12930c5521e29312b309d6344ed5ffbd2581
The previous versions happened to work too in my testing with
osmo-ggsn. Use the correct loop variable.
Fixes: 0660fc4e ("scripts/kernel-test: adjust to usr-merge")
Change-Id: I0c0ca91116a8cd156b185bb53512371bbcb76515
Set init= so the kernel doesn't try to run other scripts if /init
fails:
[ 2.946381] Run /init as init process
[ 2.948885] Failed to execute /init (error -2)
[ 2.949051] Run /sbin/init as init process
[ 2.949329] Run /etc/init as init process
[ 2.949566] Run /bin/init as init process
[ 2.949795] Run /bin/sh as init process
Change-Id: I063c7625acaa15130d8361d4e944c3773c9b37c4
In debian bookworm, the /usr merge has been implemented:
/bin → /usr/bin
/sbin → /usr/sbin
/lib → /usr/lib
/lib64 → /usr/lib64
The initramfs filesystem layout is derived from the paths of the
binaries and libraries in the full system. Create the same symlinks and
adjust initrd_add_bin so it does not trip over the symlinks.
I've also considered to change all input for initrd_add_bin to point at
the /usr/… paths. But this is not possible, for example ldd/lddtree will
point at libraries in /lib and /lib64, and this gets passed to
initrd_add_bin.
Without this patch, the init script and all binaries called from it
cannot be executed.
Related: OS#6057
Related: https://wiki.debian.org/UsrMerge
Change-Id: I975d3af0fa88869688673936a08189de800fba29
debian-bookworm-build already adds a user (as it is a combination of
debian-bullseye-build and debian-bullseye-jenkins, and the latter did
it). Remove the additional useradd in osmo-uecups-master to fix:
useradd: UID 1000 is not unique
I've looked through related configs and scripts and the username is not
hardcoded there.
Related: OS#6057
Change-Id: I28f2a110167f550e1b38332ed4e7124b9e76f312
Create debian bookworm (12) based containers for building all Osmocom
projects in master/gerrit/ttcn3 jenkins jobs.
This is a combination of debian-bullseye-build (ttcn3) and
debian-bullseye-jenkins(-arm) (master/gerrit), which were used for this
purpose but had several differences. Combining them solves the
following problems:
* The naming was confusing, as both the -jenkins and -build containers
were used in jenkins and were used to build the Osmocom stack.
* This lead to adding the dependencies to the wrong containers / not
adding them to both containers.
* Now we are sure that if a program builds from source in the master
and gerrit verifications, it will also build in the ttcn3 jobs.
Other notable changes from the debian 11 containers:
* Python2 is finally gone (OS#5950, for the few projects that still
need it like openbsc, I'll use debian 11 for the jenkins jobs)
* Removed osc and git-buildpackage, now that OBS package building is
done in different docker containers (see osmo-ci/scripts/obs)
* Combined multiple RUN commands into one as they the image build
down, used set -x to display what commands run exactly
* Use UID variable instead of hardcoding 1000
* Optimized order of commands, so e.g. the LLVM for Arm that we will
rarely change gets installed/cached before the big list of apt pkgs
* Replaced old git.osmocom.org urls
* Removed apt-get upgrade; the base image will get upgraded from time
to time, no need to upgrade within the image
* Add --depth=1 option to git clones and remove temporary git clones
* Removed generating locales code, it was only done by one of the two
images and I couldn't find in the git log why we would need this (if
we do need it we can add it back later)
The following patches add more debian bookworm containers and have
similar improvements.
Related: OS#6057
Change-Id: I49aaf62b5b97775f923453611df3b91354a640a0
Fix current jenkins test breakage:
Adjust HNBGW_Tests.cfg after changes to osmo-ttcn3-hacks in
"hnbgw: prepare cn pool: add multiple MSCs and SGSNs"
Ia29565cabc072de9aa46565b57232e1eda65874f
Change-Id: I912e8ad1f528d0d726b778a02a0f54c77b298f54
Prepare for osmo-bsc I8b3d5efb769437a5d3036e1e627b8d477275d93e where
jenkins.sh will explicitly build meas_vis and configure.ac will stop if
libcdk5-dev is not installed.
Currently meas_vis only gets built if libcdk5-dev is installed, meaning
right now it doesn't get built by the jenkins verification and
master-build jobs (only by the debian package build verification).
Related: OS#5173
Change-Id: I015b6d7cb834e99ea5d04206ba5f8c519c4e6af1
an MME testsuite exists in osmo-ttcn3-hacks but it is not executed in
docker yet.
Related: OS#5760
Change-Id: Ic1ce1dace47353b0dcf321c923a78567e3ddefb9
OsmoBTS currently uses PCUIF v.10 but will move to v.11 soon. (see
Depends). Unfortuantely this means that we have to execute the TTCN3
testsuite in master with PCUIF v.11 and in latest with PCUIF v.10. This
will be the case until the current master becomes the new latest on the
next release.
Depends: osmo-bts.git I25816ac12e63cc6b641eb414e6bc7eaa9c85fc25
Depends: osmo-ttcn3-hacks.git I08de02e951e10bc8b4381cc2ad32e63f2747e3c4
Change-Id: Ia28bc0d6d3cbfe63be19443db86631fb67bb80fb
Related: OS#5927
It was recently decided it's a good practice to always specify the role
and sctp-role for all ASPs configured in the VTY, since it's an
important configuration providing feedback on the network setup
expectancies.
Change-Id: Ia495bc3c5dd4421e5730c74b2f5dc4e4cdc1a673
While inspecting the running docker container I found that the script
already runs as redmine user. I had assumed that it runs as root
earlier. Running 'su' as redmine user fails, therefore it currently does
not run the fetch_changesets command.
Related: OS#6083
Change-Id: I195311b93868eb5fd73ad6e3c165d48f3b7b53ce
Do "docker run" directly inside the Makefile, without wrapping it
through the "run" target in make/Makefile. Use $(USER)/ttcn3-bts-test as
image name, instead of $(REGISTRY)/$(USER)/ttcn3-bts-test. The
$(REGISTRY)/ part is hardcoded in make/Makefile.
This fixes TTCN3-centos-bts-test, because it uses the ttcn3-bts-test
image that gets built in jenkins.sh before running 'make cfg'. Without
the patch, an image downloaded some time ago from the registry gets
used (a new image is not pulled), leading to the stale config.
Fixes: OS#6065
Change-Id: Iebd81e814d84e8cf8360568419ceda7ffc38e742
Until recently, the asp-clnt-* ASPs, which have specific handling in osmo_sccp_simple_client_on_ss7_id(),
were being always forcedly set to sctp-role CLIENT by code in that
function.
This prevented user of that API from explicitly configuring the ASP as
"sctp-role server" through the VTY as the option would be overwritten silently.
Now, the sctp-role from config is followed if the ASP is
defined/configured through the VTY (not dynamically created at the time
osmo_sccp_simple_client_on_ss7_id() is called).
Since the default for a VTY-specified ASP is to be in "sctp-role
server", the config files need to be updated to properly configure the
ASP to be in "sctp-role client", which is the desired mode here.
Same applies for "role", where the default is SG but it is actually used
as "ASP" here.
Change-Id: Idf84502ffa199926a5f0ee616313b515743811ab
Depends: osmo-ttcn3-hacks.git Change-Id I4eb5b5f6b4b24df079b4c74e2a2e2ebb8769b0bd
In osmo-ttcn3-hacks.git I81052ece7d1cc8b43da6155356ed1c4d9620acdc
we're adding support for so-called "norctrx"tests, covering
operation without routing-context IEs. For this, we need additional
AS/ASP definitions in the osmo-stp.cfg
Change-Id: Ie00d96d04dd36c71c79f3b73713c3fe1c26a5145
Related: OS#6003
Oliver Smith
Neels Hofmeyr
Philipp Maier
Pau Espin
Daniel Willmann
Harald Welte