I feel like there’s an issue with the CI/CD process that creates the RPM packages for telegraf (it may well affect other products, but this is the only one we use).
We use a private caching mirror in front of https://repos.influxdata.com
This works fine a lot of the time, but we get frequent problems with “Package does not match intended download” errors when trying to deploy telegraf from our mirror.
The problem seems to be that the package is being recreated in place on the upstream, which changes the signature. This results in a corresponding update of the metadata. The new metadata is cached by our mirror, but because it is quite reasonably expecting the upstream package for a particular version to remain unchanged, it does not re-cache the package without manual intervention.
This problem crops with annoying regularity and only with this particular repo (despite the fact that we are caching a large quantity of upstream content from many varied repos).
Not sure where to raise a bug about this, because it doesn’t immediately feel like a telegraf issue, rather the supporting CI/CD process around it.