Bug 1958643
| Summary: | All pods creation stuck due to SR-IOV webhook timeout | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Sabina Aledort <saledort> | ||||
| Component: | Networking | Assignee: | zenghui.shi <zshi> | ||||
| Networking sub component: | SR-IOV | QA Contact: | zhaozhanqi <zzhao> | ||||
| Status: | CLOSED ERRATA | Docs Contact: | |||||
| Severity: | urgent | ||||||
| Priority: | unspecified | CC: | keyoung, saledort, sscheink, yjoseph, ykashtan | ||||
| Version: | 4.8 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.8.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: | 2021-07-27 23:07:32 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: | |||||||
| Attachments: |
|
||||||
|
Description
Sabina Aledort
2021-05-09 13:42:55 UTC
we also know that the previous build (v4.8.0.202105042126.p0-1) did not exhibit this error The problem was the upgrade of the admission webhook to version v1 I open PR to fix it. https://github.com/k8snetworkplumbingwg/sriov-network-operator/pull/131 @Sebastian Scheinkman seems I did not meet this issue when I setup the version 4.8.0-202105080740.p0 # oc get csv NAME DISPLAY VERSION REPLACES PHASE sriov-network-operator.4.8.0-202105080740.p0 SR-IOV Network Operator 4.8.0-202105080740.p0 Succeeded # oc get pod NAME READY STATUS RESTARTS AGE network-resources-injector-8mksv 1/1 Running 0 4m28s network-resources-injector-949kk 1/1 Running 0 4m43s network-resources-injector-glskv 1/1 Running 0 5m1s operator-webhook-5kglx 1/1 Running 0 4m43s operator-webhook-qssgz 1/1 Running 0 4m28s operator-webhook-x9k8b 1/1 Running 0 5m1s sriov-cni-j6ntc 2/2 Running 0 4m40s sriov-device-plugin-g7hfr 1/1 Running 0 4m19s sriov-network-config-daemon-wb424 1/1 Running 0 5m4s sriov-network-config-daemon-xk48z 1/1 Running 0 4m44s sriov-network-operator-cd85d8457-5swhp 1/1 Running 0 5m34s also have a try with upgrade from sriov-network-operator.4.8.0-202105042126.p0 to 4.8.0-202105080740.p0 # oc get csv -n openshift-sriov-network-operator NAME DISPLAY VERSION REPLACES PHASE sriov-network-operator.4.8.0-202105080740.p0 SR-IOV Network Operator 4.8.0-202105080740.p0 sriov-network-operator.4.8.0-202105042126.p0 Succeeded Hi, Sabina Could you help verified this bug? or if you can provide the steps to reproduce this issue since it's not happen in our QE side, thanks (In reply to zhaozhanqi from comment #7) > Hi, Sabina > > Could you help verified this bug? or if you can provide the steps to > reproduce this issue since it's not happen in our QE side, thanks Hi, @Sebastian Scheinkman's PR fixed the issue. All the pods are up and running. Tested image: registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-sriov-network-operator-bundle:v4.8.0.202105111002.p0-1 Thanks, Sabina then move this bug to verified according to 8 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438 |