rpminspect - failed to fetch ./results.json - 404 not found #551

Open
opened 2026-04-01 18:03:33 +00:00 by buckaroogeek · 4 comments

In this PR for docker-buildx (https://src.fedoraproject.org/rpms/docker-buildx/pull-request/36), rpminspect is failing with Failed to fetch ./result.json: 404 Not Found.

Verbose.log contains:

Checking the component-specific rpminspect config file...
+ for ext in ${exts}
+ '[' -f rpminspect.yaml ']'
+ for ext in ${exts}
+ '[' -f rpminspect.json ']'
+ for ext in ${exts}
+ '[' -f rpminspect.dson ']'
+ rpm -qa
+ grep rpminspect
rpminspect-data-fedora-1.16-4.fc44.noarch
librpminspect-2.2-1.1.202603251926git23b5f2e8.x86_64
rpminspect-2.2-1.1.202603251926git23b5f2e8.x86_64
+ /usr/bin/rpminspect -c /usr/share/rpminspect/fedora.yaml --workdir /var/ARTIFACTS/work-rpminspecto0femzn6/rpminspect/discover/default-0/tests/workdir/ --format=json --output=/var/ARTIFACTS/work-rpminspecto0femzn6/rpminspect/execute/data/guest/default-0/rpminspect-1/data/result.json --verbose --release=fc45 docker-buildx-0.31.1-2.fc44 143911767
rpminspect: *** XML-RPC Fault: HTTP POST to URL 'https://koji.fedoraproject.org/kojihub' failed.  HTTP response code is 502, not 200 (-504)
In this PR for docker-buildx (https://src.fedoraproject.org/rpms/docker-buildx/pull-request/36), rpminspect is failing with `Failed to fetch ./result.json: 404 Not Found`. Verbose.log contains: ``` Checking the component-specific rpminspect config file... + for ext in ${exts} + '[' -f rpminspect.yaml ']' + for ext in ${exts} + '[' -f rpminspect.json ']' + for ext in ${exts} + '[' -f rpminspect.dson ']' + rpm -qa + grep rpminspect rpminspect-data-fedora-1.16-4.fc44.noarch librpminspect-2.2-1.1.202603251926git23b5f2e8.x86_64 rpminspect-2.2-1.1.202603251926git23b5f2e8.x86_64 + /usr/bin/rpminspect -c /usr/share/rpminspect/fedora.yaml --workdir /var/ARTIFACTS/work-rpminspecto0femzn6/rpminspect/discover/default-0/tests/workdir/ --format=json --output=/var/ARTIFACTS/work-rpminspecto0femzn6/rpminspect/execute/data/guest/default-0/rpminspect-1/data/result.json --verbose --release=fc45 docker-buildx-0.31.1-2.fc44 143911767 rpminspect: *** XML-RPC Fault: HTTP POST to URL 'https://koji.fedoraproject.org/kojihub' failed. HTTP response code is 502, not 200 (-504) ```
Author

Update. I ran /packit-ci test rpminspect a third time and the test worked. It failed 2 times with the above error.

Update. I ran `/packit-ci test rpminspect` a third time and the test worked. It failed 2 times with the above error.
Author

Update 3 separate PRs submitted today are showing this result for rpminspect, i.e. Failed to fetch ./result.json: 404 Not Found

https://src.fedoraproject.org/rpms/cri-o1.33/pull-request/11
https://src.fedoraproject.org/rpms/cri-o1.34/pull-request/9
https://src.fedoraproject.org/rpms/cri-o1.35/pull-request/4

Update 3 separate PRs submitted today are showing this result for rpminspect, i.e. `Failed to fetch ./result.json: 404 Not Found` https://src.fedoraproject.org/rpms/cri-o1.33/pull-request/11 https://src.fedoraproject.org/rpms/cri-o1.34/pull-request/9 https://src.fedoraproject.org/rpms/cri-o1.35/pull-request/4
Owner

There are completely different problems, but I will focus this issue tracker only on making the rpminspect results not display the 404 not found when such issues occur. Currently this is blocked by a consolidation refactoring in #548, but I will get back to this afterwards.

There are completely different problems, but I will focus this issue tracker only on making the rpminspect results not display the 404 not found when such issues occur. Currently this is blocked by a consolidation refactoring in #548, but I will get back to this afterwards.
lecris added this to the Board project 2026-04-07 10:54:18 +00:00
Author

I also filed https://github.com/rpminspect/rpminspect/issues/1565 with the rpminspect project.

I also filed https://github.com/rpminspect/rpminspect/issues/1565 with the rpminspect project.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
ci/tickets#551
No description provided.