Bug 1779863
| Summary: | GCP OVN 4.3 install jobs consistently timing out waiting for multus | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jonathan Lebon <jlebon> | |
| Component: | Networking | Assignee: | Alexander Constantinescu <aconstan> | |
| Networking sub component: | ovn-kubernetes | QA Contact: | zhaozhanqi <zzhao> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | unspecified | |||
| Priority: | unspecified | CC: | aconstan, anusaxen, bbennett, dcbw, dosmith, hongkliu, igortiunov, jchaloup, pmuller | |
| Version: | 4.3.z | |||
| Target Milestone: | --- | |||
| Target Release: | 4.3.z | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1801634 (view as bug list) | Environment: | ||
| Last Closed: | 2020-02-25 06:17:59 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: | ||||
| Bug Depends On: | 1801634 | |||
| Bug Blocks: | ||||
|
Description
Jonathan Lebon
2019-12-04 21:17:04 UTC
This looks very similar to something reported yesterday to the openshift-sdn team. In the case of the similar problem, it was reported that: ``` DaemonSet "openshift-multus/multus" rollout is not making progress ``` By the cluster-network-operator in these logs @ https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade/11961#1:build-log.txt%3A6927 It should be noted that the multus-admission-controller is not a dependency of any other function in the cluster (that is, multus doesn't need to wait for it, and neither does the openshift-sdn) That being said, I believe that this is a symptom and not a cause of the core issue. Did the master nodes become ready? As that was also a symptom of the issue reported yesterday that: ``` NodeControllerDegraded: The master node(s) \"ip-10-0-129-3.ec2.internal\" not ready ``` This looks very similar to something reported yesterday to the openshift-sdn team. In the case of the similar problem, it was reported that: ``` DaemonSet "openshift-multus/multus" rollout is not making progress ``` By the cluster-network-operator in these logs @ https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade/11961#1:build-log.txt%3A6927 It should be noted that the multus-admission-controller is not a dependency of any other function in the cluster (that is, multus doesn't need to wait for it, and neither does the openshift-sdn) That being said, I believe that this is a symptom and not a cause of the core issue. Did the master nodes become ready? As that was also a symptom of the issue reported yesterday that: ``` NodeControllerDegraded: The master node(s) \"ip-10-0-129-3.ec2.internal\" not ready ``` GCP-OVN installation is blocked in 4.3 though due to various reasons https://bugzilla.redhat.com/show_bug.cgi?id=1748162 *** Bug 1781695 has been marked as a duplicate of this bug. *** GCP + OVN is fine now that MTU issues have been sorted out. Do we have recent CI failures here that we can debug? Please see https://bugzilla.redhat.com/show_bug.cgi?id=1748162#c64 OVN can be installed in GCP cluster in 4.4.0-0.nightly-2020-01-16-113546 Here's a 4.3 CI failure from today: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-ovn-4.3/358 QE will retest it in latest v4.3 verified this bug on 4.3.0-0.nightly-2020-02-13-214539 https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-ovn-4.3/440 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:0528 |