Broker IDs are reported as negative

[actgardner]

trafficstars

We're running cruise-control 2.5.83 against MSK 2.8.2 with the stock Prometheus config and the AWS_MSK_IAM sasl config. The set of broker IDs is [1,2,3] and for some reason Cruise Control is treating them as [-1,-,2-3]:

17:39:54.366 [qtp2122267901-57] ERROR com.linkedin.kafka.cruisecontrol.servlet.response.ClusterBrokerState - Getting log dir information for broker -1 timed out.
17:40:04.370 [qtp2122267901-57] ERROR com.linkedin.kafka.cruisecontrol.servlet.response.ClusterBrokerState - Getting log dir information for broker -2 timed out.
17:40:14.370 [qtp2122267901-57] ERROR com.linkedin.kafka.cruisecontrol.servlet.response.ClusterBrokerState - Getting log dir information for broker -3 timed out.
17:40:54.526 [MetricFetcher-0] ERROR com.linkedin.kafka.cruisecontrol.monitor.sampling.MetricFetcher - Received exception.
java.lang.IllegalArgumentException: The broker id(-1) should be non-negative.
	at com.linkedin.kafka.cruisecontrol.config.BrokerCapacityConfigFileResolver.capacityForBroker(BrokerCapacityConfigFileResolver.java:187) ~[cruise-control.jar:?]
	at com.linkedin.kafka.cruisecontrol.monitor.sampling.CruiseControlMetricsProcessor.lambda$updateCachedNumCoresByBroker$1(CruiseControlMetricsProcessor.java:86) ~[cruise-control.jar:?]
	at java.util.HashMap.computeIfAbsent(HashMap.java:1134) ~[?:?]
	at com.linkedin.kafka.cruisecontrol.monitor.sampling.CruiseControlMetricsProcessor.updateCachedNumCoresByBroker(CruiseControlMetricsProcessor.java:78) ~[cruise-control.jar:?]
	at com.linkedin.kafka.cruisecontrol.monitor.sampling.CruiseControlMetricsProcessor.process(CruiseControlMetricsProcessor.java:117) ~[cruise-control.jar:?]
	at com.linkedin.kafka.cruisecontrol.monitor.sampling.AbstractMetricSampler.getSamples(AbstractMetricSampler.java:53) ~[cruise-control.jar:?]
	at com.linkedin.kafka.cruisecontrol.monitor.sampling.MetricFetcher.fetchSamples(MetricFetcher.java:160) ~[cruise-control.jar:?]
	at com.linkedin.kafka.cruisecontrol.monitor.sampling.MetricFetcher.fetchMetricsForAssignedPartitions(MetricFetcher.java:129) ~[cruise-control.jar:?]
	at com.linkedin.kafka.cruisecontrol.monitor.sampling.MetricFetcher.call(MetricFetcher.java:110) [cruise-control.jar:?]
	at com.linkedin.kafka.cruisecontrol.monitor.sampling.MetricFetcher.call(MetricFetcher.java:25) [cruise-control.jar:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
	at java.lang.Thread.run(Thread.java:829) [?:?]