This question of how to delete requests that are stuck within vRealize Suite Lifecycle Manager has come up a few times, right from version 1.x to the now current version 2.0 (as of time of writing).
Quite simply, the product GUI does not offer a way to do this however you can delete requests if you are prepared to use the product API and a REST client.
Getting the Request ID
The API call to delete requests from vRSLCM requires the ID of the request you want to delete, so before you dive into the API it’s best to make a note of the request ID(s).
Get an Authentication Token
Before you can do anything with API you need to get an authentication token which can then be used for all other API requests. The authentication token is obtained by connecting to the swagger interface of vRSLCM. The URL is:
Once you are in the swagger interface you need to make sure you have version 1 of the API selected and then expand out the “authorization /login” API call. This will expose the JSON body of the API call and allow you to enter the credentials for your vRSLCM installation.
Once you have added your credentials you can hit the “Try It Out” button to expose the execution options. The “Execute” button will POST the API call.
Upon submission of the “POST” command the API will return a response which is displayed in a window below the “Execute” button. The authentication token required is everything inside the quotation marks for the “token” attribute. In the example below it would be:
eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJ4biIsInN1YiI6Ii9jb3JlL2F1dGh6L3VzZXJzL3ZMQ01BZG1pbiIsImV4cCI6NDY5Njg5ODAzNn0.zRgNa0buMLK3IXrfcK1fENcvSHV_GfPt6REn8EJ6Gz4
REST
The next part requires a REST client (note there is no DELETE option in the swagger interface!). The client could be “curl” on the vRSLCM appliance itself or it could be a GUI client. In this example I will use POSTMAN as it is my goto REST client.
The REST call operation needs to be “DELETE” with the following URL:
https://vRSLCM_FQDN_OR_IP/lcm/api/request/PUT_REQUEST_ID_HERE
The authentication token needs to be provided as a header key:value pair with the key name being “x-xenon-auth-token”.
Executing the request should return a “200 OK” status code which means the request has been accepted successfully. The request in the GUI should now be no longer visible.
If any other status code comes back that is not in the 200 range then check for typos in the URL and make sure the header values are correct. Remember that the authorization token will expire and if this happens you will need to follow the same process to obtain a new token.
Hopefully the delete functionality will make it into the UI for the next vRSLCM version!
vnuggets 