123123213weqw opened a new issue, #1459: URL: https://github.com/apache/rocketmq-dashboard/issues/1459
## Bug `ClusterService.updateClusterConfig` initializes both broker result lists as empty. When a resolved cluster has no broker with a usable address, no live update is attempted, but `updateStatus` treats the empty failure list as `SUCCESS`. The service then persists the requested configuration even though no broker applied it. This produces a false-success response and makes the stored configuration diverge from the live cluster. ## Expected behavior A configuration update with no usable broker target should: - return `FAILED` - explain that no broker address is available - avoid persisting the unapplied configuration - record a failed update audit ## Proposed fix Add an explicit failure result when the broker loop has no usable target, and cover the no-broker path with a service regression test. -- 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]
