Aias00 opened a new issue, #917: URL: https://github.com/apache/rocketmq-dashboard/issues/917
### Description In mock mode, `updateNameServer()` can rename a NameServer to an address that already exists in the same cluster. Location: - `web/src/services/clusterService.ts:211` `createNameServer()` rejects duplicate addresses, but the edit path assigns `newAddr` directly without checking the rest of the cluster's NameServer list. This can create duplicate endpoint rows inside one cluster. ### Impact After a duplicate address is created, later restart/delete/edit actions become ambiguous because they identify NameServers by address. The mock control-plane view can then diverge from the uniqueness rule already enforced during creation and from the expected backend contract. ### Suggested fix Before assigning `newAddr`, reject it when another NameServer in the same cluster already has that address. Add regression coverage for the duplicate edit path and for keeping the original address unchanged after rejection. -- 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]
