Project

General

Profile

Actions

Bug #5913

closed

ttcn3-pgw-test is broken (open5gs components fail to start)

Added by fixeria about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
02/20/2023
Due date:
% Done:

100%

Spec Reference:

Description

Since recently, all testcases are failing in ttcn3-pgw-test:

https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-pgw-test/326/

The problem is that some open5gs components fail to start:

https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-pgw-test/326/artifact/logs/pgw/open5gs-smfd.out/*view*/

Open5GS daemon v2.6.0-35-g0df402b

02/18 14:00:24.733: [app] INFO: Configuration: '/data/open5gs-smf.yaml' (../lib/app/ogs-init.c:126)
02/18 14:00:24.746: [sbi] ERROR: TLS enabled but no server key (../lib/sbi/context.c:186)
02/18 14:00:24.746: [app] ERROR: Failed to intialize SMF (../src/smf/app.c:28)
02/18 14:00:24.746: [app] FATAL: Open5GS initialization failed. Aborted (../src/main.c:219)

https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-pgw-test/326/artifact/logs/pgw/open5gs-nrf.out/*view*/

Open5GS daemon v2.6.0-35-g0df402b

02/18 14:00:23.789: [app] INFO: Configuration: '/data/open5gs-nrf.yaml' (../lib/app/ogs-init.c:126)
02/18 14:00:23.791: [sbi] ERROR: TLS enabled but no server key (../lib/sbi/context.c:186)
02/18 14:00:23.791: [app] ERROR: Failed to intialize NRF (../src/nrf/app.c:28)
02/18 14:00:23.791: [app] FATAL: Open5GS initialization failed. Aborted (../src/main.c:219)

Interestingly enough, nowhere in our config files TLS is enabled explicitly.


Files

open5gs-nrf.yaml open5gs-nrf.yaml 3.15 KB fixeria, 02/20/2023 10:20 AM
open5gs-smf.yaml open5gs-smf.yaml 11.4 KB fixeria, 02/20/2023 10:20 AM
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)