Mismatch between Packages.bz2 and InRelease likely due to mirror sync + CF cache

[edkorthof]

Bug Report

Describe the bug

Starting about "2026-04-01 18:29:55Z" through right now ("2026-04-01 19:15:20Z") I've seen errors which appear to be around updating fluentbit. The error shows:

Err:14 https://packages.fluentbit.io/ubuntu/jammy jammy/main amd64 Packages
File has unexpected size (41726 != 42173). Mirror sync in progress? [IP: 10.254.0.22 443]

To Reproduce

• Steps to reproduce the problem:

You can see the file size for the file differs -- 41723 != 42176.

$ curl  https://packages.fluentbit.io/ubuntu/jammy/dists/jammy/InRelease 2> /dev/null | grep main/binary-amd64/Packages.bz2
 47669b0163dc161fbf618dacdeaf8e87    42173 main/binary-amd64/Packages.bz2
 d342928d56dc55537298bd25c6f2ddd8fefcd74d    42173 main/binary-amd64/Packages.bz2
 db028920ca40a84dc0f36032a1634472b24429b69d70500ede7ded4d1a1b7ea3    42173 main/binary-amd64/Packages.bz2
e1624b5ac47405157c367900c477faf56a540683bc4104f8716126a8fee9346eec7d417b11fc5e0317b56e8fbc85185abfd3de247bd8e92621ef4eaac783aa34    42173 main/binary-amd64/Packages.bz2

$   curl -sI -H "Cache-Control: no-cache" -H "Pragma: no-cache" https://packages.fluentbit.io/ubuntu/jammy/dists/jammy/main/binary-amd64/Packages.bz2 | grep content-length:
content-length: 41726

Looking at caching and last-modified headers right now:

https://packages.fluentbit.io/ubuntu/jammy/dists/jammy/main/binary-amd64/Packages.bz2:

last-modified: Tue, 31 Mar 2026 03:50:00 GMT
age: 6458
cache-control: max-age=14400

https://packages.fluentbit.io/ubuntu/jammy/dists/jammy/InRelease

last-modified: Wed, 01 Apr 2026 18:24:08 GMT
cf-cache-status: DYNAMIC

It looks like InRelease is fetched dynamically so it shows up immediately, and Packages.bz2 is cached for up to 4 hours.

Expected behavior

When a new version is published, the metadata (InRelease, I assume) should be updated around when the new release is published. I'd suggest updating the caching configuration for this CF distribution, if it's something you control. (If I filed this with the wrong system, please send me to where I should go.)

Your Environment

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.5 LTS"

Additional context

I think this will resolve in another ~2.1 hours, but 4 hours seems a bit long for this kind of mismatch.

[edkorthof]

This is now resolved (less than 4h, but more than an hour); it seems likely to come up again if the file is cached for up to 4h and metadata isn't cached. (Reducing the caching time to ~5-15 minutes on the source would be an improvement if feasible ... or manually clearing the cache as part of deploying a new version.)

[patrick-stephens]

Yeah I think this is something @edsiper may need to sort on the cache side, I had to set up rules to explicitly not cache certain things like metadata from Cloudflare previously and it may have changed with the packages/website updates.