-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Testing
-
Labels:None
In the current state of the world, debugging issues that arise related to starting clusters via mongo-orchestration require reproducing the issue on a spawnhost and manually examining the log file. It would be nice if task failures caused by issues spawning clusters automatically displayed the contents of the mongo-orchestration log at the end of the task.