Bug 1671178

Summary: Master fails to become ready because of failure to launch network pod
Product: OpenShift Container Platform Reporter: Eric Paris <eparis>
Component: NodeAssignee: Seth Jennings <sjenning>
Status: CLOSED DUPLICATE QA Contact: Jianwei Hou <jhou>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-31 01:37:35 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:
Attachments:
Description Flags
kubelet logs during failure
none
$ oc -n openshift-sdn describe pod ovs-7dddm none

Description Eric Paris 2019-01-31 00:39:00 UTC
A cluster failed to install because a master failed to come up because it was unable to run the sdn pod. I see this error in the logs (I will attach more logs)

pod_workers.go:186] Error syncing pod 6b46059d-24b7-11e9-93ee-0e8819974ef8 ("ovs-7dddm_openshift-sdn(6b46059d-24b7-11e9-93ee-0e8819974ef8)"), skipping: failed to "StartContainer" for "openvswitch" with ImageInspectError: "Failed to inspect image \"quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:b8ed77dd8962d6d76490dd8764b77d5061e43033561b49770a3c2006a95f4132\": rpc error: code = Unknown desc = Manifest does not match provided manifest digest sha256:b8ed77dd8962d6d76490dd8764b77d5061e43033561b49770a3c2006a95f4132"


version   4.0.0-0.2   False       True          6h        Unable to apply 4.0.0-0.2: the update could not be applied

Comment 1 Eric Paris 2019-01-31 00:41:08 UTC
Created attachment 1525199 [details]
kubelet logs during failure

Comment 2 Eric Paris 2019-01-31 00:44:54 UTC
Created attachment 1525200 [details]
$ oc -n openshift-sdn describe pod ovs-7dddm

Comment 3 Seth Jennings 2019-01-31 01:37:35 UTC

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