GitHub user waiphyodev added a comment to the discussion: 401 error in
cloudstack createUser rest api
My bad! Thanks for all your helps.
(error) params => get signature for params => encode signature
(success) params => encode params => get signature for encoded params => encode
signature
``
GitHub user boring-cyborg[bot] added a comment to the discussion: 401 error in
cloudstack createUser rest api
Thanks for opening your first issue here! Be sure to follow the issue template!
GitHub link:
https://github.com/apache/cloudstack/discussions/11146#discussioncomment-13669109
T
GitHub user waiphyodev added a comment to the discussion: 401 error in
cloudstack createUser rest api
Thanks for reply.
Yes, it does have required permissions to do request because I do the same
process via CloudStack dashboard with the same account and it is fine.
This is happening only via A
GitHub user waiphyodev added a comment to the discussion: 401 error in
cloudstack createUser rest api
GET (401 error)
`http://host/client/api?apikey=&command=createAccount&domainid=&email=userthree%40mail.com&firstname=User&lastname=Three&password=password&response=json&roleid=&username=userthr
GitHub user weizhouapache added a comment to the discussion: 401 error in
cloudstack createUser rest api
> GET (401 error)
> `http://host/client/api?apikey=&command=createAccount&domainid=&email=userthree%40mail.com&firstname=User&lastname=Three&password=password&response=json&roleid=&username
GitHub user DaanHoogland added a comment to the discussion: 401 error in
cloudstack createUser rest api
@waiphyodev , I suppose you left out the signature on purpose and did include
it in your attempts to create a user.
there is “account” between the URL and the rest of the parameters,
my try
GitHub user DaanHoogland added a comment to the discussion: Not able to delete
service offering from UI or API
converting to discuss item as the resolution would only be the workaround.
GitHub link:
https://github.com/apache/cloudstack/discussions/10498#discussioncomment-12386913
This i
GitHub user DaanHoogland added a comment to the discussion: Not able to delete
service offering from UI or API
@vishesh92 , we could implement the delete API in such a way that it does a
check if th offering is used and if it is it 'only' disables it. If not used it
would actually mark it as
GitHub user li-liwen added a comment to the discussion: Not able to delete
service offering from UI or API
I got it. Thanks for helping. I would just leave them inactive for now.
GitHub link:
https://github.com/apache/cloudstack/discussions/10498#discussioncomment-12386910
This is an au
GitHub user li-liwen added a comment to the discussion: Not able to delete
service offering from UI or API
@DaanHoogland Yes, I'm able to call the deleteServiceOffering API using cmk.
But the API just makes the offering inactive instead of deleting it. I think
this is probably the intended be
GitHub user vishesh92 added a comment to the discussion: Not able to delete
service offering from UI or API
> I think for now setting the `removed` field to `now()` is the best workaround.
Yes. This should work. But it can cause issues with operations for existing
VMs. The user will have to e
GitHub user rohityadavcloud added a comment to the discussion: Not able to
delete service offering from UI or API
Inactive as a workaround is okay - if historically there never was a way to
delete offerings in the UI or deleteServiceOffering API didn't work, let's
close this.
GitHub link:
h
GitHub user DaanHoogland added a comment to the discussion: Not able to delete
service offering from UI or API
I think for now setting the `removed` field to `now()` is the best workaround.
GitHub link:
https://github.com/apache/cloudstack/discussions/10498#discussioncomment-12386908
Th
GitHub user DaanHoogland added a comment to the discussion: Not able to delete
service offering from UI or API
@li-liwen If I read the changes in #8821 correctly it only changes the
behaviour of the updateOffering commands. So you should still be
able to call the deleteServiceOffering API, fo
GitHub user weizhouapache added a comment to the discussion: Not able to delete
service offering from UI or API
this looks related to #8821
cc @vishesh92
GitHub link:
https://github.com/apache/cloudstack/discussions/10498#discussioncomment-12386901
This is an automatically sent email
GitHub user harikrishna-patnala added a comment to the discussion: Not able to
delete service offering from UI or API
@rohityadavcloud I don't find any API which marks the service offering's
removed column. deleteServiceOffering API and updateServiceOffering (using
state parameter) API are up
GitHub user li-liwen added a comment to the discussion: Not able to delete
service offering from UI or API
Hi, I am using CloudStack 4.20. I encountered the same issue. According to the
author of #8821, the delete command in the API will no longer actually delete
the offering. Instead, it wil
GitHub user DaanHoogland added a comment to the discussion: Not able to delete
service offering from UI or API
@rohityadavcloud can you expand on this? #8821 claims to fix this in 4.19.1,
but you reported this in this version.
GitHub link:
https://github.com/apache/cloudstack/discussions/104
GitHub user vishesh92 added a comment to the discussion: Not able to delete
service offering from UI or API
it's been some time, but AFAIR it's kind of complicated and would require a lot
of changes.
GitHub link:
https://github.com/apache/cloudstack/discussions/10498#discussioncomment-123869
No, there is no way to spawn multiple instances with a single
deployVirtualMachine API call, however, you can easily create a loop in
whatever language you are using to provision an arbitrary number of VMs
at once.
Ref:
https://cloudstack.apache.org/docs/api/apidocs-4.2/user/deployVirtualMachine.h
Hello Guys, I have cloudstack 4.2.1 and I use API for deploy VM, exist command
for deploy many (3,4, o 5) vm's in the same command
Thanks
Cordialmente / Best regards,
Yesid Mora | Orchestration Engineer | O4IT
PBX:+57 (1) 423-5460 Ext 251 | Cel: 3124509565
| Oficina 202 |
www.o4
21 matches
Mail list logo
