During snv_26 ON-PIT run it was observed that all 26 persock2 testcases for
the STF ipsec-persock testsuite (version 1.9) failed on all architectures
and all modes. The remaining testcases (persock1, inheritance, bypass...)
have passed fine with the exception of the 2 override testcases which show
the same symptoms.
This testsuite passed all testcases during previous snv_25 PIT run.
All the testcases have the same problem, they fail due to connection timeout,
here's an extract from one of the failures:
Test_Case_Start| 129492 persock_persock/persock2-sha1-3des-sha1 | 19:06:03 0 |
stdout|
stdout| persock client to global server with sha1:3des:sha1
stdout|
stdout| Checking that 3des is supported on all systems...
stdout| Flushing IPsec policies on all systems...
stdout| Killing any existing servers on 129.156.229.209
stdout| Running tcp persock server on 129.156.229.209 with command:
stdout| server -t -p sha1:3des:sha1:unique
stdout| Process id is: 140671
stdout| Running tcp persock client on 129.156.228.182 with command:
stdout| client -t -d 129.156.229.209 -p sha1:3des:sha1:unique
stdout| Client wants: sha1:3des:sha1:REQUIRED:UNIQUE
stdout| After setsockopt(), client has: sha1:3des:sha1:REQUIRED:UNIQUE
stderr| Connection timed out...
stdout| debug logs saved in:
stdout| /var/tmp/ipsec-persock/results/persock2-sha1-3des-sha1.debug.129493
stdout| /var/tmp/ipsec-persock/results/persock2-sha1-3des-sha1.snoop.129493
stderr|
Test_Case_End| 129492 persock_persock/persock2-sha1-3des-sha1 | FAIL | 19:06:38 0 |
I've attached the persock2-sha1-3des-sha1.(debug|snoop) files to this bug report.
There has been several ipsec problems with snv_26 in PIT, i.e. CR6340735, and testsuites
that have been modified to work with the PKCS#11 v2.20 (new ef version 1.9 for this PSARC).