Open Stack

Hi,
I haven’t had the chance to play with magnum too much yet but could it  
be an issue with the image? I had an issue with Octavia when I first  
used an image which didn’t work as expected. Maybe check all relevant  
log files inside the VMs, maybe cloud-init didn’t work as expected.

Zitat von Chris DiLorenzo <cdilorenzo at gmail.com>:

> Hello,
>
> I'm trying to deploy a kubernetes cluster using CoreOS 33.   I have
> also tried with CoreOS 35/. 1 master, 1 worker.  Ths VMs are deploying
> without issue.  However, the stack is timing out on kube_cluster_deploy.
> It appears the kubernetes API isn't running:
>
> [root at tes-001-pkjawhk66slm-master-0 log]# podman ps
> CONTAINER ID  IMAGE
>    COMMAND               CREATED         STATUS             PORTS   NAMES
> a08cbea59a57
> docker.io/openstackmagnum/heat-container-agent:wallaby-stable-1
> /usr/bin/start-he...
>  21 minutes ago  Up 21 minutes ago          heat-container-agent
>
> [root at tes-001-pkjawhk66slm-master-0 log]# ss -ln | grep 8080 -> nothing
>
> [root at tes-001-pkjawhk66slm-master-0 heat-config-script]# tail -f
> 8d8fa128-bca4-485e-946f-90732ebb4cf0-tes-001-pkjawhk66slm-kube_cluster_config-bwkfqwjxzk36.log
> + sleep 5
> ++ kubectl get --raw=/healthz
> The connection to the server localhost:8080 was refused - did you specify
> the right host or port?
> + '[' ok = '' ']'
> + sleep 5
> ++ kubectl get --raw=/healthz
> The connection to the server localhost:8080 was refused - did you specify
> the right host or port?
> + '[' ok = '' ']'
> + sleep 5
> ++ kubectl get --raw=/healthz
>
> Not sure where else to look.
>
> Thanks
> Chris