When OCP is upgraded, wait for the catalog source to become ready on UI

[am-agrawa]

test- tests/ui/test_validation_ui.py::TestUserInterfaceValidation::test_dashboard_validation_ui

ocs-ci results for OCS4-7-Downstream-OCP4-8-AWS-IPI-3AZ-RHCOS-3M-3W-tier1-or-tier_after_upgrade-post-upgrade (BUILD ID: 4.7.14-268.ci RUN ID: 1667455542)

The test failed with

Message: AssertionError: ['Healthy string not found on subscription_tab']
Type: None

This is because we are upgrading OCP, and we should wait for the catalog source to become healthy on UI before failing the test.
A direct assertion will immediately fail the test just like in this case.

[ebenahar]

@am-agrawa @shyRozen @OdedViner would any of you like to take this one?

[am-agrawa]

@am-agrawa @shyRozen @OdedViner would any of you like to take this one?

It's not a high priority fix as it's intermittent in my opinion. And it should be a easy fix. We can take it as per priority.
Also, @OdedViner can send a fix as he had automated this test long back.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs.

[am-agrawa]

Another instance seen in Run ID: 1677857518

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs.