21855c3130
We are propagating the wrong context (mostly from the Cluster top-level methods). This makes that request cancellations (and cancellations of the associated contexts) are not propagated to many methods, and can result in deadlocks when an operation that is holding a lock is not aborted. This affects for example the operation tracker. Getting all operations from the tracker relies on someone reading from the out channel, or on the context being cancelled. When a request is aborted in the middle of the response, and the context is not cancelled, everything that wants to list operations would become deadlocked, including operations that need write locks like TrackNewOperation. This fixes it. |
||
|---|---|---|
| .. | ||
| operation_test.go | ||
| operation.go | ||
| operationtracker_test.go | ||
| operationtracker.go | ||
| operationtype_string.go | ||
| phase_string.go | ||