action #96438
open[security][CC] test case '[24] basic_strongswan' in 'trustedprograms' fails
Added by Xiaojing_liu over 2 years ago. Updated about 1 month ago.
0%
Description
In the audit test 'trustedprograms', the case '[24] basic_strongswan' fails.
It's related ipsec and strongswan, need to be investigated.
Files
| test_basic_strongswan.bash (3.58 KB) test_basic_strongswan.bash | amanzini, 2022-10-27 10:24 |
Updated by llzhao over 2 years ago
- Assignee set to rfan1
- Estimated time set to 32.00 h
Updated by Xiaojing_liu almost 2 years ago
- Subject changed from [sle][security][sle15sp4][CC]test case '[24] basic_strongswan' in 'trustedprograms' fails to [sle][security][CC][backlog]test case '[24] basic_strongswan' in 'trustedprograms' fails
- Priority changed from Normal to Low
- Target version set to future
Updated by rfan1 almost 2 years ago
- Assignee changed from Xiaojing_liu to pstivanin
Updated by rfan1 almost 2 years ago
At the time we started to carry out the CC tests, there were some cases failed there [base line is failed as well for now].
This is the one we recorded and can't know why this case was failed.
Updated by pstivanin over 1 year ago
- Subject changed from [sle][security][CC][backlog]test case '[24] basic_strongswan' in 'trustedprograms' fails to [security][CC] test case '[24] basic_strongswan' in 'trustedprograms' fails
- Category changed from Spike/Research to Bugs in existing tests
- Target version deleted (
future) - Start date deleted (
2021-08-02) - Estimated time deleted (
32.00 h)
Updated by pstivanin over 1 year ago
Until we work on this ticket, I've added a 'record_soft_failure' to remind us that there's a test failing (while now it's just green)
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15640
Updated by openqa_review over 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_audit-test-part2
https://openqa.suse.de/tests/9680005
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by amanzini over 1 year ago
the test runs itself a test suite, a collection of bash scripts downloaded from a repository:
our $default_code_base = get_var('IPSEC_TEST') ? 'https://gitlab.suse.de/qe-security/ipsec/-/archive/main/ipsec-main.tar' : 'https://gitlab.suse.de/security/audit-test-sle15/-/archive/master/audit-test-sle15-master.tar';
then each result of the test suite is compared against a reference "baseline", also stored in the same archive.
in detail, for testcase [24] basic_strongswan , the current baseline says that the output must be "FAIL" , so it appears like an expected failure.
we must understand/ask if
- these pre-conditions are still valid and test is expected to fail
- need to update the algo list on the bash script (see attachment) with newer crypto algorithms
Updated by openqa_review over 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_audit-test-part2
https://openqa.suse.de/tests/9969311
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by openqa_review over 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_audit-test-part2
https://openqa.suse.de/tests/10088083
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.
Updated by openqa_review about 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_audit-test-part2
https://openqa.suse.de/tests/10575192
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 112 days if nothing changes in this ticket.
Updated by openqa_review 9 months ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_audit-test-part2
https://openqa.suse.de/tests/11575404
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 216 days if nothing changes in this ticket.
Updated by JERiveraMoya 8 months ago
- Status changed from Workable to In Progress
- Assignee set to JERiveraMoya
Updated by JERiveraMoya 7 months ago
Discussed with @jsegitz that this test never had a proper network setup to run in openQA.
Therefore it is unrelated that this old script (written 8 years ago) has outdated ciphers, even if we update them with new ciphers for sle 15 (in the file are the ones for sle 12) we will never be able to run it with an specific network configuration for ipsec.
See Slack conversation.
Updated by openqa_review 7 months ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_audit-test-part2
https://openqa.suse.de/tests/11575404
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by JERiveraMoya 6 months ago
- Status changed from In Progress to Resolved
Let's resolve it as the work is done, but still pending the merge.
Updated by openqa_review 5 months ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_audit-test-part2
https://openqa.suse.de/tests/12831049
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 60 days if nothing changes in this ticket.
Updated by openqa_review 5 months ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_audit-test-part2
https://openqa.suse.de/tests/13076125
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 36 days if nothing changes in this ticket.
Updated by openqa_review 4 months ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_audit-test-part2
https://openqa.suse.de/tests/13174529
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by openqa_review 3 months ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_audit-test-part2
https://openqa.suse.de/tests/13371889
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.
Updated by openqa_review about 1 month ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: cc_audit-test-part2
https://openqa.suse.de/tests/11575404
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.