action #115778
closed
[security][fips] test fails in openvswitch_ssl
Added by punkioudi over 1 year ago.
Updated over 1 year ago.
Category:
Bugs in existing tests
Description
It seems like a product bug:
Test died: 'zypper -n in python python-base openvswitch' failed with code 104 (ZYPPER_EXIT_INF_CAP_NOT_FOUND)
No provider of 'python-base' found.
Some investigation is needed in order to make sure if any other module is needed to be activated for python-base package or if it is a product bug :)
Observation¶
openQA test in scenario sle-15-SP5-Online-s390x-fips_env_mode_tests_crypt_tool@s390x-kvm-sle12 fails in
openvswitch_ssl
Test suite description¶
Maintainer: bchou@suse.com.
Workaround for FIPS single module mode
Reproducible¶
Fails since (at least) Build 15.2 (current job)
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: fips_ker_mode_tests_crypt_tool
https://openqa.suse.de/tests/9417435#step/journald_fss/1
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.
The openvswitch would be fail in SP5 too since the POX and python3 are updated. Our test case need to be refactor to fulfill the new version. There are some discussion bug we opened, I will also comment it here later.
Sorry I missed to point the bug last time as this bug was closed.
We had a series of discussions internally and with the developer. The problem we found currently is about that the POX and python3 are in the latest image, the original test case will be outdated currently. I think at the moment we can remove the test case from the openQA test suite and refactor another new case for the new openvswitch, as the POX version is also updated and it is not controlled by our own now.
https://bugzilla.suse.com/show_bug.cgi?id=1196316
1196316 - [SLES15SP4][Build 101.1][SECURITY][FIPS] openvswitch_ssl: RuntimeError: SSL is not available
- Status changed from New to In Progress
- Assignee set to pstivanin
- % Done changed from 0 to 80
The current version of pox requires python 2.7, while on 15-SP5 we ship only 3.6
- % Done changed from 80 to 100
- Status changed from In Progress to Resolved
Also available in: Atom
PDF