Actions
action #166997
closed[qe-core] test fails in suseconnect_scc - transactional_update reports 0 even if underlying command failed
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
Start date:
2024-09-18
Due date:
% Done:
0%
Estimated time:
Difficulty:
Description
Observation¶
The following is an excrept from the test:
<stream>' (signal: bus error (core dumped))
2024-09-17 18:13:22 Application returned with exit status 255.
2024-09-17 18:13:23 tukit 4.8.1 started
2024-09-17 18:13:23 Options: --discard close 4
2024-09-17 18:13:32 No changes to the root file system - discarding snapshot.
2024-09-17 18:13:32 Merging changes in /etc into the running system.
2024-09-17 18:13:33 Discarding snapshot 4.
2024-09-17 18:13:36 Transaction completed.
transactional-update finished
When transactional update finishes, it seems that if the application dies or returns a non-zero, it still would report that "everything is ok", by returning zero. We need to investigate and file a bug if its necessary
openQA test in scenario sle-micro-6.1-Default-ppc-4096-ppc64le-slem_docker._VR_17.1@ppc64le-emu fails in
suseconnect_scc
Test suite description¶
SLE Micro as container host tests using docker as container runtime (docker, docker firewall, etc).
Reproducible¶
Fails since (at least) Build VR
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Actions