This was fixed by adding: [DEFAULT] ... region_name_for_services = <region name> ... to the heat configuration. Am 4/24/19 um 11:17 AM schrieb Florian Engelmann:
Hi Feilong,
I will answer in behalf of Pawel.
[root@kubernetes-cluster2-sdpti5674ukb-master-0 ~]# tail -n 25 /var/log/cloud-init-output.log Copying blob sha256:fb6ed010e89e8064d698019532ef87719e61ed83f10801b0ed0dee56cf46a988 240 B / 240 B 0s Copying config sha256:c1f47e73da637994ed9348a99dd25c5f66980ff887c9b2657ef48c8e481528a3 5.83 KB / 5.83 KB 0s Writing manifest to image destination Storing signatures Extracting to /var/lib/containers/atomic/heat-container-agent.0 systemctl daemon-reload systemd-tmpfiles --create /etc/tmpfiles.d/heat-container-agent.conf systemctl enable heat-container-agent + systemctl start heat-container-agent starting services activating service etcd activating service docker activating service kube-apiserver activating service kube-controller-manager activating service kube-scheduler activating service kubelet activating service kube-proxy creating /usr/local/bin/flannel-config Created symlink /etc/systemd/system/multi-user.target.wants/flannel-config.service → /etc/systemd/system/flannel-config.service. activating service flanneld activating service flanneld Cloud-init v. 0.7.9 running 'modules:final' at Wed, 24 Apr 2019 08:20:43 +0000. Up 18.36 seconds. Cloud-init v. 0.7.9 finished at Wed, 24 Apr 2019 08:24:38 +0000. Datasource DataSourceOpenStack [net,ver=2]. Up 253.24 seconds
What is the heat task
kube_cluster_deploy: type: OS::Heat::SoftwareDeployment properties: actions: ['CREATE'] signal_transport: HEAT_SIGNAL config: get_resource: kube_cluster_config server: get_attr: [kube_masters, resource.0]
ment to do?
Is it starting the scripts listed under kube_cluster_config?
kube_cluster_config: type: OS::Heat::SoftwareConfig properties: group: script config: list_join: - "\n" - - get_file: ../../common/templates/kubernetes/fragments/kube-apiserver-to-kubelet-role.sh
- str_replace: template: {get_file: ../../common/templates/kubernetes/fragments/enable-cert-api-manager.sh} params: "$CA_KEY": {get_param: ca_key} - get_file: ../../common/templates/kubernetes/fragments/core-dns-service.sh - str_replace: template: {get_file: ../../common/templates/kubernetes/fragments/enable-prometheus-monitoring.sh}
params: "$ADMIN_PASSWD": {get_param: grafana_admin_passwd} - get_file: ../../common/templates/kubernetes/fragments/calico-service.sh - str_replace: params: $enable-ingress-traefik: {get_file: ../../common/templates/kubernetes/fragments/enable-ingress-traefik.sh} template: {get_file: ../../common/templates/kubernetes/fragments/enable-ingress-controller.sh} - get_file: ../../common/templates/kubernetes/fragments/kube-dashboard-service.sh
All the best, Florian
Am 4/16/19 um 12:09 AM schrieb Feilong Wang:
Hi Pawel,
Firstly, please remove the tls-disabled param which it's a known issue. And m1.small is a bit small for master which 30mins timout maybe not enough. Please address them and try again, then if you still see error, pls provied the log /var/log/cloud-init-output.log on your master node. Cheers.
On 16/04/19 2:02 AM, Pawel Konczalski wrote:
Hi,
i try to deploy a kubernetes cluster on OpenStack rocky with Magnum. All Heat steps runs fine except for the last one "kube_cluster_deploy":
kube_cluster_deploy c3a79e96-87d8-442e-83f1-91d7a1acd896 1 minute Create Failed CREATE aborted (Task create from SoftwareDeployment "kube_cluster_deploy" Stack "kubernetes-cluster9-l4ol4ger3key" [b17bfab3-f46a-477b-921f-4719bfd8df06] Timed out)
The cluster contains three control / compute nodes, Octavia is also installed and works fine as far as I can see.
Atomic Image: https://dl.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-27-20180419...
The command was: openstack coe cluster template create kubernetes-cluster-template \ --image fedora-atomic-latest \ --external-network public \ --dns-nameserver 8.8.8.8 \ --master-flavor m1.small \ --flavor m1.large \ --coe kubernetes \ --docker-volume-size 10 \ --tls-disabled \ --floating-ip-enabled
openstack coe cluster create kubernetes-cluster \ --cluster-template kubernetes-cluster-template \ --master-count 1 \ --node-count 1 \ --timeout 30 \ --keypair mykey
Did someone run also into this Problem or know how to fix it?
BR
Pawel
-- EveryWare AG Florian Engelmann Senior UNIX Systems Engineer Zurlindenstrasse 52a CH-8003 Zürich tel: +41 44 466 60 00 fax: +41 44 466 60 10 mail: mailto:florian.engelmann@everyware.ch web: http://www.everyware.ch