Bug 1829405
| Summary: | test: Managed cluster should start all core operators: failure message too generic | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Periklis Tsirakidis <periklis> |
| Component: | Cluster Version Operator | Assignee: | W. Trevor King <wking> |
| Status: | CLOSED ERRATA | QA Contact: | liujia <jiajliu> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.4 | CC: | aos-bugs, bparees, jokerman, wking |
| Target Milestone: | --- | ||
| Target Release: | 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
test: [Feature:Platform][Early] Managed cluster should [Top Level] [Feature:Platform][Early] Managed cluster should start all core operators [Suite:openshift/conformance/parallel]
|
|
| Last Closed: | 2020-07-13 17:32:50 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
Periklis Tsirakidis
2020-04-29 14:02:36 UTC
Looking through the search results, this test fails on many different operators: https://search-clayton-ci-search.apps.build01.ci.devcluster.openshift.com/?search=Managed+cluster+should+start+all+core+operators+&maxAge=336h&context=2&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job 1) this bug should be used to improve the test to dump the operator status so we can determine why the operator in question was not available. 2) in the future when this test fails, bugs should opened against the operator that was not started. Taking a guess on CVO as the owner of this test, please reassign as needed. Retitled the bug to make it clear that the scope of this fix is getting a more specific error message out of the test (per comment 1). Once that lands there will be at least one follow-up bug that addresses the underlying operator issues that are leading to the test failures, but those operator-level changes are out of scope for this particular bug. Pulling UpcomingSprint back off. There's a PR up for this and it's in the merge queue; just needs to pass CI. Apparently this test is optional, because the final e2e-gcp run from the PR was green and also failed this test [1]: fail [github.com/openshift/origin/test/extended/operators/operators.go:159]: May 6 18:52:45.416: Some cluster operators never became ready: kube-apiserver (Progressing=True NodeInstaller: NodeInstallerProgressing: 1 nodes are at revision 4; 2 nodes are at revision 7) The blocking-ness of the test is an orthogonal issue, and the new message looks good, so marking VERIFIED. [1]: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/24948/pull-ci-openshift-origin-master-e2e-gcp/7619 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, 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/RHBA-2020:2409 |