Cannot create kubernetes cluster with tls_disabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
magnum (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
1) cat /etc/lsb_release
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:
openstack coe cluster template create kubernetes-
where fedora-atomic-27 is Fedora-
I launch my cluster as follows:
openstack coe cluster create kubernetes-cluster \
Checking the status reports the following:
$ 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/
....
+ 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 inside the vm reports the following:
systemctl list-units | grep failed
● kube-apiserver.
Reviewing the log for the kube-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/
Is there anyway to fix this?
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.