You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "Aias00 (via GitHub)" <gi...@apache.org> on 2026/08/10 12:12:20 UTC

[I] [Studio][Bug] Scope NameServer configuration drift checks to the selected instance [rocketmq-dashboard]

Aias00 opened a new issue, #1476:
URL: https://github.com/apache/rocketmq-dashboard/issues/1476

   ## Problem
   
   The NameServer configuration drift flow is cluster-scoped only. `GET /api/nameservers/config-diff` accepts `clusterId` but no `instanceId`; `NameServerConfigDiffService` consequently resolves the cluster through the default runtime context. The web page also lists clusters and queries drift results without an instance selection.
   
   In a multi-instance Studio deployment, the same cluster identifier can be resolved against the wrong managed RocketMQ endpoint, so the displayed drift result is not reliable.
   
   ## Scope
   
   - Add optional/required `instanceId` propagation from the drift page through the web API and controller/service.
   - Resolve the cluster and NameServer admin client using that selected instance endpoint.
   - Preserve existing validation and return an actionable error when the requested cluster is not available for the instance.
   - Add focused backend and frontend regression tests for instance propagation.
   
   ## Out of scope
   
   - NameServer lifecycle operations.
   - Changes to the drift comparison algorithm or safe-key catalog.
   
   ## Track
   
   Track 1 / ARCH-01 multi-instance runtime management.


-- 
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: commits-unsubscribe@rocketmq.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Studio][Bug] Scope NameServer configuration drift checks to the selected instance [rocketmq-dashboard]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #1476:
URL: https://github.com/apache/rocketmq-dashboard/issues/1476#issuecomment-5389252239

   This issue has been automatically closed because there has been no activity for 7 days. If you believe this issue is still relevant, please reopen it with updated information.


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Studio][Bug] Scope NameServer configuration drift checks to the selected instance [rocketmq-dashboard]

Posted by "Aias00 (via GitHub)" <gi...@apache.org>.
Aias00 commented on issue #1476:
URL: https://github.com/apache/rocketmq-dashboard/issues/1476#issuecomment-5248254805

   The issue is already addressed by open PR #1477. A duplicate PR created during a later baseline audit has been closed.


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Studio][Bug] Scope NameServer configuration drift checks to the selected instance [rocketmq-dashboard]

Posted by "RockteMQ-AI (via GitHub)" <gi...@apache.org>.
RockteMQ-AI commented on issue #1476:
URL: https://github.com/apache/rocketmq-dashboard/issues/1476#issuecomment-5240688914

   **Issue Evaluation**
   
   Category: `bug` | Status: **Confirmed**
   
   The issue is valid. NameServer config drift checks are currently cluster-scoped without instance context, which means they always resolve against the default runtime context. When multiple instances are configured, this produces incorrect drift results.
   
   **Root Cause:** `NameServerConfigDiffService` does not accept `instanceId`; the API endpoint and UI also lack instance selection.
   **Impact:** Drift detection results are wrong when non-default instances are in use.
   **Severity:** medium
   
   ---
   *Automated evaluation by RockteMQ-AI*


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Studio][Bug] Scope NameServer configuration drift checks to the selected instance [rocketmq-dashboard]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #1476: [Studio][Bug] Scope NameServer configuration drift checks to the selected instance
URL: https://github.com/apache/rocketmq-dashboard/issues/1476


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org