Although this might look like a clone of #2133, it isn't.
The symptoms are the same but the reason is different.
In this case we're facing an issue between trustd and csaf-walker.
It seems for a network failure reason or equivalent, a file which exists in the URL tree is not fetched.
For example rhsa-2023_5095.json.sha256 is not fetched and csaf-walker automatically tries to fetch the sibling sha512 file.
Since, the file (i.e rhsa-2023_5095.json.sha512) doesn't exist, the walker returns an error to trustd importer which fails.
This happens at random times, more likely because of networks latency, but in such way that the CSAF importer never finishes getting 100% of the files (and assuming #2133 has been addressed).
Although this might look like a clone of #2133, it isn't.
The symptoms are the same but the reason is different.
In this case we're facing an issue between
trustdandcsaf-walker.It seems for a network failure reason or equivalent, a file which exists in the URL tree is not fetched.
For example
rhsa-2023_5095.json.sha256is not fetched andcsaf-walkerautomatically tries to fetch the sibling sha512 file.Since, the file (i.e
rhsa-2023_5095.json.sha512) doesn't exist, the walker returns an error to trustd importer which fails.This happens at random times, more likely because of networks latency, but in such way that the CSAF importer never finishes getting 100% of the files (and assuming #2133 has been addressed).