Comment 4 for bug 1460087

tl;dr; canonistack sucks for real work

IIRC canonistack is *way* overcommitted and the fact that the deployment takes 3-4 times longer on canonistack compared with other clouds just reinforces that. It may be that due to severe I/O or CPU contention the agent pingers simply cannot get their message through to the state server before timing out, hence the "agent is lost" message. Also, it may be that the relations are still being started but the deployment is taking a long time to do so. The agent state going to started doesn't necessarily mean that everything is finished being wired up yet.