overlay afterburn: update to 5.10.0

[dongsupark]

Update coreos-base/afterburn to 5.10.0.

We need to skip 5.9.0, which has regressions around Azure IMDS. See also #3234.

Changelog of 5.9.0:

• Major changes:
  • Add support for Oracle Cloud Infrastructure
  • dracut: don't include module by default
• Minor changes:
  • Add TMT test structure and basic smoke test

Changelog of 5.10.0:

• Major changes:
  • Add support for UpCloud
• Minor changes:
  • Azure: fetch SSH keys from IMDS instead of deprecated certificates endpoint.
  • Azure: fix parsing of SharedConfig XML document with current serde-xml-rs

Testing done

CI: http://jenkins.infra.kinvolk.io:8080/job/container/job/packages_all_arches/6771/cldsv/ passed for all cloud providers

• Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)
• Inspected CI output for image differences: /boot and /usr size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.

[dongsupark]

With this PR, the image size increases by ~207 KB show like below:

 ./usr/bin/coreos-metadata by 212472 bytes (207 kbytes) from 6797920 bytes (6638 kbytes, 6 mbytes) to 7010392 bytes (6846 kbytes, 6 mbytes)

That is a little bump, which makes me concerned.

From a quick look at Afterburn's changelog, support for Oracle Cloud and UpCloud could be the reason. I did not have a deeper look.

EDIT: no, from the second look, I misread the log. Only 207 KB increase.

[github-actions]

Build action triggered: https://github.com/flatcar/scripts/actions/runs/18401999830

[dongsupark]

On the other hand, the Azure regression in 5.9.0 was finally fixed with the new version 5.10.0. Confirmed by Jenkins CI for all cloud providers.

[dongsupark]

Ok, I got it. The image size change was probably caused by the PR #3241, which created a new file /usr/lib/flatcar/bootengine.img (48 MB).
So that affects already the last nightly. Has nothing to do with this PR.

[tormath1]

Thanks!