testing-farm:centos-stream-10-x86_64:e2e-ffi failing
- Dominant language
- Shell
- Stars
- 37
- Forks
- 36
- Avg merge
- 10h 36m
- Merged PRs (30d)
- 2
Description
Two error types
1) "Failed to connect to system scope bus via ...."
[ INFO ] PASS: Service QM is Active.
Failed to connect to system scope bus via local transport: No such file or directory
logs
https://artifacts.dev.testing-farm.io/3895abb0-5f08-40c1-87aa-c5781fd3c146/work-ffiyhej451z/plans/e2e/ffi/execute/data/guest/default-0/tests/ffi/qm_nested-19/output.txt
2) "Failed to obtain podman configuration: decode configuration "/usr/share/containers/storage.conf": toml: line 51 (last key "storage.options"): expected '.' or '=', but got 'c' instead"
logs
https://artifacts.dev.testing-farm.io/3895abb0-5f08-40c1-87aa-c5781fd3c146/work-ffiyhej451z/plans/e2e/ffi/execute/data/guest/default-0/tests/ffi/agent-flood-24/output.txt
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked output logs for qm_nested-19 and agent-flood-24 to separate the system-bus failure from the storage configuration parse failure. Inspect the reported /usr/share/containers/storage.conf content and the e2e-ffi testing-farm setup. Done means the CentOS Stream 10 x86_64 e2e-ffi checks complete without either error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, shell
- Domain
- operating-systems, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100