Bug 1786261 - [OVN]On azure/AWS env when restart master node met error: reason:NetworkPluginNotReady message:Network plugin returns error: Missing CNI default network
Summary: [OVN]On azure/AWS env when restart master node met error: reason:NetworkPlugi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.4.0
Assignee: Alexander Constantinescu
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks: 1804078
TreeView+ depends on / blocked
 
Reported: 2019-12-24 06:30 UTC by zhou ying
Modified: 2020-05-04 11:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1804078 (view as bug list)
Environment:
Last Closed: 2020-05-04 11:21:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift ovn-kubernetes pull 70 0 None closed Upstream + hybrid-overlay merge 2019-12-28 2021-02-08 20:00:10 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:21:47 UTC

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
Note You need to log in before you can comment on or make changes to this bug.