Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1886840

Summary: operator install monitoring
Product: OpenShift Container Platform Reporter: Jing Zhang <jingzhan>
Component: MonitoringAssignee: Sergiusz Urbaniak <surbania>
Status: CLOSED DUPLICATE QA Contact: Junqi Zhao <juzhao>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.7CC: alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania, wking
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
operator install monitoring
Last Closed: 2020-10-10 04:17:54 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 Jing Zhang 2020-10-09 14:01:49 UTC 
test:
operator install monitoring 

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=operator+install+monitoring


FIXME: Replace this paragraph with a particular job URI from the search results to ground discussion.  A given test may fail for several reasons, and this bug should be scoped to one of those reasons.  Ideally you'd pick a job showing the most-common reason, but since that's hard to determine, you may also chose to pick a job at random.  Release-gating jobs (release-openshift-...) should be preferred over presubmits (pull-ci-...) because they are closer to the released product and less likely to have in-flight code changes that complicate analysis.

FIXME: Provide a snippet of the test failure or error from the job log
Comment 1 W. Trevor King 2020-10-10 04:17:54 UTC 
$ curl -s 'https://search.ci.openshift.org/search?search=operator+install+monitoring&maxAge=24h&type=junit&groupBy=job&name=release-openshift-ocp-installer-e2e-gcp-ovn-4.6' | jq -r 'keys[]'
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-ovn-4.6/1314410856292814848
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-ovn-4.6/1314697955512422400

Same two jobs as bug 1886842.  Makes sense that many components would be impacted by a control-plane kubelet failure, and no need to have all those teams perform separate investigations.

*** This bug has been marked as a duplicate of bug 1886842 ***