When pooling ClusterMonitors and SearchClusters you will add a cluster every time there is a reconfig.

As nothing will purge them, you both keep stuff alive forever and end up with more clusters that you have.
Hence the magic for not removing vipstatus when there are multiple clusters kick in preventing nodes being taken OOR.
Now it is using the ComponentId for identifying a cluster.

1 files changed, 3 insertions, 3 deletions

diff --git a/container-core/src/test/java/com/yahoo/container/handler/VipStatusTestCase.java b/container-core/src/test/java/com/yahoo/container/handler/VipStatusTestCase.java
index e54f968f41d..4c1c1622140 100644
--- a/container-core/src/test/java/com/yahoo/container/handler/VipStatusTestCase.java
+++ b/container-core/src/test/java/com/yahoo/container/handler/VipStatusTestCase.java
@@ -18,9 +18,9 @@ public class VipStatusTestCase {
         clustersStatus.setContainerHasClusters(true);
         VipStatus v = new VipStatus(clustersStatus);
 
-        Object cluster1 = new Object();
-        Object cluster2 = new Object();
-        Object cluster3 = new Object();
+        String cluster1 = new String("a");
+        String cluster2 = new String("b");
+        String cluster3 = new String("c");
 
         // initial state
         assertFalse(v.isInRotation());