Project

General

Profile

Actions

action #157330

closed

docker_firewall: fails to restart, errors in journal not available

Added by dimstar about 1 month ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2024-03-15
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

The test fails (which I believe to be a product bug https://bugzilla.opensuse.org/show_bug.cgi?id=1221458)

From an openQA PoV, what would be really helpful would be the journal being available when a service fails to restart (like most normal fail hanlder upload)

openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-container_host@64bit_virtio-2G fails in
docker_firewall

Test suite description

Container host tests on JeOS image.

Reproducible

Fails since (at least) Build 20240314

Expected result

Last good: 20240313 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by dimstar about 1 month ago

The journal is not being uploaded as the post_fail_hook aborts before reaching this point.

the post_fail_hook itself tries to restart docker again (failing the same as the regular run failed)- at which point the entire post_fail_hook is aborted - resulting in the missing journal/log upload

Actions #2

Updated by rbranco about 1 month ago

  • Status changed from New to In Progress
  • Assignee set to rbranco
Actions #3

Updated by dimstar about 1 month ago

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18900

Addresses the issue of the journal (and other debug info) not being collected in the post_fail_hook when restarting the service fails

Actions #4

Updated by dimstar about 1 month ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF