Upload hangs if --segment-size 0 is passed

[Inessa Vasilevskaya]

swift --os-username services:glance --os-password SOMEPASS upload new-container .viminfo --segment-size 0

The upload starts but doesn't seem to finish (at least 10 minutes was not enough for a 7kb file).

I believe the possibility to start upload with zero segment size should be forbidden at api level and filtered in client as well.

[Samuel Merritt (torgomatic)]

Zero-byte objects are allowed, and there's nothing special about a "segment" except that it's an object referenced by a manifest. No API change is possible here.

Disallowing a segment size of 0 in the client sounds like a good idea, though.

[Alistair Coles (alistair-coles)]

I did not manage to reproduce with

$ swift --version
swift 2.4.0.post6

Can you confirm version ofpython-swiftclient and if there is any output during upload?

[Inessa Vasilevskaya (ivasilevskaya)]

python-swiftclient==2.3.1

As for the output, I receive output in the form [filename segment #segment] which keeps updating but then freezes at some point (i've tested it on kilo devstack on devstack/stackrc default file and the last segment before "freeze" was 2108).

swift upload new-container stackrc --segment-size 0

stackrc segment 2074
stackrc segment 2071
stackrc segment 2076
stackrc segment 2079
stackrc segment 2077
stackrc segment 2075
stackrc segment 2080
stackrc segment 2073
stackrc segment 2078
stackrc segment 2083
stackrc segment 2084
stackrc segment 2085
stackrc segment 2081
stackrc segment 2082
stackrc segment 2086
stackrc segment 2087
stackrc segment 2089
stackrc segment 2088
stackrc segment 2090
stackrc segment 2092
stackrc segment 2091
stackrc segment 2093
stackrc segment 2095
stackrc segment 2096
stackrc segment 2094
stackrc segment 2097
stackrc segment 2098
stackrc segment 2100
stackrc segment 2099
stackrc segment 2101
stackrc segment 2106
stackrc segment 2104
stackrc segment 2105
stackrc segment 2102
stackrc segment 2103
stackrc segment 2107
stackrc segment 2108

[Tim Burke (1-tim-z)]

Looks like this was addressed in commit e596489, with the fix released in 2.5.0.