dynamic-loc-call fails to register channels

Bug #2045657 reported by Manuel Diewald
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dahdi-linux (Ubuntu)
New
Undecided
Unassigned
Lunar
New
Undecided
Unassigned

Bug Description

The issue can be observed with lunar:linux-gcp arm64. The issue was investigated for the 6.2.0-1020.22 release. The full log can be checked here: https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/arm64/d/dahdi-linux/20231201_174132_8742e@/log.gz

dynamic-loc-call will fail with:

[E] Spans not created or channels not properly registered in Asterisk.

Unlike LP: #2023570, this seems to be a timeout issue. The test script will sleep for 5 seconds before checking whether the spans were created and the channels are registered:

 # The spans will get automatically created and configured in Asterisk
 # using the udev hooks. It should take less than a second
 sleep 5
        if [ `lsdahdi | grep '(In use)' | wc -l ` != "$num_chans" ]; then

The spans are created but appear to not be registered in time. By adjusting the time that the test will sleep before checking the channels, the test will succeed. In a local VM, sleeping for 10 seconds will make the test pass. In conclusion, this is not an issue with the kernel or the module but rather with the test setup.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.