9c8c7e8a55
As described in bug #1558754 a rebalance after removing a device fails if min_part_seconds_left > 0, despite the note that a rebalance should remove partitions from removed devices on the next run. This patch skips the early exit, and lets the builder itself handling the rebalance. Partitions that shouldn't move now are still not moved (except for removed devices), and there is still a warning if no partition has been moved due to the fact that min_part_hours did not yet pass. A small test has been added to ensure rebalancing after removing a device works without using the --force option (tests fails on current master). Another test ensures that a rebalance after a recent change (for example increasing a device's weight) does not move partitions and still reports the former warning message. Closes-Bug: 1558754 Change-Id: I083022d066338cbe6234bab491c7a8e8e0a7b517 |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| form_signature.py | ||
| info.py | ||
| recon.py | ||
| ring_builder_analyzer.py | ||
| ringbuilder.py | ||