Connectivity issues between the server and agent-kea in Stork demo
I observed an issue whereby I authorize the "agent-kea" machine in our Docker demo but Stork server apparently can't communicate with the agent reporting "Cannot get machine state".
The issue appears to be related to the fact that agent-kea is connected to several Docker networks. Its /etc/hosts file maps agent-kea hostname to multiple IP addresses and depending on which address is first in the /etc/hosts, the name agent-kea may resolve to a wrong one. As a result the agent binds to a wrong address and server can't communicate with it.