-
Notifications
You must be signed in to change notification settings - Fork 1.2k
managementserverid value inconsistency in shutdown APIs #10669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@adietrich-ussignal these responses are updated (with UUID of the management server) in some shutdown improvements here: #9854 (will be included in 4.21 release). |
@adietrich-ussignal , does @sureshanaparti 's remark answer your concerns ? i.e. can we close this issue? |
It seems odd this was tagged as a feature when its inconsistent with many of the other API operations in the platform. Based on my understanding of the PR, it looks like the msid is being set to the UUID and not the database ID. |
@adietrich-ussignal , it is actually an improvement, but it seems github doesn't know this type of issue. We could as well have tagged it as a "task". In the past a lot of API would return DB ID as id and a separate field uuid. historic "feature" or artifact if you will. It may feel as a bug to you , I appreciate that, but it was actually implemented on purpose. |
Fixes apache#10669 Creates shutdown response to use management server UUID than internal DB ID. Signed-off-by: Rohit Yadav <[email protected]>
Raised a PR to fix the use of internal DB ID in the response - #10717 |
fixed in #10717 |
problem
When using the shutdown APIs (
prepareForShutdown
,triggerShutdown
, etc.) the management server ID is required, however, the return value appears to be the database ID.versions
ACS 4.19.2.0
CMK 6.4.0
The steps to reproduce the bug
prepare forshutdown managementserverid=<UUID of management server>
...
What to do about it?
To align with other API calls, it would be more valuable to pass the UUID of the management server in the return value for
managementserverid
.The text was updated successfully, but these errors were encountered: