Aias00 opened a new issue, #1663: URL: https://github.com/apache/rocketmq-dashboard/issues/1663
## Problem `RocketMQClusterProvider.refreshClusterDetail()` catches every Admin exception and returns `null`. `ClusterService.resolveCluster()` interprets `null` as a missing live cluster and falls back to persisted metadata. A failed NameServer refresh can therefore cause a configuration update to operate on stale persisted Broker targets or report a misleading 404. ## Expected behavior - Keep `null` only for a genuinely absent cluster or no configured endpoint. - Convert Admin/NameServer refresh failures into a structured 502 so callers do not fall back to stale metadata. - Add provider and service regression coverage. ## Track Track 1 / cluster runtime operations. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
