Bug 1226470 - [Build 93.5] openQA test fails in year_2038_detection -xen hvm system did not come back after changing date past year 2038
Summary: [Build 93.5] openQA test fails in year_2038_detection -xen hvm system did no...
Status: NEW
Alias: None
Product: PUBLIC SUSE Linux Enterprise Server 15 SP6
Classification: openSUSE
Component: XEN (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Xen Virtualization
QA Contact: Antoine Ginies
URL: https://openqa.suse.de/tests/14610891...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-18 08:59 UTC by Santiago Zarate
Modified: 2024-06-24 14:28 UTC (History)
2 users (show)

See Also:
Found By: openQA
Services Priority:
Business Priority:
Blocker: Yes
Marketing QA Status: ---
IT Deployment: ---
jbeulich: needinfo? (santiago.zarate)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Santiago Zarate 2024-06-18 08:59:01 UTC 
## Observation

openQA test in scenario sle-15-SP6-Online-x86_64-extra_tests_textmode@svirt-xen-hvm fails in
[year_2038_detection](https://openqa.suse.de/tests/14610891/modules/year_2038_detection/steps/33)

## Test suite description
Maintainer: QE Core, asmorodskyi,dheidler. Mainly console extratest 


## Reproducible

Fails since (at least) Build [93.5](https://openqa.suse.de/tests/14610891) (current job)


## Expected result

Last good: [93.2](https://openqa.suse.de/tests/14604396) (or more recent)


## Further details

Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=svirt-xen-hvm&test=extra_tests_textmode&version=15-SP6)
Comment 1 Santiago Zarate 2024-06-18 09:02:44 UTC 
This started happening only with the last build, Alice, have you seen it?
Comment 2 Jan Beulich 2024-06-24 14:28:35 UTC 
In order to consider whether we might be able to repro your scenario / observation, we'd need to know details on what exactly is being done for the test. Depending on what exactly "did not come back" means, pertinent log files would also be useful to supply _here_ (once again I can't access the links provided in #0).