Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-32477

"update failure status Build status OutOfMemoryKilled should contain OutOfMemoryKilled failure reason and message" is failing on 4.15

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • 4.16.0
    • 4.15
    • Build
    • None
    • Important
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

      Version-Release number of selected component (if applicable):

      How reproducible:

       [sig-builds][Feature:Builds][Slow] update failure status Build status OutOfMemoryKilled should contain OutOfMemoryKilled failure reason and message [apigroup:build.openshift.io] test is failing on 4.15 (e.g. https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_oc/1726/pull-ci-openshift-oc-release-4.15-e2e-aws-ovn-builds/1780913191149113344)

      Steps to Reproduce:

          1. 
    2.
    3.

      Actual results:

      Expected results:

      Additional info:

      https://github.com/containerd/containerd/issues/8180 would be the reason of failure. Because in 4.15 the expected status is OOMKilled however test fails after getting an Error status with the correct exit code (137)  

            aguclu@redhat.com Arda Guclu
            aguclu@redhat.com Arda Guclu
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: