Bug 1976939 - Interacting with CatalogSource page.Interacting with CatalogSource page renders details about the redhat-operators catalog source
Summary: Interacting with CatalogSource page.Interacting with CatalogSource page rende...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.9.0
Assignee: David Taylor
QA Contact: Yanping Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-28 15:33 UTC by Zack Zlotnik
Modified: 2021-10-18 17:37 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Interacting with CatalogSource page.Interacting with CatalogSource page renders details about the redhat-operators catalog source
Last Closed: 2021-10-18 17:36:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 9570 0 None open Bug 1976939: Interacting with CatalogSource page 2021-07-21 15:19:53 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:37:10 UTC

Internal Links: 1984102

Description Zack Zlotnik 2021-06-28 15:33:31 UTC
test:
Interacting with CatalogSource page.Interacting with CatalogSource page renders details about the redhat-operators catalog source 

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=Interacting+with+CatalogSource+page%5C.Interacting+with+CatalogSource+page+renders+details+about+the+redhat-operators+catalog+source

Example Jobs:
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.8-console-aws/1407612152746872832
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.8-console-aws/1407794468198813696
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.9-console-aws/1407022801579151360
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.9-console-aws/1407141810098147328
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.9-console-aws/1407679009591922688
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.9-console-aws/1408112640911216640
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.9-console-aws/1408333557599834112

The failure message is consistent across all of the above jobs, which appears to be a timeout of some sort:

  Interacting with CatalogSource page
  Logging in as kubeadmin
      create project
      navigate to Catalog Source page
      navigate to Catalog Source page
    1) renders details about the redhat-operators catalog source
      navigate to Catalog Source page
    ✓ allows modifying registry poll interval (5233ms)
      navigate to Catalog Source page
      delete project
  Logging out
    ✓ lists all the package manifests for redhat-operators under Operators tab (5060ms)


  2 passing (2m)
  1 failing

  1) Interacting with CatalogSource page
       renders details about the redhat-operators catalog source:

      Timed out retrying after 30000ms
      + expected - actual

      -'-'
      +'READY'
      
      at Context.eval (https://console-openshift-console.apps.ci-op-1drz477w-2e947.aws-2.ci.openshift.org/__cypress/tests?p=tests/catalog-source-details.spec.ts:14010:57)

Comment 1 Samuel Padgett 2021-07-02 21:21:19 UTC
This would be fixed indirectly if we move to a Red Hat operator for bug 1966499 since we'd no longer be installing a custom catalog source.

Comment 2 Samuel Padgett 2021-07-20 15:59:48 UTC
This is fixed indirectly by https://github.com/openshift/console/pull/9420. We no longer create a catalog source in our tests.

Comment 3 Samuel Padgett 2021-07-20 16:01:13 UTC
I might be wrong here. Looks like there is also a separate CatalogSource test. moving back to ASSIGNED.

Comment 5 Yanping Zhang 2021-07-30 07:02:07 UTC
Checked in ci job, "Interacting with CatalogSource page renders details about the redhat-operators catalog source" sometimes still failed in ci:
https://search.ci.openshift.org/?search=renders+details+about+the+redhat-operators+catalog+source&maxAge=168h&context=1&type=bug%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.9-console-aws/1420925158113153024

AssertionError: Timed out retrying after 300000ms: expected '<dd.details-item__value>' to have text 'READY', but the text was '-'

Could the failure be avoid completely?

Comment 6 David Taylor 2021-07-30 14:04:33 UTC
The test suite requires that the 'redhat-operators' catalog source be in a READY status so it can test modifing it's registry poll interval, lists it's package manifests, and verifing fields on it's detail page.  

300000ms = 5 mins.!  Surprised it takes this long, is that expected?  In another OLM test I know we wait up to 12 minutes for a particular operator to finish installing.  Does installing a catalog source take as long?  Wondering if increasing the timeout would fix this flake.

Comment 7 David Taylor 2021-09-10 16:12:59 UTC
Hi, I do not see any CI failures for this issue in the 4.9 branch in the last 14 days:
https://search.ci.openshift.org/?search=Interacting+with+CatalogSource+page%5C.Interacting+with+CatalogSource+page+renders+details+about+the+redhat-
operators+catalog+source&maxAge=336h&context=1&type=junit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

I do see failures in the 4.8 branch, we should backport the 4.9 fix (https://github.com/openshift/console/pull/9570) to 4.8 if we want to elimiate the flakes in the 4.8 branch.

Hi yanpzhan, 
I watched the video of the 4.9-console-aws/1420925158113153024 CI run you posted, the 'redhat-operators' catalog source's STATUS was '-', it didn't get to READY within the 5 minute timeout -however, I think this was a network issue considering I don't see this happening anymore in the 4.9 branch within the last 14 days.

We should consider closing this 4.9 BZ and creating a new one to backport this to 4.8 if desired.

Comment 11 errata-xmlrpc 2021-10-18 17:36:53 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:3759


Note You need to log in before you can comment on or make changes to this bug.