Skip to content

Changes

Summary

  1. ttcn3-ggsn-test-ogs: run smf in 4g only mode (details)
  2. Revert "ttcn3-docker-run.sh: Fix dumpcap failing to access /data inside (details)
Commit 141dd4f018a34037113fbe8a21f67843533184e0 by Oliver Smith
ttcn3-ggsn-test-ogs: run smf in 4g only mode

Remove the SBI related configuration, so open5gs-smf does not attempt to
connect to the NRF every few seconds.

Fix for:
  [sbi] WARNING: [299d78ae-fae5-41ee-84a3-dbd9fa117ce7] Retry registration with NRF (../lib/sbi/nf-sm.c:182)
  [sbi] WARNING: [7] Failed to connect to 127.0.1.10 port 7777 after 200 ms: Couldn't connect to server (../lib/sbi/client.c:698)

Change-Id: I61d60e6e71b671c3deb20cc7ff8abb81ea4d5f03
The file was modified ttcn3-ggsn-test/ogs/open5gs-smf-master.yaml
Commit 951082d2c1fc27acce0548d130ed49d69c5fe564 by Oliver Smith
Revert "ttcn3-docker-run.sh: Fix dumpcap failing to access /data inside docker"

This reverts commit 2b9c8e3db8cf77c5ce5c3f888365f983f3ee8d76, as it
causes a lot of testsuites to fail with e.g.

  + network_replace_subnet_in_configs
  + set +x
  Applying SUBNET=161 to: /home/osmocom-build/jenkins/workspace/ttcn3-ggsn-test/logs/ggsn-all/osmo-ggsn.cfg
  Applying SUBNET=161 to: /home/osmocom-build/jenkins/workspace/ttcn3-ggsn-test/logs/ggsn-tester-all/GGSN_Tests.cfg
  sed: couldn't open temporary file /home/osmocom-build/jenkins/workspace/ttcn3-ggsn-test/logs/ggsn-tester-all/sedsByWIc: Permission denied

Let's discuss how to fix the dumpcap problem instead in OS#6455.

Change-Id: Ic98e8206d8251060b777fc7d0b4497ba3e1caf7f
The file was modified common/ttcn3-docker-run.sh