From 8d420b824a8fc506988ee42c2322372d8b4a7e04 Mon Sep 17 00:00:00 2001 From: Ricardo Osorio Date: Wed, 1 Feb 2023 10:09:49 +0000 Subject: [PATCH] Fix an issue where we try to access a nil pointer Getting the sync progress of a deployment can sometimes fail and return back a nil result. This happens rarely but when it does we don't want to panic --- cmd/update/volume_move.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cmd/update/volume_move.go b/cmd/update/volume_move.go index 8790a082..914ae209 100644 --- a/cmd/update/volume_move.go +++ b/cmd/update/volume_move.go @@ -252,7 +252,7 @@ func (c *volumeMoveCommand) waitForSyncedReplicaOnNode(ctx context.Context, nsID if rep.Node.String() == c.toNode { if rep.Promotable { return nil - } else { + } else if rep.SyncProgress != nil { c.display.ReplicaSyncProgress(ctx, c.writer, *rep.SyncProgress) } }