transactions_reject_writes_for_moved_chunks.js verifies that a transaction that targets a chunk that has been moved since a transaction began will fail for sharded collections with range and hashed keys. In some test cases, the targeted chunk is moved twice and a refresh if forced on the chunk's recipient to avoid a StaleConfig error when the transaction targets it. The refresh is currently always for the range based collection namespace (ns is defined here), so the shard is not guaranteed to be fresh in the hashed case.

Instead, the hashed collection namespace should be refreshed in the hashed test cases.