SERVER-53950: fix ASAN errors when migration recipient is stuck on step down

1 files changed, 4 insertions, 2 deletions

diff --git a/src/mongo/db/commands/tenant_migration_donor_cmds.cpp b/src/mongo/db/commands/tenant_migration_donor_cmds.cpp
index 1570f370213..5e239bbe97d 100644
--- a/src/mongo/db/commands/tenant_migration_donor_cmds.cpp
+++ b/src/mongo/db/commands/tenant_migration_donor_cmds.cpp
@@ -98,12 +98,14 @@ public:
             auto durableState = [&] {
                 try {
                     return donor->getDurableState(opCtx);
-                } catch (ExceptionFor<ErrorCodes::ConflictingOperationInProgress>&) {
+                } catch (ExceptionFor<ErrorCodes::ConflictingOperationInProgress>& ex) {
                     // The conflict is discovered while inserting the donor instance's state doc.
                     // This implies that there is no other instance with the same migrationId, but
                     // there is another instance with the same tenantId. Therefore, the instance
                     // above was created by this command, so remove it.
-                    donorService->releaseInstance(stateDocBson["_id"].wrap());
+                    // The status from this exception will be passed to the instance interrupt()
+                    // method.
+                    donorService->releaseInstance(stateDocBson["_id"].wrap(), ex.toStatus());
                     throw;
                 }
             }();