don't depend on goroutine to avoid deadlock.

Code calls a function that has a lock that is held around that call. It
didn't deadlock as the function call was calling it as a goroutine, so
it would kick it off and then unlock which would let the goroutine then
get the lock. Found this when I temporarily removed to goroutine to
force sequential exectution for debugging. Didn't like this so I cleaned
things up such that the code doesn't rely on the goroutine to avoid the
deadlock.

coordinate.go

@@ -79,11 +79,12 @@ func (a *Agent) updateCoords(nodeCh nodeChannel) {
 		a.inflightLock.Lock()
 		if _, ok := a.inflightPings[node.Node]; ok {
 			a.logger.Warn("Error pinging node, last request still outstanding", "node", node.Node, "nodeId", node.ID)
+			a.inflightLock.Unlock()
 		} else {
 			a.inflightPings[node.Node] = struct{}{}
+			a.inflightLock.Unlock()
 			go a.runNodePing(node)
 		}
-		a.inflightLock.Unlock()
 	}
 }