What problem are you facing?

The driver is marking servers Unknown that have a different setName from the one provided in the connection string. According to the specification we should be removing servers altogether.

Fields in the SDAM unit tests are set to null and the runner attempts to assert that the nullish keys do not exist on the serverDescription. The assertion was written incorrectly so it doesn't prevent these "omittedFields" from existing. We should set these fields to null, and the runner can look for null equality on these fields.

Steps to reproduce?

Run this test: test/spec/server-discovery-and-monitoring/rs/new_primary_wrong_set_name.json

Attempt to assert that the number of servers present in the test file are equal to the number of servers that the Topology has saved. (search code for this ticket number)