Fix: controller: correctly match "node down" events

regression introduced in 2.1.2 by 03ce7376e

The symptom that led to this was that removing a remote node connection
resource would lead to the remote node getting fenced when the connection stop
was not recognized as an expected down event.