If you have an account on the vRealize Suite Lifecycle Manager server and you have remote server access, you can check for patches online and use the API to download the patch files that you want.

This procedure shows how to use the API to download a patch from the CDN directly into vRealize Suite Lifecycle Manager.

Prerequisites

Procedure

  1. Check for the latest patch binaries that are available online in the Content Delivery Network (CDN). 
    curl -X POST \
  '$url/lcm/lcops/api/v2/settings/patch-binaries' \
  -H 'Authorization: Basic YWRtaW5AbG9jYWw6VGhpc0lzUGFzc3dvcmQ=' \
  -H 'Content-Type: application/json' | jq "."
    The request triggers the API. The response shows the request ID. 
    {
    "requestId":"asdf1234a-6e1f-4772-a97d-af300ad9999c"
}
  2. Assign the request ID variable. 
    requestId = "asdf1234a-6e1f-4772-a97d-af300ad9999c"
  3. Track your request. 
    curl -X GET '$url /lcm/request/api/v2/requests/$requestId' -H 'Authorization: Basic YWRtaW5AbG9jYWw6VGhpc0lzUGFzc3dvcmQ=' | jq "."
    After completion, the list of available patch binaries in vRealize Suite Lifecycle Manager refreshes. 
    ...
},
  "outputMap": {},
  "state": "COMPLETED",
  "executionId": "94301f3c-20cc-47a1-90ec-130635edb7d1",
...
  4. List the patch binaries. 
    curl -X GET \
  '$url/lcm/lcops/api/v2/settings/patch-binaries' \
  -H 'Authorization: Basic YWRtaW5AbG9jYWw6VGhpc0lzUGFzc3dvcmQ=' \
  -H 'Content-Type: application/json' | jq "."
    Examine the response to find the patch that you want. A snippet of the response shows the patch ID, product ID, and product version of the patch binary and "patchDownloadStatus": "NOT AVAILABLE", so you must download that patch. 
    ...    
      "patchInfo": {
      "name": "vRealize Automation, version 8.0.1.7526",
      "summary": "vRSLCM wrapped vRealize Automation, version 8.0.1.7526 Patch4",
      "description": "vRSLCM wrapped vRealize Automation, version 8.0.1.7526 Patch4",
      "kbUrl": "https://kb.vmware.com/s/article/76805",
      "eulaFile": null,
      "category": "bugfix",
      "urgency": "critical",
      "releaseType": "patch",
      "releaseDate": 1590039695062,
      "additionaInfo": {}
    },
    "metadataId": "vrlcm-vra-8.0.1-8.0.1.7526",
    "metadataVersion": "1",
    "patchId": "c0a13037-3906-43b8-8eb3-7f73e76c3ea8",
    "patchBundleCreationDate": 1590039921132,
    "selfPatch": false,
    "product": {
      "productId": "vra",
      "productName": "vRealize Automation",
      "productVersion": "8.0.1",
      "supportedVersions": [
        "8.0.1"
      ],
   ...
   },
   "patchFileName": "vrlcm-vra-8.0.1.7526.patch",
   "patchSize": 6073307467,
   "patchSha256sum": "9fed5f30f7c2967cdaac3b914a49b3aaec6520c4er422b90cd5703f9794e5",
   "patchRunningcounter": 1,
   "patchStatus": "ACTIVE",
   "patchDownloadStatus": "NOT AVAILABLE",
   "extract": false,
   "patchCounter": "4"
...
  5. Download the patch binary into vRealize Suite Lifecycle Manager. 
    curl -X POST \
  '$url/lcm/lcops/api/v2/settings/patch-binaries/download' \
  -H 'Authorization: Basic YWRtaW5AbG9jYWw6VGhpc0lzUGFzc3dvcmQ=' \
  -H 'Content-Type: application/json' \
  -d '{
    "patchId": "c0a13037-3906-43b8-8eb3-7f73e76c3ea8",
    "productId": "vra"
    "productVersion": "8.0.1"
  }' | jq "."
    The request triggers the API. The response shows the request ID. 
    {
    "requestId":"1dac194a-6e1f-4772-a97d-af300ad5086c"
}
  6. Assign the request ID variable. 
    requestId = "1dac194a-6e1f-4772-a97d-af300ad5086c"
  7. Track your request. 
    curl -X GET '$url /lcm/request/api/v2/requests/$requestId' -H 'Authorization: Basic YWRtaW5AbG9jYWw6VGhpc0lzUGFzc3dvcmQ=' | jq "."
    The request might take some time. At completion, the patch is downloaded. 
    ...
},
  "outputMap": {},
  "state": "COMPLETED",
  "executionId": "61274f3c-20cc-47a1-90ec-130635edb7d1",
...

What to do next

Apply the product patch. See Apply a product patch.