-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
ALL
-
Storage Execution 2025-12-8, Storage Execution 2025-12-22
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
- Non-assignee request [Answer Required]: What is the reason for requesting this backport?
-
- To fix issues with multiversion tests, this is necessary to resolve BF-40620
- Could this introduce any (intentional or unintentional) breaking changes? Please explain.
-
- No, this is only a test change.
- Could this change unintentionally cause tests to fail or introduce risk to internal tools and test infrastructure?
-
- Highly unlikely, this resolves a test that is already failing on multiversion tests.
- What is the risk and potential customer impact of backporting this?
-
- Minimal risk, test change only.
- If the risk is not low, then what would a smaller and simpler solution or mitigation to this issue be? (assuming leaving the issue unfixed is also not low impact). For example, see the comments in ** BACKPORT-5428 and its[ ** CR|https://mongodbcr.appspot.com/673840020].
-
- What is the risk and potential customer impact of not backporting this?
-
- None, this is only a test change.
- Why is it worth the risk to backport?
-
- There is nearly no risk and this resolves currently failing tests.