The kill_rooted_or.js test is running concurrent dropCollection and index modification commands. This test is already handling certain errors that can be bubbled up to the user when a command fails due to the collection being concurrently dropped.

With the introduction of SERVER-80372, though, the probability of hitting a staleConfig error due to concurrent dropCollection has increased. This is because there is a longer period of time between the implicit creation of the collection and the creation of the index, making it more likely that a collection drop can start and grab the critical section while a createIndex is running.

This ticket is to add StaleConfig to the list of accepted errors due to the collection being dropped.