In #forum-mco, it was reported that the e2e-gcp-op tests are randomly timing out. Additionally, cdoern@redhat.com, observed similar behavior with his PR.

My first instinct is to raise our test timeouts. While this would alleviate the issue in the short-term, it will inevitably come back in the future. Therefore, I propose that if we raise the test timeouts, we should also implement one of the test improvements identified in MCO-160. The approach that I recommend is consolidation of as many of the MachineConfig test cases as possible.

Done When:

• We've identified the cause of the e2e-gcp-op timeouts.
• We've implemented a short-term mitigation such as temporarily raising the test timeouts.
• We've implemented a long-term mitigation such as one of the solutions identified in MCO-160.