| 2023-10-18 13:11:00 |
Gabriel Cocenza |
description |
I'm in a cloud upgrading from victoria to wallaby and I noticed that the leader unit didn't get upgrade after changing the openstack-origin to cloud:focal-wallaby (action-managed-upgrade was set to False).
The leader unit is active idle for some hours and the packages didn't get upgrade:
https://pastebin.canonical.com/p/jf293y3dYV/
If I run `juju run-action barbican/2 openstack-upgrade` then after the unit is stable, the package is upgraded.
The same pattern happened on charm-aodh, so maybe it's a problem with reactive openstack-charms |
I'm in a cloud upgrading from victoria to wallaby and I noticed that one unit didn't get upgrade after changing the openstack-origin to cloud:focal-wallaby (action-managed-upgrade was set to False).
The unit that didn't upgrade is active idle for some hours and the packages version didn't change:
https://pastebin.canonical.com/p/jf293y3dYV/
If I run `juju run-action barbican/2 openstack-upgrade` then after the unit is stable, the package is upgraded.
The same pattern happened on charm-aodh, so maybe it's a problem with reactive openstack-charms |
|
