Bug 1878150

Summary: CVP Produced Index Image Fails To Start
Product: OpenShift Container Platform Reporter: Matt Mahoney <mmahoney>
Component: OLMAssignee: Evan Cordell <ecordell>
OLM sub component: OLM QA Contact: Jian Zhang <jiazha>
Status: CLOSED DUPLICATE Docs Contact:
Severity: urgent    
Priority: unspecified CC: krizza
Version: 4.5   
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:
Last Closed: 2020-09-11 15:04:55 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 Matt Mahoney 2020-09-11 13:28:45 UTC 
Description of problem:

CVP produced index image for a Kiali build produced 'registry-proxy.engineering.redhat.com/rh-osbs/iib:8384', but pod fails to start when attempting to create a Catalog Source with this image

sudo podman run -it registry-proxy.engineering.redhat.com/rh-osbs/iib:8384
/bin/opm: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /bin/opm)

Reference CVP build http://external-ci-coldstorage.datahub.redhat.com/cvp/cvp-redhat-operator-bundle-image-validation-test/openshift-istio-kiali-operator-metadata-container-1.8-1/c1fef07c-8150-43f1-b312-e8952a33934e/

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

How reproducible:


Steps to Reproduce:
1. Create Catalog Source:
{
    "kind": "List",
    "apiVersion": "v1",
    "metadata": {},
    "items": [
        {
            "apiVersion": "operators.coreos.com/v1alpha1",
            "kind": "CatalogSource",
            "metadata": {
                "name": "kiali-manifests"
            },
            "spec": {
                "image": "registry-proxy.engineering.redhat.com/rh-osbs/iib:8384",
                "sourceType": "grpc"
            }
        }
    ]
}

2.
3.

Actual results:
Pod fails to start

Expected results:
Pod is expected to start

Additional info:
Comment 1 Kevin Rizza 2020-09-11 15:04:55 UTC 

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