Two recent stratisd updates encountered an rpminspect test failure:
Both test failures look the same: Failed to fetch ./result.json: 404 Not Found .
https://artifacts.dev.testing-farm.io/9676f332-4819-44fc-905e-ee289a59acc2/
stratis-cli rpminspect check succeeds. We have not been able to get any stratisd rpminspect failiures by running rpminspect locally. We think that the failure we see in Bodhi must be due to the testing infrastructure failing, somehow.
We would like you to investigate this problem yourself, if it is your responsibility, or redirect our issue to the correct person. We do not believe that this is an rpminspect issue, because we can not reproduce it locally, so we have not filed an issue with rpminspect.
We have no pressing deadline for the solution of this problem as we are at liberty to ignore rpminspect failures when doing Fedora releases.
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, medium-trouble, ops
it looks like rpminspect is core dumping, based on this log file: https://artifacts.dev.testing-farm.io/9f6b9543-1e69-4fb8-bfb9-e90111151676/work-rpminspectd1psn1fa/log.txt . I think this may be a problem with rpminspect-runner, as the log says "Command returned '0' (success)." immediately after the core dump is reported. I'm logging an issue against rpminspect-runner and may be able to close this issue.
Issue filed: https://github.com/fedora-ci/rpminspect-runner/issues/143
I looked a bit and asked the #ci:fedoraproject.org room about it.
They suggested trying it locally in the container it uses:
https://github.com/fedora-ci/rpminspect-pipeline/blob/master/rpminspect.fmf#L18
Log in to comment on this ticket.