Merge lp:~james-page/charms/trusty/swift-storage/lp1318083-next into lp:~openstack-charmers-archive/charms/trusty/swift-storage/next
Proposed by
James Page
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 40 | ||||
Proposed branch: | lp:~james-page/charms/trusty/swift-storage/lp1318083-next | ||||
Merge into: | lp:~openstack-charmers-archive/charms/trusty/swift-storage/next | ||||
Diff against target: |
11 lines (+2/-1) 1 file modified
hooks/swift_storage_utils.py (+2/-1) |
||||
To merge this branch: | bzr merge lp:~james-page/charms/trusty/swift-storage/lp1318083-next | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Liam Young (community) | Approve | ||
Review via email: mp+230263@code.launchpad.net |
To post a comment you must log in.
This points to a wider problem that swift ring configuration is currently eventually consistent; we should really look to use something better for ring management going forward which does transactional, incremental updates to ring files (swift-ringmaster might be an option).