Bug 1999756

Summary:	NetworkManager-wait-online.service Fails when Deploying Dual-stack Cluster with 3 Master
Product:	OpenShift Container Platform	Reporter:	Adina Wolff <awolff>
Component:	Networking	Assignee:	Jaime Caamaño Ruiz <jcaamano>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aconstan, hpokorny
Version:	4.8	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.10.0
Hardware:	Unspecified
OS:	Linux
Whiteboard:	telco
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-09-21 16:11:53 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 Adina Wolff 2021-08-31 17:16:02 UTC

Version:

$ openshift-install version
4.8.8

Platform:

baremetal vm

Please specify:
IPI

What happened?

When deploying OCP with 3 masters (no workers) on dual-stack, the deployment usually (around 75%) fails to wait for bootstrapping
A look at the cluster shows a failure of services;

[core@master-0-1 ~]$ sudo systemctl list-units --failed
  UNIT                               LOAD   ACTIVE SUB    DESCRIPTION
● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online
● ovs-configuration.service          loaded failed failed Configures OVS with proper host networking configuration



What did you expect to happen?

Cluster is deployed successfully.

How to reproduce it (as minimally and precisely as possible)?

Install OCP on dualstack with 3 master and 0 workers.

Logs:
http://rhos-compute-node-10.lab.eng.rdu2.redhat.com/logs/NetworkManager-wait-online.log
http://rhos-compute-node-10.lab.eng.rdu2.redhat.com/logs/ovs-configuration.log
http://rhos-compute-node-10.lab.eng.rdu2.redhat.com/logs/log-bundle-20210901082821.tar.gz

Comment 1 Honza Pokorny 2021-09-07 16:19:20 UTC

This seems like a networking issue, would you mind having a look?

Comment 2 Ben Nemec 2021-09-09 22:19:53 UTC

configure-ovs is failing to create br-ex with a bond, so I think this is one for the ovn-kubernetes folks.

Comment 3 Jaime Caamaño Ruiz 2021-09-21 16:11:53 UTC


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