Comment 11 for bug 1899680

> However, this does not take effect. As shown in the log I posted these charms will still attempt to install python-apt over python3-apt, which does not make any sense as I am running Victoria, on Groovy.

Yes, but they didn't get installed as the series-upgrade doesn't trigger the charm to run particular package upgrades. i.e. series upgrade is designed around the idea that the OpenStack version doesn't change, just the underlying OS. i.e. the upgrade goes from xenial-queens to bionic-queens (distro), and from bionic-ussuri -> focal-ussuri (distro). In order to series upgrade to groovy, it would be necessary to OpenStack upgrade to focal-victoria and then do a series upgrade to groovy-victoria. Upgrading from focal-ussuri to groovy-victoria directly is just something the charms are not designed to handle. But this shouldn't try to install python-apt so something strange *is* going on there. It's possible that the charm is mis-detecting what is it running on and doing the wrong thing.

I don't think, on reviewing them, that our upgrades documentation (https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/upgrade-overview.html) is fully clear on what the charms are capable of handling, as we assume (in the team) that everybody will run on LTS versions.