Comment 17 for bug 2020474

You are correct that this is the same issue. However, the reason you are seeing this in Lunar is that
you are running with -proposed enabled, which is where packages are staged before being released to -release, or -updates for stable release updates. So, this means that you installed 1:9.0p1-1ubuntu8.1 from lunar-proposed, which contains the bug that causes the problem on upgrade. However, thanks to this bug report from you, we have uploaded 1:9.0p1-1ubuntu8.2 to lunar-proposed to fix the underlying issue *before* openssh is released to lunar-updates. This means that users who upgrade to 1:9.0p1-1ubuntu8.2 from 1:9.0p1-1ubuntu8 (i.e. they never installed 1:9.0p1-1ubuntu8.1) will not see this bug. Since a buggy version of openssh was not yet released to lunar-updates, we did not apply the extra patches that we did in mantic to work around the bug on upgrade (for mantic, a buggy version was released to mantic-release, so the situation was a bit different).

So, anyone running -proposed on kinetic or lunar will hit this bug once, but those users should be able to reboot, run dpkg --configure -a, and be sorted.