From 99c3c2646023945d95df954078a334a80b413077 Mon Sep 17 00:00:00 2001
From: Enrico Golfieri <enrico.golfieri@mongodb.com>
Date: Thu, 24 Nov 2022 16:07:27 +0000
Subject: SERVER-71277 Not assume that '_collInfo' is initialized when we hit
 an error at '_runImpl' from 'collmod_coordinator.cpp'

---
 src/mongo/db/s/collmod_coordinator.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/mongo/db/s/collmod_coordinator.cpp b/src/mongo/db/s/collmod_coordinator.cpp
index 277e2dc3f02..f3dba24ecb0 100644
--- a/src/mongo/db/s/collmod_coordinator.cpp
+++ b/src/mongo/db/s/collmod_coordinator.cpp
@@ -382,7 +382,7 @@ ExecutorFuture<void> CollModCoordinator::_runImpl(
                             "error"_attr = redact(status));
                 // If we have the collection UUID set, this error happened in a sharded collection,
                 // we should restore the migrations.
-                if (_doc.getCollUUID()) {
+                if (_doc.getCollUUID() && _collInfo) {
                     auto opCtxHolder = cc().makeOperationContext();
                     auto* opCtx = opCtxHolder.get();
                     getForwardableOpMetadata().setOn(opCtx);
-- 
cgit v1.2.1