Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Fully Compatible
-
ALL
-
Service Arch 2020-02-24
Description
The current implementation of CancelRemotely and CancelRemotelyTimedOut expects the command being cancelled to have already acquired a connection by the time cancelCommand starts. This is not always true, and when cancelCommand is run before the command has acquired a connection, cancelCommand immediately fulfills the promise with CallbackCancelled, which causes the checks in the these tests to fail. These tests should wait for the command to acquire a connection before calling cancelCommand (e.g. using a failpoint).