Attempts to replace consensus find consensus in cache, and do nothing.

Have a look at these logs:

2022-01-07T17:48:34.088380Z  INFO tor_dirmgr::state: The current consensus is fresh until 2022-01-07 16:00:00.0 +00:00:00, and valid until 2022-01-07 18:00:00.0 +00:00:00. I've picked 2022-01-07 17:45:22.815194352 +00:00:00 as the earliest time to replace it.
2022-01-07T17:48:34.089864Z  INFO tor_dirmgr: Directory is complete.
2022-01-07T17:48:34.162128Z  INFO tor_dirmgr::state: The current consensus is fresh until 2022-01-07 16:00:00.0 +00:00:00, and valid until 2022-01-07 18:00:00.0 +00:00:00. I've picked 2022-01-07 17:47:00.32194958 +00:00:00 as the earliest time to replace it.
2022-01-07T17:48:34.163459Z  INFO tor_dirmgr: Directory is complete.
2022-01-07T17:48:34.234338Z  INFO tor_dirmgr::state: The current consensus is fresh until 2022-01-07 16:00:00.0 +00:00:00, and valid until 2022-01-07 18:00:00.0 +00:00:00. I've picked 2022-01-07 17:49:49.038417374 +00:00:00 as the earliest time to replace it.
2022-01-07T17:48:34.235715Z  INFO tor_dirmgr: Directory is complete.

It looks like we're deciding to replace a stale-but-still valid consensus, and then finding that same consensus in our cache, and using it.