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
Change-Id: Iccda25bc274ee93705c23dfd3e0f9dad5fc2a059
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
sccplite again.
Related: I1c57a04747f5ec004ccf4657954dcb0b003c24fc
Related: Ie2c664ba0f845da644e20e2c919c12d8fc2af6ba (osmo-ttcn3-hacks)
Related: OS#4156
Change-Id: I00547dccf8908d46df4730cb513fe577956d7683
Last releases of osmo-bsc and osmo-bsc already support Osmux, so we can
drop those lines as indicated.
Change-Id: Id6a18f2d691f6e9234a5a0cf91ed5c840a6394de
Previous commit was merged without dependent tests from osmo-ttcn3-hacks
being yet present. Let's disable them until they are present.
Fixes: ca2ef84252
Change-Id: Icd7a3885bac7f8189272981d4fdac3f269e6adef
To support Iu tests, start osmo-stp when testing.
Depends-on: I66069e31c30d33934ad57cc2b8794f56ffd5c7d6 (osmo-ttcn3-hacks)
Change-Id: I4d6aef98832202652c5fe254105728430ba77119
Analogous to osmo-ttcn3-hacks patch If44dd6b578cdc55076c8180707d1c2d69fe5f2a8,
also remove the neighbor config from osmo-bsc.cfg here.
Change-Id: I23d9a2046709452f4d3904230871f7421c6987a9
Enable test of systemd services for osmo-sgsn, osmo-pcu, osmo-hnbgw and
osmo-bts-virtual. Add issue ID to failing osmo-ctrl2cgi and
osmo-trap2cgi services.
Depends: Id892e1f4ab2daabbe9824b819b5fed985373b97a (osmo-sgsn)
Depends: Ie8001611756b661ff1871508c6248b2e990ba1d7 (osmo-bsc)
Depends: I354140f014854f1755b649e40a65e5d88b99c0ec (osmo-iuh)
Related: OS#3369
Change-Id: I4e182b396e1a2e36a73384233b1a38a70c7cd5d9
Previously we were using 178.18.12.0/24 which could have conflicted with
the osmo-bsc sccplite TTCN3 tests.
Change-Id: Ib5ab391ebb21ce2455fbb1ae47dd01ed53cd2e41
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.
Change-Id: Ib9c2e96dc7309f7fcbd563d656b64d37f2599f7b
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).
Related: OS#3369
Change-Id: Ie6385f85560fefa7e7c9dca72cb5e2e914d4507a
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.
Related: OS#3369
Change-Id: Ide795092b656c9f0eb92a075d8f662944089019f
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.
Related: OS#3369
Change-Id: I0348f65a2ac184ba6b001e5130dfc8124e657367
Each access list will have their own counters. Have only one in the
config so the script generating the counter documentation doesn't repeat
itself.
Change-Id: I01b6e5af9cf84cf1b8d313ac47ab6b77fc598f4c
62825cc8eb4e26d58d32a0af72b17256b185af61 (osmocom-bb)
started to use the python module enum which not part of the standard
libary of python 2.
Change-Id: I70b7f1b43a1e121114a924c09614d6eddc801881
Configure each osmo-* program to send GSMTAP log output to the IP of the
docker container, which runs the testsuite (and therefore runs tcpdump).
Related: https://lists.osmocom.org/pipermail/openbsc/2019-June/012946.html
Change-Id: I99e74f6ffb5b7d566cec35995bf067df414968d8
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
test runs.
Change-Id: Id6d13b233ebfd808d8dfe83b6d1d1ba20c3392c8
Provide all build dependencies needed to pass ./configure of most
Osmocom repositories. This will be used to run osmo-release-tarballs.sh
in jenkins.
Related: OS#3870
Change-Id: I991fe41a1f55ccd6a66815ec3d7f239850397d9a
Change default from osmo-interact-vty.py to osmo_interact_vty.py, which
is the name of the script in osmo-python-tests.git.
Check if that script is in PATH before building and running the docker
container.
Change-Id: I763c7379b710160e0155f1fde091137754141335
The way our counter reporting works is that each counter group is
reported even if the same one exists multiple times. To avoid that
change the default config (used by regen_doc.sh) to only configure one
bts / bsc.
Change-Id: I57468d983580b5ed4f15961ac1eac9bed9096556
Related: OS#1700
This does not break ttcn3-sgsn-test since it uses a custom config file
with the correct IPs.
Change-Id: I2a922139c50d06217e5e6105ea65bf673daa10a8
Related: OS#1700
Don't bind to a specific IP otherwise starting osmo-mgw will fail (if we
don't configure that exact IP address)
Related: OS#1700
Change-Id: Ic5828957a29d4f317e1ebf4f03b5f5359f6250e8
The osmo-nitb-master image can run not only osmo-nitb, but also
osmo-bsc_nat. In that case we can't use the default command from
Dockerfile, but should provide our own. This argument makes it possible
to do so.
Change-Id: I52c3cb2cdcfb143e71ac2c1aa40bb466e41a0f5c
Related: OS#1700
This script needs access to the VTY interface, so I changed some
remaining config files to bind the VTY interface to 0.0.0.0.
There are a couple of services that do that already.
Related: OS#1700
Change-Id: Ic5cf7f59de0c18d4c5568b89433c2b11db2a72a5
When fixing the permissions at the end of a test run, it really doesn't
matter if we're running a current debian-stretch-build image, or if we
are using an ancient one. All we need is a 'chmod' binary.
Change-Id: Ib008ee72f40aeefb307c0ba74a57b70daae9d07b
Related: OS#4060
Other tests already do it, and allows using the CTRL iface in docker
setups where 127.0.0.1 is not used.
Change-Id: I6f16dc322d38f9f0870241f3416c81df8ec5481b
Latest tagged version of osmo-msc doesn't support "osmux on/off" VTY
commands, so we have to enable osmux use on that version to avoid most
TTCN3 tests failing during set up phase.
Depends: osmo-ttcn3-hacks.git I53d58b2d905905ebf1df322d0389b3715a48212f
Change-Id: I6b3be3981978661de2fa90be130f6f1811a3d1f9
Recent commit added bits to disable "osmux on/off" vty commands on
"-latest" tested, but forgot to add required line in
sccplite/BSC_Tests.cfg for sed command in jenkins.sh script to work.
Fixes: 2cdab85e5f
Change-Id: I9b4ce2d7151d65b4c83417a59fd01672971b3937
Run the testsuite one more time; this time for OML tests which
require us to run without a BSC. We can run those with trxcon
and omso-bts-trx and don't need virtphy for them.
Related: OS#4031
Depends: osmo-ttcn3-hacks I82bb85b684d2db3a6b1e96a68ffde03e22affa6b
Change-Id: I97db9c74c56ca93c75e5e5226955799cd945eec0
Some tests require GPRS features not yet present in trxcon, so we have
to fall back using virtphy.
Change-Id: I2f17f03194a4dfa0abca51b0d3e22b3934d08a9a
Pau Espin
Alexander Couzens
Harald Welte
Oliver Smith
Daniel Willmann
Eric Wild