Comment 4 for bug 1655007

Hi,
I have encountered this before.
The reason of my situation was because after kube_master launching successfully and starting all service that kubernetes needs,
kube_master will start wc-notify.service to notify Heat that it has finished.
What wc-notify.service does is just curl heat api.
But if you configure endpoint api in host name such as http://hostname:8004/v1/%\(tenant_id\)s,
the curl command in wc-notify.service will also use hostname which kube_master doesn't know what it refers to try to curl heat api.
Thus, wc-notify.service will failed and kube_master will stay in CREATE_IN_PROGRESS forever.

There are two solutions now.
First, manually add hostname and ip into /etc/hosts in kube_master.
Second, change the configuration of heat and its endpoint api.

Also, kube_minion encounters the same problem, and it use /var/lib/cloud/instance/scripts/part-014 this script to curl heat api.

Hope my comment helps.