Adjust integration tests timeout to tolerate >10 min wait for custom Operatorhub.io catalog source readiness

[fabiobrz]

OperatorSubscriptionTestCase fails at deploying the WildFly Operator as it seems that the custom CatalogSource which is created by Intersmash needs more than 10 minutes (default timeout) to get ready sometimes.

The fix would be to add a higher timeout via xtf.waiting.timeout to the job which executing the maven build, but this must be verified because WildflyOpenShiftOperatorProvisionerTest should fail as well, instead it's passing.

---

• Environment: testsuite/integration-tests module, CI
• Steps to reproduce: mvn clean test -pl testsuite/integration-tests -Pts.openshift test -pl testsuite/integration-tests -Dtest=OperatorSubscriptionTestCase

[dosubot]

Hi, @fabiobrz. I'm Dosu, and I'm helping the intersmash team manage their backlog. I'm marking this issue as stale.

Issue Summary:

• The OperatorSubscriptionTestCase fails due to the custom CatalogSource exceeding the 10-minute readiness timeout.
• Suggested fix involves extending the timeout using xtf.waiting.timeout.
• Further investigation is needed as WildflyOpenShiftOperatorProvisionerTest does not encounter the same issue, suggesting different test conditions or configurations.

Next Steps:

• Please confirm if this issue is still relevant to the latest version of the intersmash repository. If so, you can keep the discussion open by commenting on the issue.
• If there is no further activity, the issue will be automatically closed in 30 days.

Thank you for your understanding and contribution!