Skip to content
Unstable

Changes

Summary

  1. testenv: fix 'container crashed' detection (details)
  2. testenv: podman-main: set watchdog timer to 60s (details)
  3. statsd: Support f_statsd_snapshot() API when using VTY-triggered stats (details)
  4. hnbgw: Introduce module parameter mp_statsd_prefix (details)
  5. hnbgw: Introduce module parameter mp_pfcp_upf_node_id (details)
  6. hnbgw: Handle PFCP Assoc Setup procedure in test_CT (details)
  7. hnbgw: Introduce test TC_ps_iu_release_req_rua_disconnect (details)
Commit 106b6190e4dc976c366a3e7f96965107710230de by Oliver Smith
testenv: fix 'container crashed' detection

* When the testsuite stopped and using podman, check if it stopped
  because the container crashed and raise an exception.

* Even after 9eb5e696 ("testenv: make podman stop more robust") it
  happens sometimes in jenkins that the container gets stopped on
  purpose because the testsuite is done, but then the watchdog process
  prints an error saying it crashed (without actually stopping testenv
  at this point). Change the message to a debug message that just says
  it stopped, this should not be an error.

Related: OS#6607
Change-Id: I3c116719cdc00a99e27e5237ba3d57d5258b0919
The file was modified_testenv/testenv/testsuite.py
The file was modified_testenv/testenv/podman.py
Commit 2766aba0c4b02034e17c5b065585956d86d727f1 by Oliver Smith
testenv: podman-main: set watchdog timer to 60s

Increase the timer from 10s to 60s, as with 10s I see jobs failing with:

  ERROR: /tmp/watchdog was not created, exiting

In theory 10s should already be enough, my guess is that if a jenkins
node is currently under a lot of load then the feed command may take
several seconds and so we hit the previous timer. Even if this is not
the cause, I think it is good to rule it out.

Exiting after 60s if the jenkins job was (manually / with connection
loss) aborted is still relatively quick.

Related: OS#6607
Change-Id: Ide7a9d5bc395106cdaa47cec3aa746a978674c9e
The file was modified_testenv/data/scripts/testenv-podman-main.sh
Commit 7c8615e6c5127ff1554a81c3a1ca7b1699a36f4d by Pau Espin Pedrol
statsd: Support f_statsd_snapshot() API when using VTY-triggered stats report

Until now that API was only used in testsuites which relied on
time-trigerred reports. This commit also supports getting a given
snapshots if the IUT is configured to only trigger a report based on VTY
request.

Change-Id: I87d34e2f365d3b71ce328c08999be43d482326ad
The file was modifiedlibrary/StatsD_Checker.ttcnpp
Commit 1058dc9a2941c06cf192915ce1a04d808a2e56cd by Pau Espin Pedrol
hnbgw: Introduce module parameter mp_statsd_prefix

The value in that parameter depends on IUT configuration.

Change-Id: I007d45b8323831e8f3708d22c6a9bc6e9badd896
The file was modifiedhnbgw/HNBGW_Tests.ttcn
Commit f6584fb7049480391a0a3839416484054929e5cb by Pau Espin Pedrol
hnbgw: Introduce module parameter mp_pfcp_upf_node_id

This will allow using it later in HNBGW_Tests.ttcn file when waiting for
PFCP Assoc Req.

Change-Id: I2142289965adba0b457e865e10f0cfc9908b0bb2
The file was modifiedhnbgw/ConnHdlr.ttcn
The file was modifiedhnbgw/HNBGW_Tests.ttcn
Commit 86c44427a35bded24f4a037d76568e2b4c4e633e by Pau Espin Pedrol
hnbgw: Handle PFCP Assoc Setup procedure in test_CT

Handle PFCP Assoc Setup Req during PFCP initialization in main test_CT.
This simplifies test logic.

Depends: osmo-hnbgw.git Change-Id Ic71df8df83e97f4015077677e426c803f84d31ea
Change-Id: Ic5edecea86b9465c60f008e245a44cfce64c8ddb
The file was modifiedhnbgw/ConnHdlr.ttcn
The file was modifiedhnbgw/HNBGW_Tests.ttcn
Commit a0861ee1877ee1ba57eea0712f8e39d3ba897149 by Pau Espin Pedrol
hnbgw: Introduce test TC_ps_iu_release_req_rua_disconnect

Change-Id: Id24a5aed5255af77fbbd30521be70700a9bff1c9
The file was modifiedhnbgw/expected-results.xml
The file was modifiedhnbgw/HNBGW_Tests.ttcn