single unit not upgrading packages after changing openstack-origin
Bug #2039604 reported by
Gabriel Cocenza
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ceph RADOS Gateway Charm |
New
|
Undecided
|
Unassigned | ||
| OpenStack AODH Charm |
New
|
Undecided
|
Unassigned | ||
| OpenStack Barbican Charm |
New
|
Undecided
|
Unassigned | ||
| OpenStack Designate Charm |
New
|
Undecided
|
Unassigned | ||
| OpenStack Octavia Charm |
New
|
Undecided
|
Unassigned | ||
| OpenStack Placement Charm |
New
|
Undecided
|
Unassigned | ||
Bug Description
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-
The unit that didn't upgrade is active idle for some hours and the packages version didn't change:
https:/
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
Revision history for this message
| Gabriel Cocenza (gabrielcocenza) wrote | #1 |
Revision history for this message
| Gabriel Cocenza (gabrielcocenza) wrote | #2 |
| summary: |
- leader unit not upgrading packages after openstack-upgrade + single unit not upgrading packages after changing openstack-origin |
| description: | updated |
Revision history for this message
| Gabriel Cocenza (gabrielcocenza) wrote | #3 |
To post a comment you must log in.
The workaround for ceph-radosgw was manually changing /etc/apt/