Comment 8 for bug 1881087

A couple of thoughts about this bug:

- While both scenario 10, the ovn provider and non-ovn provider jobs are only similar in the deployment code - the running of tempest is quite different. I feel if we are going to track scenario 10 timeouts, it makes sense to track timeouts due to scenario 10 deployment and tempest separately.

- This was filed in 2020. It seems likely that the root cause for original issue has passed. Is the idea here to keep a log-like bug for recurring timeout issues that might be unrelated?