Bug #4571
closedTTCN3-centos-sip-test: 4/5 tests failing
100%
Description
This log message seems related:
SIP_Test-SIP@3a8a7ddac7cd: Dynamic test case error: SIP Test Port: syntax error "v" -> unexpected character at character position 1.
https://jenkins.osmocom.org/jenkins/view/TTCN3-centos/job/TTCN3-centos-sip-test/
Updated by laforge over 3 years ago
Interestingly wireshark segfaults when trying to open https://jenkins.osmocom.org/jenkins/view/TTCN3-centos/job/TTCN3-centos-sip-test/lastSuccessfulBuild/artifact/logs/sip-tester/SIP_Tests.TC_mt_success_rel_sip.pcap - rebuilding current wireshark in the hope it actually allows me to look at the SIP messages.
Updated by laforge over 3 years ago
- Priority changed from Normal to High
From the IRC log:
23:07 <@LaF0rge> interestingly my wireshark segfaults when trying to open https://jenkins.osmocom.org/jenkins/view/TTCN3-centos/job/TTCN3-centos-sip-test/lastSuccessfulBuild/artifact/logs/sip-tester/SIP_Tests.TC_mt_success_rel_sip.pcap 23:09 < fixeria> does not crash on my machine :/ 23:10 < fixeria> so maybe rebuilding master would help 23:13 < fixeria> although my wireshark does not want to decode packet#18 as SIP (despite being forced to using "Decode As") and shows raw bytes instead 23:17 < fixeria> LaF0rge: maybe that's the problem - there is no SIP header at all 23:18 < fixeria> the payload starts with "v=0..o=Osmocom" 23:18 < fixeria> "Dynamic test case error: SIP Test Port: syntax error "v" -> unexpected character at character position 1."
So somehow the sofia-sip library used on Centos8 produces malformed SIP messages without any SIP header. This needs to be investigated.
Updated by Hoernchen over 3 years ago
- % Done changed from 0 to 50
The sofia-sip provided by Ubuntu works, but centos does not offer sofia-sip, so we provide our own version based on a pristine copy of the source code which is unmaintained since 2011. As it turns out Ubuntu has fixes applied to it relating to strict aliasing violations, so that is most likely the issue we're seeing here, too.
Updated by Hoernchen over 3 years ago
I ran the ttcn3 sip test from my host with a osmo-sip-connector in a centos container, and merely building a rpm from the opensuse forge spec file (https://build.opensuse.org/package/show/openSUSE:Factory/sofia-sip) + debian sofia-sip repo that is listed as package source for the deb/ubuntu packages (https://salsa.debian.org/ron/sofia-sip debian branch) works, while our own package linked from the forge package build does not. The most reasonable fix was suggested by laforge - just create a source tarball from this and push it to our obs build once which should then be built for centos only + remove the linked package from osmo-ci/scripts/osmocom-obs-link.sh, daniel can you do that?
Updated by daniel over 3 years ago
Can you check if the packages in https://build.opensuse.org/package/binaries/home:daniel_w:branches:openSUSE:Factory/sofia-sip/CentOS_8_Stream work for you?
If it does I can push it to osmocom:network...
Updated by roox over 3 years ago
daniel wrote:
Can you check if the packages in https://build.opensuse.org/package/binaries/home:daniel_w:branches:openSUSE:Factory/sofia-sip/CentOS_8_Stream work for you?
If it does I can push it to osmocom:network...
daniel I just cleaned up the ancient openSUSE package...
(source and patch are from the debian package)
https://build.opensuse.org/package/show/home:mnhauke/sofia-sip
https://build.opensuse.org/request/show/811245
Updated by daniel over 3 years ago
- Status changed from New to Resolved
- % Done changed from 50 to 100
roox wrote:
daniel I just cleaned up the ancient openSUSE package...
(source and patch are from the debian package)
https://build.opensuse.org/package/show/home:mnhauke/sofia-sip
https://build.opensuse.org/request/show/811245
Great, thanks!
With that package https://jenkins.osmocom.org/jenkins/view/TTCN3-centos/job/TTCN3-centos-sip-test/ is passing.
I'll redirect the link once the request went through.