action #166337
closed
[security][15-SP7] test fails in w3m_https
Added by amanzini 4 months ago.
Updated 3 months ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-SP7-Online-x86_64-fips_env_mode_tests_crypt_web@ipmi-tyrion fails in
w3m_https
Test suite description¶
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.
Reproducible¶
Fails since (at least) Build 8.2
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
First observation¶
no fips pattern for 15-SP7 ?
- Estimated time set to 8.00 h
weird thing is that curl and wget passes; trying to check if it depends on the website contacted or if it's IPMI related.
looking at login screen, the "last login date" is in the future: https://openqa.suse.de/tests/15354393#step/wget_https/2 .
Better to have a time sync step on startup
- Status changed from New to Feedback
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
- 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: fips_env_mode_tests_crypt_web@ipmi-tyrion
https://openqa.suse.de/tests/15238731#step/w3m_https/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.
- Status changed from Feedback to Resolved
The referred results is older than the fix.
Also available in: Atom
PDF