Bug 1652225 - After certificate redeploy nodes service is not starting static pods.
Summary: After certificate redeploy nodes service is not starting static pods.
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Master
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Michal Fojtik
QA Contact: Xingxing Xia
Depends On:
TreeView+ depends on / blocked
Reported: 2018-11-21 17:37 UTC by Ryan Howe
Modified: 2018-11-21 22:49 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-11-21 22:49:37 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Ryan Howe 2018-11-21 17:37:58 UTC
Description of problem:

 After redeploying the OpenShift CA and Master certificates, node is failing to start static pods. 

Version-Release number of selected component (if applicable):

Steps to Reproduce:
1. # systemctl restart atomic-openshift-node
2. Node service fails 

Actual results:
  Node service fails 
  Docker ps -a does not show any running or exited pods 
Expected results:

Pods in /etc/origin/node/pods/ to start. 
    apiserver.yaml  controller.yaml 

    atomic-openshift-node logs showing: 
    atomic-openshift-node[51213]: kubelet.go:1869] SyncLoop (ADD, "file"): "master-api-XXX_kube-system(97ac55b2f65e0be517207dcd5fc8d65c), master-controllers-master-0.XXX_kube-system(8e879171c85e221fb0a023e3f10ca276)"

Additional info:

 - `docker ps -a` output is empty
 - Pod and control plane images are pulled already to host. 
 - Docker does not show any errors 
 - Node logs exits before showing any Static pods adds.

Comment 5 Ryan Howe 2018-11-21 22:49:37 UTC
Wrong systemd unit file was being used that did not point to the correct start script for the atomic-openshift-node service.

Note You need to log in before you can comment on or make changes to this bug.