Bug 1976939
Summary: | Interacting with CatalogSource page.Interacting with CatalogSource page renders details about the redhat-operators catalog source | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Zack Zlotnik <zzlotnik> |
Component: | Management Console | Assignee: | David Taylor <dtaylor> |
Status: | CLOSED ERRATA | QA Contact: | Yanping Zhang <yanpzhan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.9 | CC: | aos-bugs, jokerman, sippy, spadgett, yapei |
Target Milestone: | --- | ||
Target Release: | 4.9.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
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 | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Zack Zlotnik
2021-06-28 15:33:31 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. This is fixed indirectly by https://github.com/openshift/console/pull/9420. We no longer create a catalog source in our tests. I might be wrong here. Looks like there is also a separate CatalogSource test. moving back to ASSIGNED. 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? 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. 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. Search in the ci there is no this error in 4.9 now. 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 Move the bug to Verified. 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 |