minion resolves hostname and fails - do we need this?

[tofulupo]

yadtshell:

cat target

hosts:
- minion

connection test:

ping minion
PING minion (172.28.128.3) 56(84) bytes of data.
64 bytes from minion (172.28.128.3): icmp_seq=1 ttl=64 time=0.316 ms
64 bytes from minion (172.28.128.3): icmp_seq=2 ttl=64 time=0.519 ms
...

ssh minion
Last login: Tue Oct 21 08:57:59 2014 from 172.28.128.4
[vagrant@minion ~]$

configuration ist ok, now we try to call a yadtshell status:

status

WARNING  no broadcaster config found
WARNING  No module named broadcasterconf
ERROR    'host://minion'
STATUS FAILED
CRITICAL exit code: 1
INFO     For details see: "/tmp/logs/yadtshell/2014-10-21/vagrant/yadtshell.vagrant.2014-10-21--15-12-34.vagrant.000.localhost.status.log"
INFO     The first error was:
                20141021-151235 ERROR twisted.py:201 'host://minion'

we can fix this by setting the hostname on the minion side:

[vagrant@localhost ~]$ sudo hostname minion
[vagrant@localhost ~]$ logout 
Last login: Tue Oct 21 15:12:18 2014 from 10.0.2.2
[vagrant@minion ~]$

Now we call status again and it will work as expected.

Do we need to resolve the hostname on yadtshell and minion side? What do you think :)

[mriehl]

FTR as I told you I think we should be able to deal with a broken hostname on the host itself since the FQDN information is not used anyway, AFAIK.
I'll try to give this a shot on Monday, but I can't promise anything.