Bug 1788818
Summary: | Install OCP 4.4 failed with error "openshift-ovn-kubernetes/ovnkube-node" rollout is not making progress | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | gaoshang <sgao> |
Component: | Networking | Assignee: | Ricardo Carrillo Cruz <ricarril> |
Networking sub component: | ovn-kubernetes | QA Contact: | zhaozhanqi <zzhao> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | urgent | ||
Priority: | urgent | CC: | ricarril, xtian |
Version: | 4.4 | ||
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-05-04 11:23:07 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
gaoshang
2020-01-08 07:49:19 UTC
This bug fixed in OCP 4.4.0-0.nightly-2020-01-12-032939, Version: # oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.4.0-0.nightly-2020-01-12-032939 True False 17m Cluster version is 4.4.0-0.nightly-2020-01-12-032939 Steps: 1, Install OCP 4.4 4.4.0-0.nightly-2020-01-12-032939 and succeed 2, Check ovnkube-node image updated # oc describe pod ovnkube-node-2sm9v -n openshift-ovn-kubernetes | grep "Image ID" Image ID: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ba36719f8d038c93b2ba4b8de7f12846d7b96fe812c64b2c74242d31e3061092 Image ID: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ba36719f8d038c93b2ba4b8de7f12846d7b96fe812c64b2c74242d31e3061092 Hey @gaoshang , so is this fixed then , can we close the bug? (In reply to Ricardo Carrillo Cruz from comment #2) > Hey @gaoshang , so is this fixed then , can we close the bug? According to above comment, moved bug status to VERIFIED, thanks. 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, 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/RHBA-2020:0581 |