Actions
action #66763
closed[sle][functional][y][sporadic] Investigate vnc got shutdown unexpectively in PowerVM
Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - SLE 15 SP2
Start date:
2020-05-13
Due date:
2020-06-02
% Done:
0%
Estimated time:
Difficulty:
Description
Observation¶
openQA test in scenario sle-15-SP2-Online-ppc64le-autoyast_mini@ppc64le-hmc-single-disk fails in
installation
Since build 190.2, right after the installation finishes in this AutoYaST job, we have found issue where vnc is closed unexpectedly and there are not logs to figure out why this happened. We should try to retrieve some logs or any information at this point.
Once investigated, we should consider if it could be a product bug.
Reproducible¶
Fails since (at least) Build 190.2
Updated by JERiveraMoya almost 4 years ago
- Subject changed from [sle][functional][y] Improve handling of unexpected failures in PowerVM to Improve handling of unexpected failures in PowerVM
- Description updated (diff)
Updated by JERiveraMoya almost 4 years ago
- Subject changed from Improve handling of unexpected failures in PowerVM to [sle][functional][y] Investiage vnc got shutdown unexpectively in PowerVM
- Description updated (diff)
- Category changed from Enhancement to existing tests to Bugs in existing tests
Updated by JERiveraMoya almost 4 years ago
- Subject changed from [sle][functional][y] Investiage vnc got shutdown unexpectively in PowerVM to [sle][functional][y] Investigate vnc got shutdown unexpectively in PowerVM
Updated by riafarov almost 4 years ago
- Due date set to 2020-06-02
- Priority changed from Normal to High
- Target version set to SLE 15 SP2
Updated by riafarov almost 4 years ago
- Subject changed from [sle][functional][y] Investigate vnc got shutdown unexpectively in PowerVM to [sle][functional][y][sporadic] Investigate vnc got shutdown unexpectively in PowerVM
Updated by riafarov almost 4 years ago
- Status changed from New to Resolved
So problem is that on powerVM we have to predict when reboot occurs, in the failed run we failed to match needle with autoyast-stage1-reboot-upcoming tag. I've created additional one, which should remove sporadic issues. Resolving for now.
Actions