If a change occurs in a vRealize Suite product following a configuration drift, you can get a remediation report.

Prerequisites

Satisfy the following conditions before performing the tasks for this use case.
  • Use POST /lcm/api/v1/login to log in to vRealize Suite Lifecycle Manager.
  • Verify that you have a valid authentication token that matches your login credentials. See Request an Authentication Token.

Procedure

  1. Retrieve a remediation report.
    curl -X GET "https://LCM-HostName/lcm/api/v1/remediation" -H "accept: application/json" -H "x-xenon-auth-token: $token"
    The following input is optional:
    • environment = environment name
    • requestId = request ID
    • product = product type
  2. To identify any changes, examine the response. A remediation report is only available if a configuration drift in the vRealize Suite environment has occurred.
    In the following code snippet from a response body, "driftedProducts": ["764b17cc6f57875569146ef4e5a2"] shows a change in vRealize Automation version 7.3.
    {
      "updateTime": "2018-06-28T11:09:28.632Z[Etc/UTC]",
      "isRetry": false,
      "productType": "vra-7.3.0",
      "productNames": [
        "764b17cc6f57875569146ef4e5a2"
      ],
      "nodes": [
        {
        ...
        },
        {
          "type": "vRealize Automation Cafe Virtual Machine",
          "nodeIdField": "vra2-va.sqa.local",
          "driftedProducts": [
            "764b17cc6f57875569146ef4e5a2"
          ],
          "categories": [
            {
            ...
            },
            {
              "categoryType": "vRealize Automation VM Network Information",
              "categoryId": "10.158.129.11",
              "isRetry": false,
              "isRemediationEnabled": true,
              "driftedProducts": [
                "764b17cc6f57875569146ef4e5a2"
              ],
              "property": [
                {
                  "name": "ipaddress",
                  "isRemediationEnabled": false,
                  "isRetry": false,
                  "values": [
                    {
                      "productName": "TEMPLATE",
                      "value": "10.158.129.11"
                    },
                    {
                      "productName": "764b17cc6f57875569146ef4e5a2",
                      "value": "10.158.129.11"
                    }
                  ]
                },
                {
                  "name": "ethernet",
                  "isRemediationEnabled": false,
                  "isRetry": false,
                  "values": [
                    {
                      "productName": "TEMPLATE",
                      "value": "eth0"
                    },
                    {
                      "productName": "764b17cc6f57875569146ef4e5a2",
                      "value": "eth0"
                    }
                  ]
                },
                {
                ...
                },
                {
                  "name": "passphrase",
                  "isRemediationEnabled": true,
                  "isRetry": false,
                  "values": [
                    {
                      "productName": "TEMPLATE",
                      "value": ""
                    },
                    {
                      "productName": "764b17cc6f57875569146ef4e5a2",
                      "value": ""
                    }
                  ]
                }
              ],
              "subCategory": []
            },
          ]
        },
        {
          "type": "vRealize Automation Cafe Virtual Machine",
          "nodeIdField": "vra2-web.sqa.local",
          "driftedProducts": [],
          "categories": [
    	    {
    	    ...
    	    }
          ]
        }
      ],
      "documentVersion": 0,
      "documentUpdateTimeMicros": 0,
      "documentExpirationTimeMicros": 0
    }

What to do next

If a change has occurred, you can trigger a drift remediation. See Trigger a Remediation.