Comment 6 for bug 1968873

Thank you for summarizing John.

To be clear, I don't think a non-interactive upgrade between releases is a particularly important user story in itself. I'm more concerned that the current issue in the upgrade from Focal to Jammy reveals that a latent issue exists, and this kind of thing can also impact automated upgrades _within_ a single release, and it's the latter which is a common thing for deployment automation to do. The fix is, as you say, unconnected with Jammy's release schedule. It also doesn't help already-deployed instances.