You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by "adietrich-ussignal (via GitHub)" <gi...@apache.org> on 2025/04/08 20:49:02 UTC
[I] managementserverid value inconsistency in shutdown APIs [cloudstack]
adietrich-ussignal opened a new issue, #10669:
URL: https://github.com/apache/cloudstack/issues/10669
### 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.
```
prepare forshutdown managementserverid=0b2faa01-706f-4f37-82ff-3e5e8f0971f8
{
"prepareforshutdown": {
"managementserverid": 1,
"pendingjobscount": 0,
"readyforshutdown": true,
"shutdowntriggered": true
}
}
```
### versions
ACS 4.19.2.0
CMK 6.4.0
### The steps to reproduce the bug
1. `prepare forshutdown managementserverid=<UUID of management server>`
2. Observe return values.
...
### 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`.
--
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@cloudstack.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] managementserverid value inconsistency in shutdown APIs [cloudstack]
Posted by "adietrich-ussignal (via GitHub)" <gi...@apache.org>.
adietrich-ussignal commented on issue #10669:
URL: https://github.com/apache/cloudstack/issues/10669#issuecomment-2796938458
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.
--
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@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] managementserverid value inconsistency in shutdown APIs [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #10669:
URL: https://github.com/apache/cloudstack/issues/10669#issuecomment-2796898603
@adietrich-ussignal , does @sureshanaparti 's remark answer your concerns ? i.e. can we close this issue?
--
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@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] managementserverid value inconsistency in shutdown APIs [cloudstack]
Posted by "rohityadavcloud (via GitHub)" <gi...@apache.org>.
rohityadavcloud commented on issue #10669:
URL: https://github.com/apache/cloudstack/issues/10669#issuecomment-2804236571
Raised a PR to fix the use of internal DB ID in the response - https://github.com/apache/cloudstack/pull/10717
--
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@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] managementserverid value inconsistency in shutdown APIs [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland closed issue #10669: managementserverid value inconsistency in shutdown APIs
URL: https://github.com/apache/cloudstack/issues/10669
--
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@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] managementserverid value inconsistency in shutdown APIs [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #10669:
URL: https://github.com/apache/cloudstack/issues/10669#issuecomment-2829721957
fixed in #10717
--
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@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] managementserverid value inconsistency in shutdown APIs [cloudstack]
Posted by "sureshanaparti (via GitHub)" <gi...@apache.org>.
sureshanaparti commented on issue #10669:
URL: https://github.com/apache/cloudstack/issues/10669#issuecomment-2796828278
these response are addressed in some shutdown improvements here: https://github.com/apache/cloudstack/pull/9854
--
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@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] managementserverid value inconsistency in shutdown APIs [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #10669:
URL: https://github.com/apache/cloudstack/issues/10669#issuecomment-2800732866
> 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.
--
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@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org