Handle subordinates OpenStack upgrades better
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron Open vSwitch Charm |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Principal charms (well at least nova-compute) currently don't appear to have a way to tell a subordinate charm to do an openstack upgrade. Subordinate charms don't have openstack-origin config options to trigger an upgrade (which makes sense). So it seems the principal charm would need to trigger the subordinate to upgrade.
For nova-compute, here's how we currently handle subordinate package dependencies. We handle them in the nova-compute charm, which is awkward and not obvious. This is particularly an issue with the transition from queens->rocky where we switched from py2 to py3. But this code could still be error prone in future releases. See commit 32ef5b4c and 280c0d7d. I'd like to see if we can figure out a better way for principals to tell subordinates they need to upgrade and allow them to upgrade their own packages.
def determine_
...
if cmp_release >= 'rocky':
packages = [p for p in packages if not p.startswith(
if filter_
if filter_
if filter_
if virt_type == 'lxd':
return packages
Changed in charm-neutron-openvswitch: | |
status: | New → Triaged |
Changed in charm-neutron-openvswitch: | |
importance: | Undecided → Wishlist |
tags: | added: sts |
This is particularly problematic when doing Q -> R and therefore py2 -> py3