VMware Cloud Community
spride
Enthusiast
Enthusiast
Jump to solution

CloudClient 3.3.1: vra provisioneditem action execute broken?

Apologies in advanced if this is not the correct forum for CloudClient issues/bugs.

Version: cloudclient-3.3.1-2966416

I downloaded CloudClient 3.3.1 yesterday, and was trying to run the "vra provisioneditem action execute" command, but it kept giving me an error that the '--id' parameter was not a valid UUID.  I ran this before using the VM name as the id with v3.1.0 and never had a problem.  Even the help says the 'id' parameter can be an "ID or name".  Here is the error:

Version : 3.3.1

*Tip* : You can hit tab to move through commands and arguments

Welcome to the VMware CloudClient

CloudClient>vra provisioneditem action execute --id "mytestvm" --action "Power Off"

Error: The input provided resulted in a REST exception: Invalid UUID string: mytestvm. The HTTP status is 400 - BAD_REQUEST.

Using cloudclient-3.1.0-2375258:

Version : 3.1.0

*Tip* : You can hit tab to move through commands and arguments

Welcome to the VMware CloudClient

CloudClient>vra provisioneditem action execute --id "mytestvm" --action "Power Off"

Success.

0 Kudos
1 Solution

Accepted Solutions
SeanKohler
Expert
Expert
Jump to solution

Per support there is a maintenance release coming out soon (next month or so) that will fix this issue.

We would need to leverage workarounds to supply UUID instead of name for now.

View solution in original post

0 Kudos
5 Replies
SeanKohler
Expert
Expert
Jump to solution

Trying to duplicate your issue...

0 Kudos
SeanKohler
Expert
Expert
Jump to solution


Yeah.  The Name should work per the online help, and it indeed does not.

cloudclient.jpg

Probably the best bet is to open a service ticket with VMware.  CloudClient is a "supported" application.

I suppose the workaround would be to get the ID from the machine before making the call.

0 Kudos
SeanKohler
Expert
Expert
Jump to solution

Per support there is a maintenance release coming out soon (next month or so) that will fix this issue.

We would need to leverage workarounds to supply UUID instead of name for now.

0 Kudos
spride
Enthusiast
Enthusiast
Jump to solution

Thanks Sean.  For now I downgraded to 3.1 until a new update comes out.

0 Kudos
SeanKohler
Expert
Expert
Jump to solution

Oh good idea!

0 Kudos