The server status command will get migration information as part of the sharding section if there is an ongoing migration. Getting this information requires the CSR which, on 8.0, requires the collection lock. The ActiveMigrationsRegistry is using AutoGetCollection to acquire the db and coll lock, which triggers the direct shard connection checks.

This means that the server status command will be blocked by the direct shard connection checks if there is an ongoing migration when the command is run.

This is only on 8.0 because SERVER-99928 removed the db/coll locks requirement for the CSR.

Two potential solutions would be to backport SERVER-99928 to 8.0 or to replace the AutoGetCollection with a dblock + colllock acquisition in the active migrations registry.