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

Bug 1796127

Summary: Memory-related issues in release-openshift-ocp-installer-e2e-metal-4.3 jobs
Product: OpenShift Container Platform Reporter: Petr Muller <pmuller>
Component: Test InfrastructureAssignee: Steve Kuznetsov <skuznets>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: bparees, ccoleman, sdodson
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-03 15:03:06 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 Petr Muller 2020-01-29 16:46:14 UTC 
Description of problem:

Recent runs of release-openshift-ocp-installer-e2e-metal-4.3 jobs exhibit many test failures where the symptom is "cannot allocate memory":



https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-metal-4.3/1193
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-metal-4.3/1192

This looks to me that the test template for metal is somehow installing clusters on insufficient nodes and that should be fixed - I honestly have no idea about where to actually assign this.
Comment 1 Steve Kuznetsov 2020-01-29 17:12:22 UTC 
$ git log --no-merges --pretty=%ae -- ci-operator/templates/openshift/installer/cluster-launch-installer-metal-e2e.yaml | sort | uniq -c | sort -nr | head -n 5
     12 ccoleman
      7 abhinav.dahiya
      5 bparees
      4 sdodson
      3 crawford
Comment 2 Ben Parees 2020-01-29 19:49:05 UTC 
Scott Dodson noted that the allocation error appears to be occurring within the test pod running on api.ci, not in the cluster under test.  So we'd need to scale up the size of the test pod.  I will look at submitting a PR.
Comment 5 Scott Dodson 2020-02-03 15:03:06 UTC 
This hasn't happened in the past 72 hours where as it was happening quite frequently prior to this change.
Comment 6 Scott Dodson 2020-02-17 13:54:23 UTC 
*** Bug 1793675 has been marked as a duplicate of this bug. ***