From looking at the test's code, it's possible that this is happening because the test isn't waiting for the migration to be completely done before attempting to run "juju run" on the deployed mongodb unit. veebers is taking a look.
From looking at the test's code, it's possible that this is happening because the test isn't waiting for the migration to be completely done before attempting to run "juju run" on the deployed mongodb unit. veebers is taking a look.