Bug 1769136 - Spinning up 4.3 cluster with OVN network seems to timeout consistently
Summary: Spinning up 4.3 cluster with OVN network seems to timeout consistently
Keywords:
Status: CLOSED DUPLICATE of bug 1748162
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Casey Callendrello
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-05 23:15 UTC by Bowen Song
Modified: 2019-11-06 10:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-06 10:48:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Bowen Song 2019-11-05 23:15:11 UTC 
Description of problem:
Timeout installing 4.3 OpenShift cluster with OVN network happens consistently across different platforms (gcp, azure, aws ...) This 

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


How reproducible:
Not sure (It is 100% by CI on Nov 5th, 2019 after 12PM EST)

Steps to Reproduce:
1. Create a 4.3 Openshift Cluster (e.g.: registry.svc.ci.openshift.org/ocp/release:4.3.0-0.nightly-2019-11-05-211939) 
2.
3.

Actual results:
azure:
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-azure-ovn-kubernetes-4.3/2 

gcp:
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-ovn-kubernetes-4.3/2


Expected results:


Additional info:
Comment 3 W. Trevor King 2019-11-05 23:51:14 UTC 
While many of these 4.3 OVN jobs are failing, only the GCP jobs have the installer failing to hit the Kube API [1].

[1]: https://search.svc.ci.openshift.org/chart?name=ovn-kubernetes-4.3&search=Bootstrap%20failed%20to%20complete:%20waiting%20for%20Kubernetes%20API:%20context%20deadline%20exceeded&search=failed%20to%20initialize%20the%20cluster:%20Cluster%20operator%20monitoring%20is%20still%20updating&search=failed%20to%20initialize%20the%20cluster:%20Multiple%20errors%20are%20preventing%20progress&search=failed:.*The%20HAProxy%20router%20should
Comment 4 Casey Callendrello 2019-11-06 10:48:45 UTC 

*** This bug has been marked as a duplicate of bug 1748162 ***
Note You need to log in before you can comment on or make changes to this bug.