Checking the status of failed services reports the following:
systemctl list-units | grep failed
● kube-apiserver.service loaded failed failed kubernetes-apiserver
Reviewing the log for the kube-apiserver.service reveals the true issue:
-- Logs begin at Thu 2018-12-20 12:52:47 UTC, end at Thu 2018-12-20 13:06:07 UTC. --
Dec 20 12:58:44 kubernetes-cluster-lathbpb54t7w-master-0.novalocal systemd[1]: Started kubernetes-apiserver.
Dec 20 12:58:46 kubernetes-cluster-lathbpb54t7w-master-0.novalocal runc[1966]: I1220 12:58:45.991182 1 server.go:121] Version: v1.9.3
Dec 20 12:58:47 kubernetes-cluster-lathbpb54t7w-master-0.novalocal runc[1966]: error creating self-signed certificates: open /var/run/kubernetes/apiserver.crt: permission denied
Dec 20 12:58:47 kubernetes-cluster-lathbpb54t7w-master-0.novalocal systemd[1]: kube-apiserver.service: Main process exited, code=exited, status=1/FAILURE
Dec 20 12:58:47 kubernetes-cluster-lathbpb54t7w-master-0.novalocal systemd[1]: kube-apiserver.service: Unit entered failed state.
Dec 20 12:58:47 kubernetes-cluster-lathbpb54t7w-master-0.novalocal systemd[1]: kube-apiserver.service: Failed with result 'exit-code'.
Dec 20 12:58:47 kubernetes-cluster-lathbpb54t7w-master-0.novalocal systemd[1]: kube-apiserver.service: Service hold-off time over, scheduling restart.
Dec 20 12:58:47 kubernetes-cluster-lathbpb54t7w-master-0.novalocal systemd[1]: Stopped kubernetes-apiserver.
Dec 20 12:58:47 kubernetes-cluster-lathbpb54t7w-master-0.novalocal systemd[1]: Started kubernetes-apiserver.
Dec 20 12:58:47 kubernetes-cluster-lathbpb54t7w-master-0.novalocal runc[2261]: I1220 12:58:47.544421 1 server.go:121] Version: v1.9.3
Dec 20 12:58:47 kubernetes-cluster-lathbpb54t7w-master-0.novalocal runc[2261]: error creating self-signed certificates: open /var/run/kubernetes/apiserver.crt: permission denied
Dec 20 12:58:47 kubernetes-cluster-lathbpb54t7w-master-0.novalocal systemd[1]: kube-apiserver.service: Main process exited, code=exited, status=1/FAILURE
Dec 20 12:58:47 kubernetes-cluster-lathbpb54t7w-master-0.novalocal systemd[1]: kube-apiserver.service: Unit entered failed state.
Dec 20 12:58:47 kubernetes-cluster-lathbpb54t7w-master-0.novalocal systemd[1]: kube-apiserver.service: Failed with result 'exit-code'.
Dec 20 12:58:47 kubernetes-cluster-lathbpb54t7w-master-0.novalocal systemd[1]: kube-apiserver.service: Service hold-off time over, scheduling restart.
Dec 20 12:58:47 kubernetes-cluster-lathbpb54t7w-master-0.novalocal systemd[1]: Stopped kubernetes-apiserver.
Dec 20 12:58:48 kubernetes-cluster-lathbpb54t7w-master-0.novalocal systemd[1]: Started kubernetes-apiserver.
So apparently I cannot access /var/run/kubernetes/.
1) cat /etc/lsb_release RELEASE= 18.04 CODENAME= bionic DESCRIPTION= "Ubuntu 18.04.1 LTS"
DISTRIB_ID=Ubuntu
DISTRIB_
DISTRIB_
DISTRIB_
2) My setup is:
Openstack Queens
magnum-api 6.1.0-0ubuntu1
magnum-common 6.1.0-0ubuntu1
magnum-conductor 6.1.0-0ubuntu1
python-magnum 6.1.0-0ubuntu1
python-magnumclient 2.8.0-0ubuntu1
3) What you expected to happen:
Create a kubernetes cluster
4) What happened instead:
I create the following template: cluster- template \
--image fedora-atomic-27 \
--external- network external \
--dns-nameserve r 8.8.8.8 \
--master- flavor m1.medium \
--flavor m1.medium \
--docker- storage- driver overlay2 \
--coe kubernetes \
--tls-disabled
openstack coe cluster template create kubernetes-
where fedora-atomic-27 is Fedora- Atomic- 27-20180419. 0.x86_64. qcow2
I launch my cluster as follows:
--cluster- template kubernetes- cluster- template \
--master- count 1 \
--node- count 1 \
--keypair magnum
openstack coe cluster create kubernetes-cluster \
Checking the status reports the following: ------- ------- -+----- ------- ------- ------- ------- ------- ------- ------- ------+ ------- ------- -+----- ------- ------- ------- ------- ------- ------- ------- ------+ 10a5-4a64- 9da6-db02322afc 18 | b351-4903- 9237-a94e913930 7b | 7469-4ad8- 920a-9a38955f8d 10 | 20T12:50: 07+00:00 | 20T12:50: 13+00:00 | /discovery. etcd.io/ 5e3c06417323e4b 2c267e74bbcf0a4 02 | ------- ------- -+----- ------- ------- ------- ------- ------- ------- ------- ------+
$ openstack coe cluster show kubernetes-cluster
+------
| Field | Value |
+------
| status | CREATE_IN_PROGRESS |
| cluster_template_id | 5cf527fd-
| node_addresses | [] |
| uuid | 1a9490c2-
| stack_id | 3bd7783f-
| status_reason | None |
| created_at | 2018-12-
| updated_at | 2018-12-
| coe_version | None |
| labels | {} |
| faults | |
| keypair | magnum |
| api_address | None |
| master_addresses | [] |
| create_timeout | 60 |
| node_count | 1 |
| discovery_url | https:/
| master_count | 1 |
| container_version | None |
| name | kubernetes-cluster |
| master_flavor_id | m1.medium |
| flavor_id | m1.medium |
+------
The status is always stuck in CREATE_IN_PROGRESS.
Checking the /var/log/ cloud-init- output. log reports the following:
.... 127.0.0. 1:8080/ version 127.0.0. 1:8080/ version 127.0.0. 1:8080/ version 127.0.0. 1:8080/ version 127.0.0. 1:8080/ version
+ echo 'Waiting for Kubernetes API...'
Waiting for Kubernetes API...
+ curl --silent http://
+ sleep 5
+ curl --silent http://
+ sleep 5
+ curl --silent http://
+ sleep 5
+ curl --silent http://
+ sleep 5
+ curl --silent http://
+ sleep 5
Checking the status of failed services reports the following: service loaded failed failed kubernetes- apiserver
systemctl list-units | grep failed
● kube-apiserver.
Reviewing the log for the kube-apiserver. service reveals the true issue: cluster- lathbpb54t7w- master- 0.novalocal systemd[1]: Started kubernetes- apiserver. cluster- lathbpb54t7w- master- 0.novalocal runc[1966]: I1220 12:58:45.991182 1 server.go:121] Version: v1.9.3 cluster- lathbpb54t7w- master- 0.novalocal runc[1966]: error creating self-signed certificates: open /var/run/ kubernetes/ apiserver. crt: permission denied cluster- lathbpb54t7w- master- 0.novalocal systemd[1]: kube-apiserver. service: Main process exited, code=exited, status=1/FAILURE cluster- lathbpb54t7w- master- 0.novalocal systemd[1]: kube-apiserver. service: Unit entered failed state. cluster- lathbpb54t7w- master- 0.novalocal systemd[1]: kube-apiserver. service: Failed with result 'exit-code'. cluster- lathbpb54t7w- master- 0.novalocal systemd[1]: kube-apiserver. service: Service hold-off time over, scheduling restart. cluster- lathbpb54t7w- master- 0.novalocal systemd[1]: Stopped kubernetes- apiserver. cluster- lathbpb54t7w- master- 0.novalocal systemd[1]: Started kubernetes- apiserver. cluster- lathbpb54t7w- master- 0.novalocal runc[2261]: I1220 12:58:47.544421 1 server.go:121] Version: v1.9.3 cluster- lathbpb54t7w- master- 0.novalocal runc[2261]: error creating self-signed certificates: open /var/run/ kubernetes/ apiserver. crt: permission denied cluster- lathbpb54t7w- master- 0.novalocal systemd[1]: kube-apiserver. service: Main process exited, code=exited, status=1/FAILURE cluster- lathbpb54t7w- master- 0.novalocal systemd[1]: kube-apiserver. service: Unit entered failed state. cluster- lathbpb54t7w- master- 0.novalocal systemd[1]: kube-apiserver. service: Failed with result 'exit-code'. cluster- lathbpb54t7w- master- 0.novalocal systemd[1]: kube-apiserver. service: Service hold-off time over, scheduling restart. cluster- lathbpb54t7w- master- 0.novalocal systemd[1]: Stopped kubernetes- apiserver. cluster- lathbpb54t7w- master- 0.novalocal systemd[1]: Started kubernetes- apiserver.
-- Logs begin at Thu 2018-12-20 12:52:47 UTC, end at Thu 2018-12-20 13:06:07 UTC. --
Dec 20 12:58:44 kubernetes-
Dec 20 12:58:46 kubernetes-
Dec 20 12:58:47 kubernetes-
Dec 20 12:58:47 kubernetes-
Dec 20 12:58:47 kubernetes-
Dec 20 12:58:47 kubernetes-
Dec 20 12:58:47 kubernetes-
Dec 20 12:58:47 kubernetes-
Dec 20 12:58:47 kubernetes-
Dec 20 12:58:47 kubernetes-
Dec 20 12:58:47 kubernetes-
Dec 20 12:58:47 kubernetes-
Dec 20 12:58:47 kubernetes-
Dec 20 12:58:47 kubernetes-
Dec 20 12:58:47 kubernetes-
Dec 20 12:58:47 kubernetes-
Dec 20 12:58:48 kubernetes-
So apparently I cannot access /var/run/ kubernetes/ .
Is there anyway to fix this?