swift charms need support for removing devices
Bug #1448190 reported by
Jacek Nykis
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Swift Proxy Charm |
Confirmed
|
Low
|
Unassigned | ||
OpenStack Swift Storage Charm |
Confirmed
|
Low
|
Unassigned | ||
swift-proxy (Juju Charms Collection) |
Invalid
|
Undecided
|
Unassigned | ||
swift-storage (Juju Charms Collection) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The swift-proxy charm generates ring files using data from the swift-storage relation which provides list of disks on each storage node.
The swift-storage charm will only relation-set list of disks in swift-storage-
This is problematic because it means it's impossible to permanently remove disk from swift (it will be readded next time the swift-storage relation runs) .
It may be possible to change weights or add disks by hand on the storage-proxy unit but I am not entirely sure this changes will be persistent, they should be but I have not read the whole charm to be absolutely sure.
summary: |
- It is not possible to add, remove of change disk weight + It is not possible to remove disks from swift |
Changed in swift-proxy (Juju Charms Collection): | |
milestone: | 16.04 → 16.07 |
Changed in swift-storage (Juju Charms Collection): | |
milestone: | 16.04 → 16.07 |
Changed in swift-proxy (Juju Charms Collection): | |
milestone: | 16.07 → 16.10 |
Changed in swift-storage (Juju Charms Collection): | |
milestone: | 16.07 → 16.10 |
Changed in swift-proxy (Juju Charms Collection): | |
status: | New → Invalid |
Changed in swift-storage (Juju Charms Collection): | |
status: | New → Invalid |
Changed in swift-proxy (Juju Charms Collection): | |
milestone: | 16.10 → none |
Changed in swift-storage (Juju Charms Collection): | |
milestone: | 16.10 → none |
Changed in charm-swift-proxy: | |
milestone: | none → 17.11 |
Changed in charm-swift-storage: | |
milestone: | none → 17.11 |
Changed in charm-swift-proxy: | |
status: | New → Confirmed |
Changed in charm-swift-storage: | |
status: | New → Confirmed |
Changed in charm-swift-proxy: | |
importance: | Undecided → Low |
Changed in charm-swift-storage: | |
importance: | Undecided → Low |
Changed in charm-swift-proxy: | |
milestone: | 17.11 → 18.02 |
Changed in charm-swift-storage: | |
milestone: | 17.11 → 18.02 |
Changed in charm-swift-proxy: | |
milestone: | 18.02 → 18.05 |
Changed in charm-swift-storage: | |
milestone: | 18.02 → 18.05 |
Changed in charm-swift-proxy: | |
milestone: | 18.05 → 18.08 |
Changed in charm-swift-storage: | |
milestone: | 18.05 → 18.08 |
Changed in charm-swift-proxy: | |
milestone: | 18.08 → 18.11 |
Changed in charm-swift-storage: | |
milestone: | 18.08 → 18.11 |
Changed in charm-swift-proxy: | |
milestone: | 18.11 → 19.04 |
Changed in charm-swift-storage: | |
milestone: | 18.11 → 19.04 |
Changed in charm-swift-proxy: | |
milestone: | 19.04 → 19.07 |
Changed in charm-swift-storage: | |
milestone: | 19.04 → 19.07 |
Changed in charm-swift-proxy: | |
milestone: | 19.07 → 19.10 |
Changed in charm-swift-storage: | |
milestone: | 19.07 → 19.10 |
Changed in charm-swift-proxy: | |
milestone: | 19.10 → 20.01 |
Changed in charm-swift-storage: | |
milestone: | 19.10 → 20.01 |
Changed in charm-swift-storage: | |
milestone: | 20.01 → 20.05 |
Changed in charm-swift-proxy: | |
milestone: | 20.01 → 20.05 |
Changed in charm-swift-storage: | |
milestone: | 20.05 → 20.08 |
Changed in charm-swift-proxy: | |
milestone: | 20.05 → 20.08 |
Changed in charm-swift-proxy: | |
milestone: | 20.08 → none |
Changed in charm-swift-storage: | |
milestone: | 20.08 → none |
To post a comment you must log in.
I hit similar issue to this yesterday when removing a node with a single disk from a zone with juju remove-unit the rings were not updated to reflect the removed node/disk.
While the rings were in this inconsistent state it was possible to add-unit and the additional node/disk was added to the ring files and joined the cluster successfully.
However once I manually removed the previously removed node/disk from the rings subsequent add-unit operations caused a hook error on the swift-proxy instance and a traceback in that unit's juju logs.
So it appears that manually mixing manual maintenance operations with juju managed service causes issues, but also currently we support scale-out but not scale-in.