action #112580
closed[qe-core] Upgraded system shutdown too slow
0%
Description
Observation¶
Most upgrade tests no longer shut down in the timeout window, but reach it delayed.
We should identify the reason for it and file the relevant product bugs (possibly more than one)
This ticket serves as tracker to identify the issues and then direct resources as appropriate
openQA test in scenario opensuse-Tumbleweed-NET-x86_64-zdup-Leap-15.3-kde@64bit fails in
shutdown
Test suite description¶
Reproducible¶
Fails since (at least) Build 20220614 (current job)
Expected result¶
Last good: 20220613 (or more recent)
Further details¶
Always latest result in this scenario: latest
Acceptance Criteria¶
- Identify possible reasons for the shutdown taking long time and document them on this ticket
- Create follow-up tickets (when needed) to mitigate the issue on different backends
Updated by szarate almost 2 years ago
- Sprint set to QE-Core: June Sprint (Jun 08 - Jul 06)
- Tags set to bugbusters
- Subject changed from Upgraded system shutdown too slow to [qe-core] Upgraded system shutdown too slow
- Description updated (diff)
- Status changed from New to Workable
- Target version set to QE-Core: Ready
Perhaps https://bugzilla.suse.com/show_bug.cgi?id=1199531#c1 is a good starting point, I guess somebody from the bugbusters can add the list of the timers
Updated by dimstar almost 2 years ago
https://bugzilla.opensuse.org/show_bug.cgi?id=1200682 seems to correlate closely to the upgrade time plan.
The kids also hunt in this direction
Updated by szarate almost 2 years ago
I guess that at this stage, installing and getting support info would not hurt, for multiple products: https://bugzilla.opensuse.org/show_bug.cgi?id=1200682#c3
Updated by szarate almost 2 years ago
- Related to action #89329: [qe-core] test fails in shutdown - Machine didn't shut down added
Updated by favogt almost 2 years ago
- Status changed from Workable to Rejected
This is https://bugzilla.opensuse.org/show_bug.cgi?id=1200682, a product bug.