swift-proxy _get_zone breaks when replicas value is the same as the number of swift-storage block-devices
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
swift-proxy (Juju Charms Collection) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
deploying swift-proxy and swift-storage like this:
swift-proxy:
branch: lp:charms/swift-proxy
options:
replicas: 3
swift-hash: fdfef9d4-
use-https: 'no'
swift-storage:
branch: lp:charms/swift-storage
num_units: 3
options:
overwrite: 'true'
zone: 1
Results in successful deployment, but swift-storage services won't start due to missing swift-hash.
swift-hash isn't set/sent because all storage nodes are put into the same zone.
This is a result of a bug in swift-proxy/
The algorithm doesn't account for a single storage node having multiple devices; this confuses the distribution logic.
Related branches
- OpenStack Charmers: Pending requested
-
Diff: 20 lines (+8/-2)1 file modifiedhooks/swift_utils.py (+8/-2)
- Liam Young (community): Approve
-
Diff: 20 lines (+8/-2)1 file modifiedhooks/swift_utils.py (+8/-2)
tags: | added: cloud-installer |
tags: | added: landscape |
Changed in swift-proxy (Juju Charms Collection): | |
status: | Fix Committed → Fix Released |
Applied this fix to linked branch.
This resolves the issue for the included deployment yaml. Could use more testing.