If JOC Cockpit is assigned the Cluster Watch role then fail-over capabilities of JOC Cockpit apply.
If an Agent is assigned the Cluster Watch role (available for earlier releases of JS7 until branch 2.5) then the above explanations suggest that the Agent should Agent should never be run on the hosts that the Primary and Secondary Controller instances are operated on.

If the Cluster Watch is terminated at the same time as a failed Active Controller Instance then no fail-over can occur.
If the Cluster Watch is terminated at the same time as one of the Controller instances then the Controller Cluster cannot start up as this requires operational readiness of the Cluster Watch.
A Cluster Watch that is started after failure of the Active Controller Instance is disqualified from casting its vote as it has no knowledge of whether the Controller instances' journals are in sync.

High Availability Setup

For high availability setup with two server nodes the following distribution of active and standby JS7 products should be applied:

Server 1	Server 2
Active JOC Cockpit Instance	Standby JOC Cockpit Instance
Standby Controller Instance	Active Controller Instance

Cluster Operations

Cluster operations include an automated fail-over and a manual switch-over of the Active Controller Instance.

...