Bug 1786261

Summary:	[OVN]On azure/AWS env when restart master node met error: reason:NetworkPluginNotReady message:Network plugin returns error: Missing CNI default network
Product:	OpenShift Container Platform	Reporter:	zhou ying <yinzhou>
Component:	Networking	Assignee:	Alexander Constantinescu <aconstan>
Networking sub component:	ovn-kubernetes	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	aconstan, bbennett, zzhao
Version:	4.3.0
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:
Clones:	1804078 (view as bug list)		Environment:
Last Closed:	2020-05-04 11:21:22 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:
Bug Blocks:	1804078

Description zhou ying 2019-12-24 06:30:44 UTC

Description of problem:
On azure env when restart master node met error: reason:NetworkPluginNotReady message:Network plugin returns error: Missing CNI default network

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-12-23-193915

How reproducible:
always

Steps to Reproduce:
1. Restart one of the master on azure env;

Actual results:
1. Check the pod runnning on the restart master node failed with error: network is not ready: runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: Missing CNI default network

Expected results:
1. Pod running well

Additional info:

Comment 8 zhaozhanqi 2020-01-13 08:16:02 UTC

verified this bug on 4.4.0-0.nightly-2020-01-13-010304
when the master or worker restarted. the apiserver pod can be worked well.

Comment 10 errata-xmlrpc 2020-05-04 11:21:22 UTC

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