new images

[Luap99]

Mainly to pull in a new pasta version to fix
containers/podman#23517

[github-actions]

Cirrus CI build successful. Found built image names and IDs:

Stage	Image Name	IMAGE_SUFFIX
base	debian	do-not-use
base	fedora	do-not-use
base	fedora-aws	do-not-use
base	fedora-aws-arm64	do-not-use
base	image-builder	do-not-use
base	prior-fedora	do-not-use
cache	build-push	c20240808t132550z-f40f39d13
cache	debian	c20240808t132550z-f40f39d13
cache	fedora	c20240808t132550z-f40f39d13
cache	fedora-aws	c20240808t132550z-f40f39d13
cache	fedora-netavark	c20240808t132550z-f40f39d13
cache	fedora-netavark-aws-arm64	c20240808t132550z-f40f39d13
cache	fedora-podman-aws-arm64	c20240808t132550z-f40f39d13
cache	fedora-podman-py	c20240808t132550z-f40f39d13
cache	prior-fedora	c20240808t132550z-f40f39d13
cache	rawhide	c20240808t132550z-f40f39d13
cache	win-server-wsl	c20240808t132550z-f40f39d13

[edsantiago]

• 20240808t132550z-f40f39d13
• 20240805t173227z-f40f39d13 ⇑ (built in add bpftrace for CI debugging #371)

	debian	prior-fedora	fedora	fedora-aws	rawhide
kernel	6.10.3-1	6.9.12-100	6.8.5-301	6.9.12-200	6.8.5-301
	6.9.12-1 ⇑		6.9.12-200 ⇑
grub2-common	2.12-5	2.06-121	2.06-123	2.06-123	2.12-3
					2.06-124 ⇑
aardvark-dns	1.6.0-3	1.11.0-1	1.12.1-1	1.12.1-1	1.12.1-1
				1.11.0-3 ⇑
netavark	1.6.0-2.1	1.11.0-1	1.12.1-1	1.12.1-1	1.12.1-1
				1.11.0-3 ⇑	1.11.0-3 ⇑
gvisor-tap-vsock	?	0.7.3-1	?	0.7.4-1	?
				0.7.3-2 ⇑
passt	2024-08-06	2024-06-24	2024-08-06	2024-07-26	2024-08-06
	2024-07-26 ⇑		2024-07-26 ⇑	2024-06-24 ⇑	2024-07-26 ⇑
systemd	256.4-2	254.16-1	255.10-3	255.10-3	256.4-1
			255.10-1 ⇑	255.10-1 ⇑

[Luap99]

passt 2024-07-26 in fedora-aws is not good. Are we not using the same repos there or do the aws images have some older mirrors?

[edsantiago]

aws always lags by a few days/weeks. @cevich might understand why. Pragmatically speaking, look through the history for "timebomb dnf install pasta"

[edsantiago]

e.g., cd783f0 (that's a remove, not an add, but you get the idea)

[Luap99]

Yeah I figure they use their own aws specific mirrors then, I have no rush here so I can wait until next week.

[cevich]

Yeah I figure they use their own aws specific mirrors

That sounds plausible to me, in GCP we're pulling in the generic cloud image and molding it into a GCP-compatible image via a nested-virt builder. For AWS, we search AWS-specific images build and published by the fedora project so they easily could have AWS-specific content, like repo-mirror configuration. It should be easy to observe this using a hack/get_ci_vm.sh somewhere, against an EC2-based task.