Comment 6 for bug 2004618

I'm told that jammy's behavior appears to match the behavior of focal + the updated ovmf - i.e., it will default to the ms.fd variant. Which makes sense - jammy has always advertised only the _4M variants in its descriptors. And same as focal, jammy's virtinst doesn't match the 4M images in its "_uefi_arch_patterns" regex map. In fact, this is still true in virtinst upstream.

So this puts us in a weird situation. AIUI:

focal/before the ovmf SRU: Behaves as upstream intended
focal/after the ovmf SRU: Broken per upstream's intention
>= jammy: Broken per upstream's intention
upstream: Broken per upstream's intention

So we could submit a fix upstream to add 4M images to the regex map and backport that everywhere. That would restore upstream's intended behavior and fix this focal regression. But correcting that in jammy and kinetic would change the behavior of those stable releases.

We could fix focal and upstream (and therefore future Ubuntu releases) and skip jammy and kinetic. But doing so would make jammy and kinetic's behavior different than the releases before and after them.