swift-manage-shard-ranges inject shards into the container that is in process of sharding

[alex]

Here are the steps of botched sharding attempt. The doc had a command listed with redirection ">" symbol in it, which caused different command output from one listed in the doc. Than i did re issued replace command, which correctly told that sharding is underway and no need to do anything. However, when I pressed 'q', six more shards were inserted and sharding process stuck with audit_root failure.

# swift-manage-shard-ranges /srv/node/sdb/containers/739/e9d/b8d3bf06b4b58efd12ece64175b9de9d/b8d3bf06b4b58efd12ece64175b9de9d.db find 1000 > test_ranges
Loaded db broker for AUTH_0deacb4b247b45dd8973e1e56e603ef3/sharding_test.
Found 6 ranges in 0.00700998s (total object count 5832)

# swift-manage-shard-ranges /srv/node/sdb/containers/739/e9d/b8d3bf06b4b58efd12ece64175b9de9d/b8d3bf06b4b58efd12ece64175b9de9d.db find_and_replace 1000 --enable > --force
Loaded db broker for AUTH_0deacb4b247b45dd8973e1e56e603ef3/sharding_test.

# swift-manage-shard-ranges /srv/node/sdb/containers/739/e9d/b8d3bf06b4b58efd12ece64175b9de9d/b8d3bf06b4b58efd12ece64175b9de9d.db replace test_ranges
Loaded db broker for AUTH_0deacb4b247b45dd8973e1e56e603ef3/sharding_test.
This will delete existing 6 shard ranges.
WARNING: Be very cautious about deleting existing shard ranges. Deleting all ranges in this db does not guarantee deletion of all ranges on all replicas of the db.
  - this db is in state sharding
  - 6 existing shard ranges have started sharding
Do you want to show the existing ranges [s], delete the existing ranges [yes] or quit without deleting [q]? q
Injected 6 shard ranges.
Run container-replicator to replicate them to other nodes.
Use the enable sub-command to enable sharding.