Summary

Now that server v6.1.0-rc0 is available, the "journal" configuration block appears to no longer be supported (see SERVER-55208). Additionally, the "journal" block in the server configurations specifies the default behavior for all supported server versions, so including it is redundant. Remove the "journal" configuration block from all mongo-orchestration server configurations.

Motivation

Who is the affected end user?

DBX devs.

How does this affect the end user?

Driver CI builds that use the "latest" server version may fail consistently for reasons unrelated to the driver.

How likely is it that this problem or use case will occur?

It will fail consistently for all CI tasks using the "latest" server version on platforms where the "latest" server version is v6.1.0-rc0 or greater.

If the problem does occur, what are the consequences and how severe are they?

Failing CI builds cause unnecessary noise and may hide real issues.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

No.