Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 311
    • Issues 311
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 27
    • Merge requests 27
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • storkstork
  • Issues
  • #517
Closed
Open
Issue created Mar 26, 2021 by Marcin Siodelski@marcinMaintainer

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.

Assignee
Assign to
Time tracking