Minions are not registering because of hostname translation failure

[Martin Matyáš]

After merging of
https://github.com/openstack/magnum/commit/556084ebadca4dca19dd4ce687b1d3f21e58efae

it seems that minions are not registering to kube master anymore for me.
Probable reason is that minions are after that change registering via its hostname and this is not translatable by dns.
Error from minion kubelet reported:

localhost kubelet: E1004 18:21:08.648318 9414 kubelet.go:1131] Unable to construct api.Node object for kubelet: can't get ip address of node k8-mc7nfjpnts-1-kqvsqr55cii7-kube-minion-dptiqjeomb4v: lookup k8-mc7nfjpnts-1-kqvsqr55cii7-kube-minion-dptiqjeomb4v on <my_dns>:53: server misbehaving

After roll-backing/changing the kubelet_args in /etc/kuberentes/kubelet the minion is registered successfully.

Openstack deployment done using kolla for newton.

Not sure what is expected configuration in order to register minions successfully.

[Martin Matyáš (martinx-maty)]

reason: unsupported image used. The only supported image is
https://fedorapeople.org/groups/magnum/fedora-atomic-latest.qcow2

accordingly to
https://github.com/openstack/magnum/blob/master/install-guide/source/launch-instance.rst

[PanFengyun (pan-feng-yun)]

@Martin Matyáš, I run into this issue too. We can get something from the comment of 'https://review.openstack.org/#/c/373417/'.

And I can not understand 'reason: unsupported image used.', what can the image that comes from https://fedorapeople.org/groups/magnum/fedora-atomic-latest.qcow2 do?

Please explain. Thanks.

[PanFengyun (pan-feng-yun)]

How do the image resolve the hostname of minion nodes? Or others can resolve it?

[Martin Matyáš (martinx-maty)]

Magnum takes a VM image to create master and minions VMs. Issue on my Kolla/Magnum deployment was that minion VMs could not resolve their own name as identified by Nova to register to kube-master.
Magnum's customized Fedora Atomic obviously support that resolution in some way. I used bare Centos Atomic and that resolution was not working there. After switching to Magnum's Fedora Atomic, it started working.

I'm not happy much neither with such dependency on specific VM image but it seems that it's a statement of Magnum team that they support/test only with their own customized Fedora Atomic.