● bootkube.service - Bootstrap a Kubernetes cluster
Loaded: loaded (/etc/systemd/system/bootkube.service; static; vendor preset: disabled)
Active: active (exited) (Result: exit-code) since Thu 2018-10-25 19:34:03 UTC; 1h 33min ago
Process: 913 ExecStart=/opt/tectonic/bootkube.sh (code=exited, status=125)
Main PID: 913 (code=exited, status=125)
Memory: 0B
CGroup: /system.slice/bootkube.service
Oct 25 19:34:03 localhost.localdomain systemd[1]: Started Bootstrap a Kubernetes cluster.
Oct 25 19:34:03 localhost.localdomain systemd[1]: Starting Bootstrap a Kubernetes cluster...
Oct 25 19:34:04 localhost.localdomain bootkube.sh[913]: Trying to pull registry.svc.ci.openshift.org/ci-op-nvfgsy47/release:latest...Failed
Oct 25 19:34:05 localhost.localdomain bootkube.sh[913]: unable to pull registry.svc.ci.openshift.org/ci-op-nvfgsy47/release:latest: unable to pull image: Error determining manifest MIME type for docker://registry.svc.ci.openshift.org/ci-op-nvfgsy47/release:latest: pinging docker...
Oct 25 19:34:05 localhost.localdomain systemd[1]: bootkube.service: main process exited, code=exited, status=125/n/a
Hint: Some lines were ellipsized, use -l to show in full.
[core@ip-10-0-6-79 ~]$ ps aux | grep 913
core 16482 0.0 0.0 10688 972 pts/0 S+ 21:07 0:00 grep --color=auto 913
[core@ip-10-0-6-79 ~]$ journalctl -u bootkube
-- Logs begin at Thu 2018-10-25 19:33:29 UTC, end at Thu 2018-10-25 21:08:07 UTC. --
Oct 25 19:34:03 localhost.localdomain systemd[1]: Started Bootstrap a Kubernetes cluster.
Oct 25 19:34:03 localhost.localdomain systemd[1]: Starting Bootstrap a Kubernetes cluster...
Oct 25 19:34:04 localhost.localdomain bootkube.sh[913]: Trying to pull registry.svc.ci.openshift.org/ci-op-nvfgsy47/release:latest...Failed
Oct 25 19:34:05 localhost.localdomain bootkube.sh[913]: unable to pull registry.svc.ci.openshift.org/ci-op-nvfgsy47/release:latest: unable to pull image: Error determining manifest MIME type for docker://registry.svc.ci.openshift.org/ci-op-nvfgsy47/release:latest: pinging docker re
Oct 25 19:34:05 localhost.localdomain systemd[1]: bootkube.service: main process exited, code=exited, status=125/n/a
[core@ip-10-0-6-79 ~]$ systemctl cat bootkube
# /etc/systemd/system/bootkube.service
[Unit]
Description=Bootstrap a Kubernetes cluster
Wants=kubelet.service
After=kubelet.service
[Service]
WorkingDirectory=/opt/tectonic
RemainAfterExit=true
ExecStart=/opt/tectonic/bootkube.sh
Restart=on-failure
RestartSec=5s
The bootkube service should have started.
In one one my ci runs https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/146/pull-ci-openshift-machine-config-operator-master-e2e-aws/117
Platform (aws|libvirt|openshift):
AWS
What happened?
The bootkube service failed die to dns blip and was not restarted
What you expected to happen?
The bootkube service should have started.