Issue

• I cannot connect to Client controller(s) and I am redirected to a blank page at $JENKINS_URL/securityRealm/finishLogin?code=xxxxxxx
• Operations Center logs show WARNINGS:

2016-02-08 15:53:51.116+0000 [id=175]	WARNING	c.c.o.s.m.h.MasterHealthCheckConditionSource$MasterHealthCheckCondition#getFailingChecks: Error getting master health checks from "my-controller"
java.util.concurrent.ExecutionException: java.lang.NoSuchMethodError: jenkins.metrics.api.Metrics$HealthChecker.getHealthCheckResults()Ljava/util/Map;
	at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289)
	at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276)
	at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111)
	at com.google.common.util.concurrent.Futures$ChainingListenableFuture.get(Futures.java:635)
	at com.cloudbees.opscenter.server.metrics.RemoteDataSnapshot.getSnapshot(RemoteDataSnapshot.java:98)
	at com.cloudbees.opscenter.server.metrics.health.MasterHealthCheckConditionSource$MasterHealthCheckCondition.getFailingChecks(MasterHealthCheckConditionSource.java:153)
	at com.cloudbees.opscenter.server.metrics.health.MasterHealthCheckConditionSource$MasterHealthCheckCondition.isActive(MasterHealthCheckConditionSource.java:102)
	at com.cloudbees.jenkins.plugin.metrics.views.Alerter$Condition.checkState(Alerter.java:650)
	at com.cloudbees.jenkins.plugin.metrics.views.Alerter$PeriodicWorkImpl.execute(Alerter.java:977)
	at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:53)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NoSuchMethodError: jenkins.metrics.api.Metrics$HealthChecker.getHealthCheckResults()Ljava/util/Map;

Environment

• CloudBees Jenkins Enterprise
• Jenkins
• Operations Center Monitoring Plugin < 1.8.2
• Metrics <= 3.1.2.3

Related Issues

Resolution

There was a breaking API change in metrics 3.1.2.3 that breaks communication between CJOC and CM, preventing attachment or SSO to work. The issue has been fixed in Metrics 3.1.2.4.

To fix this, upgrade the Metrics Plugin to version 3.1.2.4 or later.

(Note: Operations Center Monitoring Plugin 1.8.3 has been released to depend on the fixed version 3.1.2.5 of the Metrics Plugin)