Comment 15 for bug 1605653

The assess_recovery script is updated. It verifies that the hosted model is operational when restore reports it is successful. This bug is still observed. As the error is happening within a single juju command (juju restore-backup) there is nothing the test can change to mitigate that restore on xenial with mongo 3.x fails, unlike restore of trusty with mongio 2.4. The test passes when we use an older juju 2.

Manual tests of a restore of xenial have been observed to report a pass, but that leads to the next bug, juju thinks it is upgrading, which is impossible. If juju were to think it was upgrading during a restore, EOF my might be a symptom.

See bug 1606265 (juju thinks it is upgrade, but cannot possibly be upgrading) and bug 1625258 (juju is not permitted to auto upgrade, but it thinks it is).