get_container returns None instead of the expected tuple
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-swiftclient |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Hi,
During https:/
The following code:
try:
except swclient.
raise this exception because None is returned instead of the headers and files.
[Thu Feb 22 12:35:23.833389 2018] [:error] [pid 19] [remote 192.168.24.3:188] yield future.result()
[Thu Feb 22 12:35:23.833406 2018] [:error] [pid 19] [remote 192.168.24.3:188] File "/usr/lib/
[Thu Feb 22 12:35:23.833438 2018] [:error] [pid 19] [remote 192.168.24.3:188] return self.__get_result()
[Thu Feb 22 12:35:23.833450 2018] [:error] [pid 19] [remote 192.168.24.3:188] File "/usr/lib/
[Thu Feb 22 12:35:23.833820 2018] [:error] [pid 19] [remote 192.168.24.3:188] result = self.fn(*self.args, **self.kwargs)
[Thu Feb 22 12:35:23.833835 2018] [:error] [pid 19] [remote 192.168.24.3:188] File "/usr/lib/
[Thu Feb 22 12:35:23.833862 2018] [:error] [pid 19] [remote 192.168.24.3:188] return list(executor.
[Thu Feb 22 12:35:23.833873 2018] [:error] [pid 19] [remote 192.168.24.3:188] File "/usr/lib/
[Thu Feb 22 12:35:23.833893 2018] [:error] [pid 19] [remote 192.168.24.3:188] metric, aggregation.method, aggregation.
[Thu Feb 22 12:35:23.833903 2018] [:error] [pid 19] [remote 192.168.24.3:188] File "/usr/lib/
[Thu Feb 22 12:35:23.833921 2018] [:error] [pid 19] [remote 192.168.24.3:188] metric, aggregation, granularity, version)),
[Thu Feb 22 12:35:23.833931 2018] [:error] [pid 19] [remote 192.168.24.3:188] File "/usr/lib/
[Thu Feb 22 12:35:23.834481 2018] [:error] [pid 19] [remote 192.168.24.3:188] container, full_listing=True)
[Thu Feb 22 12:35:23.834555 2018] [:error] [pid 19] [remote 192.168.24.3:188] TypeError: 'NoneType' object is not iterable
I checked the python-swiftclient code; it must be an obscure circumstance where that happens. By default exceptions are either raised or a tuple is returned, and I wasn't able to spot a situation where this won't happen.
Can't verify this because we're lacking logs from Swift at that timepoint - so marking as incomplete for now.