Bug 1949202

Summary: sriov-network-operator not available from operatorhub on ppc64le
Product: OpenShift Container Platform Reporter: Manoj Kumar <manokuma>
Component: NetworkingAssignee: zenghui.shi <zshi>
Networking sub component: SR-IOV QA Contact: Manoj Kumar <manokuma>
Status: CLOSED NOTABUG Docs Contact:
Severity: high    
Priority: unspecified CC: zzhao
Version: 4.8   
Target Milestone: ---   
Target Release: 4.8.0   
Hardware: ppc64le   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-01 19:43:10 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 Manoj Kumar 2021-04-13 17:30:51 UTC
Description of problem:  The SRIOV operator cannot be installed from operatorhub.


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


How reproducible: Consistent

Steps to Reproduce:
1. Login to OpenShift Console/UI on a ppc64le clusetr
2. Switch to Operator view
3.

Actual results: No SRIOV-Network operator available for deploy on ppc64le clusters


Expected results: SRIOV-network-operator available as an option


Additional info:

Comment 1 zhaozhanqi 2021-04-14 02:35:53 UTC
Manoj I guess you already tested with the fixed PR

Can you verified this bug since I do have have one cluster with ppc64le
thanks.

Comment 3 zhaozhanqi 2021-04-15 00:42:03 UTC
@manokuma could you help verify this bug? thanks

Comment 4 Manoj Kumar 2021-04-15 22:19:33 UTC
Having trouble pulling the built image:

  Normal   Scheduled       4m9s                   default-scheduler  Successfully assigned openshift-marketplace/6be9abfdb729e4a82da5c624230c46789275a258f64303737996d1a7ce57w8z to test-zcjqn-worker-0-4hkb9
  Normal   AddedInterface  4m7s                   multus             Add eth0 [10.128.2.25/23]
  Normal   Pulling         4m7s                   kubelet            Pulling image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:fdfd43236fa206a63c5a2b0758019dbb6a253ca88e9c30f876a1260e58c5a147"
  Normal   Pulled          3m59s                  kubelet            Successfully pulled image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:fdfd43236fa206a63c5a2b0758019dbb6a253ca88e9c30f876a1260e58c5a147" in 7.675435154s
  Normal   Created         3m59s                  kubelet            Created container util
  Normal   Started         3m59s                  kubelet            Started container util
  Warning  Failed          3m16s (x3 over 3m57s)  kubelet            Error: ErrImagePull
  Normal   BackOff         2m42s (x5 over 3m56s)  kubelet            Back-off pulling image "registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-sriov-network-operator-bundle@sha256:90bef48a7e9a915b7495235d97d61e600cfd9a7072d019dc6f601462dbb0a365"
  Warning  Failed          2m42s (x5 over 3m56s)  kubelet            Error: ImagePullBackOff
  Normal   Pulling         2m31s (x4 over 3m58s)  kubelet            Pulling image "registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-sriov-network-operator-bundle@sha256:90bef48a7e9a915b7495235d97d61e600cfd9a7072d019dc6f601462dbb0a365"
  Warning  Failed          2m30s (x4 over 3m57s)  kubelet            Failed to pull image "registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-sriov-network-operator-bundle@sha256:90bef48a7e9a915b7495235d97d61e600cfd9a7072d019dc6f601462dbb0a365": rpc error: code = Unknown desc = (Mirrors also failed: [brew.registry.redhat.io/rh-osbs/openshift-ose-sriov-network-operator-bundle@sha256:90bef48a7e9a915b7495235d97d61e600cfd9a7072d019dc6f601462dbb0a365: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/articles/3399531]): registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-sriov-network-operator-bundle@sha256:90bef48a7e9a915b7495235d97d61e600cfd9a7072d019dc6f601462dbb0a365: error pinging docker registry registry-proxy.engineering.redhat.com: Get "https://registry-proxy.engineering.redhat.com/v2/": dial tcp: lookup registry-proxy.engineering.redhat.com on 192.168.126.1:53: no such host

Comment 7 Manoj Kumar 2021-07-01 19:43:10 UTC
Console on 4.8 does not show this operator as being available.

New BZs have been opened for 4.8 and 4.9 to get this resolved. 

https://bugzilla.redhat.com/show_bug.cgi?id=1978437
https://bugzilla.redhat.com/show_bug.cgi?id=1978435

Closing.