Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1745546

Summary:	[osp] cluster cannot be setup with OVN network type
Product:	OpenShift Container Platform	Reporter:	zhaozhanqi <zzhao>
Component:	Networking	Assignee:	Aniket Bhat <anbhat>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	medium
Priority:	medium	CC:	anbhat, anusaxen, aos-bugs, bbennett, eduen, nagrawal
Version:	4.2.0	Keywords:	TestBlocker
Target Milestone:	---	Flags:	anusaxen: needinfo-
Target Release:	4.4.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-21 21:04:39 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 zhaozhanqi 2019-08-26 10:57:28 UTC

Description of problem:
Setup the cluster with ovn network type on openstack. api cannot be running.

ssh into master. check the master contaniers failed:

# crictl ps -a | grep ovn
30e454b62226a       96612f5dfeb3288d44567ad96bbbaa1c03e03a84a85d65971cc0dee7110f4bd1                                                         2 hours ago         Exited              ovn-node            2                   6b77f539f7124
eca7b6593f841       96612f5dfeb3288d44567ad96bbbaa1c03e03a84a85d65971cc0dee7110f4bd1                                                         2 hours ago         Exited              ovn-controller      2                   6b77f539f7124


crictl logs eca7b6593f841
================== ovnkube.sh --- version: 3 ================
 ==================== command: ovn-controller
 =================== hostname: qe-zzhao-ovn-dwfj9-master-2
 =================== daemonset version 3
 =================== Image built from ovn-kubernetes ref: refs/heads/rhaos-4.2-rhel-7  commit: fb435e034a426d1a11fc61b284426e8ea82187ee
=============== ovn-controller - (wait for ovs)
=============== ovn-controller - (wait for ready_to_start_node)
info: Waiting for ready_to_start_node  to come up, waiting 1s ...
info: Waiting for ready_to_start_node  to come up, waiting 5s ...
info: Waiting for ready_to_start_node  to come up, waiting 5s ...
info: Waiting for ready_to_start_node  to come up, waiting 5s ...
info: Waiting for ready_to_start_node  to come up, waiting 5s ...
info: Waiting for ready_to_start_node  to come up, waiting 5s ...
info: Waiting for ready_to_start_node  to come up, waiting 5s ...
info: Waiting for ready_to_start_node  to come up, waiting 5s ...
info: Waiting for ready_to_start_node  to come up, waiting 5s ...
info: Waiting for ready_to_start_node  to come up, waiting 5s ...
info: Waiting for ready_to_start_node  to come up, waiting 5s ...
info: Waiting for ready_to_start_node  to come up, waiting 5s ...
info: Waiting for ready_to_start_node  to come up, waiting 5s ...
info: Waiting for ready_to_start_node  to come up, waiting 5s ...
info: Waiting for ready_to_start_node  to come up, waiting 5s ...
info: Waiting for ready_to_start_node  to come up, waiting 5s ...
error: ready_to_start_node  did not come up, exiting



Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-08-25-233755

How reproducible:
alweys

Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info:
openshift-sdn works well on OSP

Comment 1 Casey Callendrello 2019-08-26 11:04:29 UTC

Need to check that we care at all about OVN-Kubernetes on OpenStack. I'm happy moving this out of 4.2.

Comment 2 Ben Bennett 2019-09-05 13:46:04 UTC

For the 4.2 tech preview of ovn-kubernetes, we will not support OpenStack IPI.  You could do a UPI installation on OpenStack if necessary.

Comment 3 zhaozhanqi 2019-09-11 01:53:28 UTC

@Ben Bennett

 UPI on OSP installation do not be supported yet for 4.2 now. So we still cannot test OVN on OSP for 4.2

Comment 4 Ben Bennett 2019-11-14 20:04:26 UTC

I believe this is fixed with the 4.3 work.

Comment 6 Aniket Bhat 2020-01-21 19:06:10 UTC

@Anurag: Does this need to be reverified now that the GCP cluster is able to come up with OVN?

Comment 8 Aniket Bhat 2020-01-21 21:04:39 UTC


*** This bug has been marked as a duplicate of bug 1748162 ***