Improve UATs logs

[orfeas-k]

Context

Right now, when UATs fail, they do not provide any useful logs apart from the failed assertion of the notebook

• example 1
• example 2

This results in providing 0 information on what is the reason behind the failure, which is crucial for CI runs, hides intermittent failures and adds a lot of workload in order to debug those.

On top of those, even in cases with access to the cluster, since the UATs go ahead and delete the failed pods after the test's failure, one needs to capture logs before that happens.

What needs to get done

Refactor the way the driver runs the UATs in order to capture and expose logs that are sufficient for debugging

Definition of Done

UATs provide logs

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5959.

This message was autogenerated