openstack-upgrade action upgrades all packages on a machine co-hosting principal charms
Bug #1862640 reported by
Diko Parvanov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Swift Storage Charm |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
In an environment, which has swift and ceph-osd co-hosted in machines where nova-compute runs, running the openstack-upgrade action on the swift charms did upgrade the nova packages to the next release.
This was tested in Ocata->Pike and Pike->Queens upgrades. Possibly this bug affects more than one charm.
The described actions in https:/
| tags: | added: openstack-upgrade |
| Changed in charm-swift-storage: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
Revision history for this message
| Alex Kavanagh (ajkavanagh) wrote | #1 |
| Changed in charm-swift-storage: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
This isn't a bug, but perhaps a misunderstanding about hyper-convergence and co-locating services.
The OpenStack api and service packages are PER host, not per unit. Thus if two charms are co-located on a host and they rely on common packages (or even if packages are just "apt upgrade"d) then the packages WILL be updated.
Marking as invalid as this is how the packaging distribution for OpenStack works. To obtain isolation, LXD or other separated hypervisor units should be used for units that don't need kernel packages, with the bare metal being reserved for ceph-osd and nova-compute nodes.