Adjust the SCCPlite osmo-bsc.cfg according to changes applied in osmo-bsc.cfg,
which were obviously forgotten to also apply to the SCCPlite test runs.
Make the SI2quater config reflect that of the AoIP osmo-bsc.cfg.
Change-Id: I4dbabcc28309424a336d2a052a067484d17663ac
Adjust the SCCPlite osmo-bsc.cfg according to changes applied in osmo-bsc.cfg,
which were obviously forgotten to also apply to the SCCPlite test runs.
These handover config changes should fix the TC_ho_* tests in
ttcn3-bsc-sccplite.
Change-Id: I9694863b2db6be6384d1d6ffb35fc477fe774d02
Forgot to also adjust the SCCPlite structure in previous commit
c7b52048e6, which broke SCCPlite testing.
Change-Id: I923e398ccd4bdd31c8325de1a850fe4c3236db79
This only enables ttcn to be able to connect multiple MSCs. To be able to use
this in the BSC_Tests, osmo-bsc.cfg needs adjusting in an upcoming patch; tests
using this are in osmo-ttcn3-hacks I21cbab193cd0de2e5692665442eae113d5f61904.
Depends: Ibb36695b7c31f7b04eec6c5d59522fc0779b3c2f (osmo-ttcn3-hacks)
Change-Id: I1986e4ef43beee161c82193694421b56136c1afe
Don't list debian-stretch-build and debian-stretch-titan as dependencies
anymore, now that docker_images_require finds them automatically.
Related: OS#4564
Change-Id: I3cb6b693f3dd9df84fb29c0217bb3dae454cc18f
EGPRS Packet Channel Request cannot be enabled in 'GPRS only' mode
anyway. Moreover, this command was deprecated. Let's just remove it.
Change-Id: I03733490d9c4bf78a748d22874e550e015fbab78
In the recent osmo-bsc master, this configuration parameter has
been removed, so it fails to start due to "unknown parameter".
Change-Id: I8f763a4b35f80f4db637bebdd8e802a835a9fd2d
This configuration option is unused. Related: the IMSI filtering access list is
being dropped from osmo-bsc, which might cause test fallout.
Related: I89727af5387e8360362e995fdee959883c37d89a (osmo-bsc)
Change-Id: Ied8d766ba230b93cb1185fc8b1a77f5540dfdbc1
osmo-bsc does not use an rtp-base for years, ever since we're using an MGW.
Related: Id14fa3066ca5d472a817593074a6222f159168a8
Change-Id: I267840ecb816e9de6d89ebbacb3e296c59fad57c
Allow to pass options to each "docker run" line in the various
jenkins.sh scripts. I'm using this to run the testsuites and Osmocom
components in docker with the same configurations as jenkins, but with
Osmocom and testsuite binaries built outside and mounted into the
containers:
DOCKER_ARGS="-v /usr/local:/usr/local:ro -v $hacks:/osmo-ttcn3-hacks:ro"
This allows very short test cycles without a second set of configs. The
full script that makes use of this feature is in osmo-dev.git,
ttcn3/ttcn3.sh.
Change-Id: I8d1f78aee926f8f6ec0b704e16639bc83f525816
As of Change-Id Id965295dfe04f8bd5ce831db70c86f67b8dc290b the
bogus 'NAT' log category has been removed from osmo-bsc.
Change-Id: Ie2afacfc15589c26238214cddc00baaf80e993c1
for some strange reason, the tests developed + merged in September 2019
are not yet automatically executed. Let's fix that.
"latest" should work fine, the BSC side code was already present in 1.6.0
Change-Id: I4408265d1be900359256f5cab553893d03cc8362
The logging categories cc and mgcp are obsolete. The tests still contain
logging statements with those categories, which makes osmo-bsc
terminate during startup while parsing the configuration file.
Change-Id: Ifd6bf46b73420c0443f997ea953318710544b751
Since libosmo-sccp.git 89407619a31a4332bdb59e7921b99a29b7d6e00c it is
not allowed to use routing ctx != 0 for IPA AS.
Change-Id: If3e883aa988ffa1686f1363d5d5d4dbb21ce36c7
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
Analogous to osmo-ttcn3-hacks patch If44dd6b578cdc55076c8180707d1c2d69fe5f2a8,
also remove the neighbor config from osmo-bsc.cfg here.
Change-Id: I23d9a2046709452f4d3904230871f7421c6987a9
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
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
Latest tagged version of osmo-bsc 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 I61e4c59b2926f3f70cb6d0190a8683861e54179a
Change-Id: I745b210f43cb147d323a15f78c294f70ee077729
Replace 'git checkout -f -B $BRANCH origin/$BRANCH && \' in all
Dockerfiles that accept branch variables ($OSMO_TTCN3_BRANCH,
$OSMO_MGW_BRANCH, ...) with the following:
git checkout $BRANCH && \
(git symbolic-ref -q HEAD && git reset --hard origin/$BRANCH || exit 1); \
This allows using branch names and commit hashes in the $BRANCH
variables. Using commits is needed for the bisect script added in [1].
The second line ("(git symbolic...") checks if we are in detached HEAD
state after the checkout, and if we are not, pulls in all new commits
from origin/$BRANCH. Note that it ends in ';' instead of '&&', because
the command in the next line should be executed even if
"git symbolic-ref" does not exit with 0 (detached HEAD state).
Here is an example, to illustrate that the new command does the right
thing. Clone a repository and be 50 commits behind origin/master:
$ git clone "https://git.osmocom.org/osmo-mgw"
$ cd osmo-mgw
$ git reset --hard origin/master~50
With BRANCH="master":
$ git checkout master && \
(git symbolic-ref -q HEAD && git reset --hard origin/master || exit 1); \
echo "done"
Already on 'master'
...
done
$ git status
Your branch is up-to-date with 'origin/master'.
With BRANCH="85978d":
$ git checkout 85978d && \
(git symbolic-ref -q HEAD && git reset --hard origin/85978d || exit 1); \
echo "done"
Note: checking out '85978d'.
...
done
$ git status
HEAD detached at 85978dad
Related previous changes:
* [2] made it work for commit hashes, but broke using branch names other
than master, and pulling in new commits from master
* [3] made branches other than master work again, but did not fix
pulling in new commits from master
* [4] reverted [3] and the git checkout related part from [2]
[1] Change-Id: I11f7e61a9b30d58a0fdfcaf77dde447806bf661f
[2] Change-Id: If3bc5fae07cf63c4fef68306be4c4328660bc869
[3] Change-Id: I2ff745c8d19b777d876170d5717c082ceb68a1f3
[4] Change-Id: Ie6da0f9ea96f11407e38545a6b3cf22ef9cadc25
Related: OS#4015
Change-Id: I4004980baf0b7d6096702b6f3067ccbdb369a28c
Unfortuately this commit will check out *local* master (i.e. the
previous checkout) rather than the origin/master as it's supposed to
be. This means that ever since merging this patch, our ttcn3 tests
were running some "undefined" stale versions and not current master.
This reverts commit 26565bb729.
Change-Id: Ie6da0f9ea96f11407e38545a6b3cf22ef9cadc25
Replace the following statements:
a) "git checkout -f -B $BRANCH origin/$BRANCH"
b) "git checkout -f -B $BRANCH $BRANCH"
with:
c) "git checkout -f $BRANCH"
Regarding a), we don't need to specify 'origin/' for each branch, since
we are cloning the repositories in the same Dockerfile, and therefore we
know for sure that there is only one remote and branch names won't be
ambiguous. Removing the 'origin/' allows to put commit hashes into the
branch variables (like done in the new bisect script [1]).
Version b) does not work with branch names:
$ git checkout -f -B osmith/check-imei-before-lu osmith/check-imei-before-lu
fatal: Cannot update paths and switch to branch 'osmith/check-imei-before-lu' at the same time.
Did you intend to checkout 'osmith/check-imei-before-lu' which can not be resolved as commit?
New version c) works with both commits and branches, and it is shorter.
[1] Change-Id: I11f7e61a9b30d58a0fdfcaf77dde447806bf661f
Change-Id: I2ff745c8d19b777d876170d5717c082ceb68a1f3
This is quite useful when looking at jenkins logs to know which exact
version was built at the time.
Change-Id: Id52c382b454e2beecf46820752aeff15b2c1a0ae
Currently no EARFCN is set in osmo-bsc.cfg. This setting is required for
TC_chan_rel_hard_clear_csfb to function
Change-Id: I929c0b2927eb78573b7208683cf610be6be8812a
Related: OS#3852
Since Ib2335d02ea545aff837aadd49f15b2fdb418c46e, this VTY option
is deprecated in osmo-bsc, so let's actualize the config files.
Change-Id: I709e1afd2a9cccdc92eec312dff607947a10c299
Default value "master" of the IMAGE_SUFFIX environment variable can be
changed to "latest" to test the latest stable builds instead of the
nightly ones. Use docker_images_require() to make sure that the required
images are existing and up-to-date before running the tests.
Related: OS#3268
Change-Id: Idbb708ab16cb71bab5069127945b63388222369e
This mirrors osmo-ttcn3-hacks change:
"bsc: inter-BSC HO: add TC_ho_out_of_this_bsc, TC_ho_into_this_bsc"
change-id Id22852d4be7f127d827e7a8beeec55db27c07f03
(As well as removal of the 'add' keyword in change-id
I6a83a8d4ba61b87905c6fae457d4b4eb6078dce9 after osmo-bsc change
I143f21f6069d1a86096cc8240cf69eb7ea9c8ac8.)
Related: OS#2283
Change-Id: I077c2ad2ede900ec43f55655bd740651d3bbe83d
Instead of hardcoding laforge's username in all FROM statements in the
Dockerfiles, make use of the USER variable (as passed through by the
"make/Makefile" with "docker build --build-arg USER=..."). Thanks to
fixeria for proposing this fix!
This requires running docker-ce, old versions of docker (such as the
one in the official repositories of the latest Fedora) don't support
variables in the FROM line. But docker-ce can be installed after
adding docker's 3rd party repositories.
Closes: OS#3457
Change-Id: Ic5f11c8a4e247f632cb6aea6d147e94c53e0130f
The osmo-sip-connector test is already using 172.18.11.x, let's migrate
sccplite to 172.18.12.x to prevent any conflicts when running both tests
on the same build slave (docker instance).
Change-Id: I96beed1f5e01bdb8e77e20f77a459aa006de10fe
Previous to this commit, log messages were not being merged if tests
were resolved as failed (test-suite.sh ending with exit code != 0),
which can happen if at least one test failed.
Change-Id: If293fc2d3182ef2a7b997faa8b41129a9dd89c45
The existing dest config + jenkins.sh test 3GPP AoIP operation,
while the new set of configs + jenkins-sccplite.sh are testing
IPA/SCCPlite operation of osmo-bsc.
Change-Id: Ief0799a8f7d378dc3831e7988c9175166c82eace
The osmo-bsc configuration file used on Jenkins assigned wrong location
area codes to BTS 1 and 2. This fix should make TC_paging_imsi_nochan_lac
and TC_paging_imsi_nochan_lai pass on Jenkins.
Change-Id: Id35a85804c4a07f6c4136ef4570b4e21e250b9cd
To remove code dup and prepare a change to where logs are written, add
collect_logs() to jenkins_common.sh and call that from each jenkins.sh after
the tests are done.
The 'rm -rf' is already done before a test starts. No need to do that again
after each test.
Change-Id: I5d8472ec36b07c828685b1bd7718e31392d168a3
After merging Change-Id: Ie844c4de62e0ef5d5c4c366185968211a7f6d676
in osmo-ttcn3-hacks, the module parameters for BSSAP configuration
require one extra argument.
Change-Id: I2a0011bc6f7bdf013005d1ea36da591673344eed
Related: OS#2544
This is no longer needed as the fix for https://osmocom.org/issues/2718
has been merged to master of osmo-ttcn3-hacks
Change-Id: Ia0c1c134405fdbce1c65059d705827f1a643e774
Related: OS#2718