Project

General

Profile

Actions

action #152551

closed

test fails in rootless_podman: wrong configuration

Added by dimstar 5 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2023-12-13
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

TW switched from CNI (as default) to netavark. The module podman_netavark is reverting the config back to CNI though - but the cni-plugins package is not installed, which results in this error.

A cloned job with podman_netavark excluded confirms rootless_podman passing as expected: https://openqa.opensuse.org/tests/3808960#step/rootless_podman/1

openQA test in scenario microos-Tumbleweed-DVD-x86_64-container-host@64bit fails in
rootless_podman

Test suite description

Reproducible

Fails since (at least) Build 20231212

Expected result

Last good: 20231211 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by szarate 5 months ago

Actions #2

Updated by pdostal 5 months ago

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

Updated by dimstar 5 months ago

Actions #4

Updated by ph03nix 5 months ago

szarate wrote in #note-1:

@ph03nix

thanks!

Actions #5

Updated by openqa_review 4 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: containers_host_podman
https://openqa.opensuse.org/tests/3840006#step/podman_firewall/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions #6

Updated by pdostal 4 months ago

  • Status changed from In Progress to Resolved

Not failing any more.

Actions

Also available in: Atom PDF