Background: When an agent (e.g. "agent-1") reboots, the agentId might change under certain circumstances (to, e.g. "agent-2"). If that agent's state contained dynamic reservations and persistent volumes, Marathon would not update the AgentInfo when launching a new instance based on these. As a result, the instance as reported via the Marathon API would still say "agent-1", when the actual task and the persistent volume would run on "agent-2" – the volume and task appear to be on different nodes.
Further, if the hosts hostname changes on re
Details on on the customer JIRA COPS-580