Bug 1768854 - network plugin is not ready: cni config uninitialized
Summary: network plugin is not ready: cni config uninitialized
Keywords:
Status: CLOSED DUPLICATE of bug 1767579
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Casey Callendrello
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-05 12:06 UTC by Maciej Szulik
Modified: 2019-11-05 13:05 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 13:05:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Maciej Szulik 2019-11-05 12:06:30 UTC 
This is happening consistently in https://github.com/openshift/origin/pull/23941 see the job history here:

https://prow.svc.ci.openshift.org/pr-history/?org=openshift&repo=origin&pr=23941
https://prow.svc.ci.openshift.org/job-history/origin-ci-test/pr-logs/directory/test_pull_request_origin_extended_conformance_install-release-3.11

I'm seeing:

runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized

and that prevents node from being restarted, more details eg. https://storage.googleapis.com/origin-ci-test/pr-logs/pull/23941/test_pull_request_origin_extended_conformance_install-release-3.11/1204/build-log.txt
Comment 1 Maciej Szulik 2019-11-05 12:07:15 UTC 
From what I've checked this is blocking entire submit queue for 3.11
Comment 2 Casey Callendrello 2019-11-05 13:03:41 UTC 
There is another bug, where Aniket Bhat is looking in to this. So far, he's found that the sdn pod isn't even scheduled on the node! If you have any idea why, please let us know.
Comment 3 Casey Callendrello 2019-11-05 13:05:00 UTC 

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