Open Stack

Can you talk to the Heat API from your master node?


On 20/02/19 6:43 AM, Giuseppe Sannino wrote:
> Hi all...again,
> I managed to get over the previous issue by "not disabling" the TLS in
> the cluster template.
> From the cloud-init-output.log I see:
> Cloud-init v. 17.1 running 'modules:final' at Tue, 19 Feb 2019
> 17:03:53 +0000. Up 38.08 seconds.
> Cloud-init v. 17.1 finished at Tue, 19 Feb 2019 17:13:22 +0000.
> Datasource DataSourceEc2.  Up 607.13 seconds
>
> But the cluster creation keeps on failing.
> From the journalctl -f I see a possible issue:
> Feb 19 17:42:38 kube-cluster-tls-6hezqcq4ien3-master-0.novalocal
> runc[2723]: publicURL endpoint for orchestration service in null
> region not found
> Feb 19 17:42:38 kube-cluster-tls-6hezqcq4ien3-master-0.novalocal
> runc[2723]: Source [heat] Unavailable.
> Feb 19 17:42:38 kube-cluster-tls-6hezqcq4ien3-master-0.novalocal
> runc[2723]: /var/lib/os-collect-config/local-data not found. Skipping
>
> anyone familiar with this problem ?
>
> Thanks as usual.
> /Giuseppe
>
>
>
>
>
>
>
> On Tue, 19 Feb 2019 at 17:35, Giuseppe Sannino
> <km.giuseppesannino at gmail.com <mailto:km.giuseppesannino at gmail.com>>
> wrote:
>
>     Hi all,
>     need an help.
>     I deployed an AIO via Kolla on a baremetal node. Here some
>     information about the deployment:
>     ---------------
>     kolla-ansible: 7.0.1
>     openstack_release: Rocky
>     kolla_base_distro: centos
>     kolla_install_type: source
>     TLS: disabled
>     ---------------  
>
>
>     VMs spawn without issue but I can't make the "Kubernetes cluster
>     creation" successfully. It fails due to "Time out"
>
>     I managed to log into Kuber Master and from the
>     cloud-init-output.log I can see:
>     + echo 'Waiting for Kubernetes API...'
>     Waiting for Kubernetes API...
>     ++ curl --silent http://127.0.0.1:8080/healthz
>     + '[' ok = '' ']'
>     + sleep 5
>
>
>     Checking via systemctl and journalctl I see:
>     [fedora at kube-clsuter-qamdealetlbi-master-0 log]$ systemctl status
>     kube-apiserver
>     ● kube-apiserver.service - kubernetes-apiserver
>        Loaded: loaded (/etc/systemd/system/kube-apiserver.service;
>     enabled; vendor preset: disabled)
>        Active: failed (Result: exit-code) since Tue 2019-02-19
>     15:31:41 UTC; 45min ago
>       Process: 3796 ExecStart=/usr/bin/runc --systemd-cgroup run
>     kube-apiserver (code=exited, status=1/FAILURE)
>      Main PID: 3796 (code=exited, status=1/FAILURE)
>
>     Feb 19 15:31:40 kube-clsuter-qamdealetlbi-master-0.novalocal
>     systemd[1]: kube-apiserver.service: Main process exited,
>     code=exited, status=1/FAILURE
>     Feb 19 15:31:40 kube-clsuter-qamdealetlbi-master-0.novalocal
>     systemd[1]: kube-apiserver.service: Failed with result 'exit-code'.
>     Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal
>     systemd[1]: kube-apiserver.service: Service RestartSec=100ms
>     expired, scheduling restart.
>     Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal
>     systemd[1]: kube-apiserver.service: Scheduled restart job, restart
>     counter is at 6.
>     Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal
>     systemd[1]: Stopped kubernetes-apiserver.
>     Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal
>     systemd[1]: kube-apiserver.service: Start request repeated too
>     quickly.
>     Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal
>     systemd[1]: kube-apiserver.service: Failed with result 'exit-code'.
>     Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal
>     systemd[1]: Failed to start kubernetes-apiserver.
>
>     [fedora at kube-clsuter-qamdealetlbi-master-0 log]$ sudo journalctl
>     -u kube-apiserver
>     -- Logs begin at Tue 2019-02-19 15:21:36 UTC, end at Tue
>     2019-02-19 16:17:00 UTC. --
>     Feb 19 15:31:33 kube-clsuter-qamdealetlbi-master-0.novalocal
>     systemd[1]: Started kubernetes-apiserver.
>     Feb 19 15:31:34 kube-clsuter-qamdealetlbi-master-0.novalocal
>     runc[2794]: Flag --insecure-bind-address has been deprecated, This
>     flag will be removed in a future version.
>     Feb 19 15:31:34 kube-clsuter-qamdealetlbi-master-0.novalocal
>     runc[2794]: Flag --insecure-port has been deprecated, This flag
>     will be removed in a future version.
>     Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal
>     runc[2794]: Error: error creating self-signed certificates: open
>     /var/run/kubernetes/apiserver.crt: permission denied
>     :
>     :
>     :
>     Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal
>     runc[2794]: error: error creating self-signed certificates: open
>     /var/run/kubernetes/apiserver.crt: permission denied
>     Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal
>     systemd[1]: kube-apiserver.service: Main process exited,
>     code=exited, status=1/FAILURE
>     Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal
>     systemd[1]: kube-apiserver.service: Failed with result 'exit-code'.
>     Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal
>     systemd[1]: kube-apiserver.service: Service RestartSec=100ms
>     expired, scheduling restart.
>     Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal
>     systemd[1]: kube-apiserver.service: Scheduled restart job, restart
>     counter is at 1.
>
>
>     May I ask for an help on this ?
>
>     Many thanks
>     /Giuseppe
>
>
>
>
-- 
Cheers & Best regards,
Feilong Wang (王飞龙)
--------------------------------------------------------------------------
Senior Cloud Software Engineer
Tel: +64-48032246
Email: flwang at catalyst.net.nz
Catalyst IT Limited
Level 6, Catalyst House, 150 Willis Street, Wellington
-------------------------------------------------------------------------- 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190220/bec6d423/attachment-0001.html>