You can upgrade any outdated Software Agents on virtual machines on Amazon Web Service (AWS) or Azure manually.

Prerequisites

  • Successful upgrade to vRealize Automation 7.4.

  • A software tunnel is present and the tunnel virtual machine IP address is known.

Procedure

  1. Create a node file for each node that you need to upgrade.
    /usr/lib/vcac/server/webapps/ROOT/software/initializeUpdateSoftwareAgents.py -a <$DestinationVRAServer> -t <$Tenant> -tu <$TenantUser> -S <$SourceVRAServer>
    
    Note:

    For an in-place upgrade, the $DestinationVRAServer is the same as the $SourceVRAServer.

  2. Create a plan file to upgrade the Software Agent on a Linux or a Windows virtual machine.
    • Modify the migrate params file under /var/log/vcac/agentupdate/{tenant}/{subtenant-UUID} to contain the value of the private IP address corresponding to the AWS or Azure endpoint.

      "key": "ipAddress",
      
              "value": {
      
                  "type": "string",
      
                  "value": "<$PrivateIp:$PrivatePort>"
      
              }
    • Use this command for updating a Linux machine.

      /usr/lib/vcac/server/webapps/ROOT/software/updateSoftwareAgents.py -a <$DestionationVRAServer> -t <$Tenant> -S <$SourceVRAServer> -tu <$TenantUser> -CL Software.LinuxAgentUpdate74 --source_cloud_provider azure
    • Use this command for updating a Windows machine.

      /usr/lib/vcac/server/webapps/ROOT/software/updateSoftwareAgents.py -a <$DestionationVRAServer> -t <$Tenant> -S <$SourceVRAServer> -tu <$TenantUser> -CW Software.WindowsAgentUpdate74 --source_cloud_provider azure
    • This command runs the plan file.

      /usr/lib/vcac/server/webapps/ROOT/software/updateSoftwareAgents.py -a <$DestionationVRAServer> -t <$Tenant> -tu <$TenantUser> --plan_file /usr/lib/vcac/server/webapps/ROOT/software/plan
  3. Use this command to update the Software Agent using the node file from step 1 and the plan file from step 2.
    /usr/lib/vcac/server/webapps/ROOT/software/updateSoftwareAgents.py -a <$DestinationVRAServer> -t <$tenant> -tu <$TenantUser> --component_windows Software.WindowsAgentUpdate74 --component_linux Software.LinuxAgentUpdate74 --plan_file /usr/lib/vcac/server/webapps/ROOT/software/plan --plan_index 0 --node_file /usr/lib/vcac/server/webapps/ROOT/software/node --source_cloud_provider azure --action plan_batch -S <$SourceVRAServer>

    As an alternative, you can use this command to run one node at a time from the node file by providing a node index.

    /usr/lib/vcac/server/webapps/ROOT/software/updateSoftwareAgents.py -a <$DestinationVRAServer> -t <$tenant> -tu <$TenantUser> --component_windows Software.WindowsAgentUpdate74 --component_linux Software.LinuxAgentUpdate74 --plan_file /usr/lib/vcac/server/webapps/ROOT/software/plan --plan_index 0 --node_file /usr/lib/vcac/server/webapps/ROOT/software/node --source_cloud_provider azure --action execute_node -S <$SourceVRAServer> --node_index <0 through n-1>

    As you perform this procedure, you can tail logs from the vRealize Automation virtual appliance and host machine to see the Server Agent upgrade process.

    After upgrade, the upgrade process imports a software update script for Windows or Linux to the vRealize Automation 7.4 virtual appliance. You can log into the vRealize Automation virtual appliance host to ensure that the software component is imported successfully. After the component is imported, a software update is sent to the old Event Broker Service (EBS) to relay software update scripts to the identified virtual machines. When the upgrade completes and the new Software Agents become operative, they bind to the new vRealize Automation virtual appliance by sending a ping request.

    Note:

    Useful Log Files

    • Catalina output for source vRealize Automation: /var/log/vcac/catalina.out. In this file, you see the upgrade requests being made as the agent migrations are made. This activity is the same as running a software provisioning request.

    • Catalina output for destination vRealize Automation: /var/log/vcac/catalina.out. In this file, you see the migrated virtual machines reporting their ping requests here to include version numbers 7.4.0-SNAPSHOT. You can tally these together by comparing the EBS topic names, for example, sw-agent-UUID.

    • Agent update folder on destination vRealize Automation machine master upgrade log file: /var/log/vmware/vcac/agentupdate/updateSoftwareAgents.log. You can tail this file to see which upgrade operation is in progress.

    • Individual logs available under tenant folders: /var/log/vcac/agentupdate/{tenant}/{subtenant-UUID}. Individual nodes are listed here as lot files with failures and in-progress extensions.

    • Migrated VMs: /opt/vmware-appdirector/agent/logs/darwin*.log. You can spot check this location which should list the software update requests being received as well as the eventual restart of the agent_bootstrap + software agent.