Skip to main content

 Troubleshooting Aria Automation reconciliation of vMotion migrated VM's

https://knowledge.broadcom.com/external/article?articleNumber=383529

Products

VMware Aria Suite

Issue/Introduction

Starting in Aria Automation 8.18.1, reconciliation of managed VM's that are vMotioned is possible preventing the VM's from reporting a 'missing' status: https://techdocs.broadcom.com/us/en/vmware-cis/aria/aria-automation/all/Chunk340324046.html

In some situations, a vMotion of a VM can still result in the machine going missing from Aria Automation inventory rendering the VM unavailable for management.

Environment

Aria Automation 8.18.1 and later

Cause

This can be caused by incorrect configuration of config mappings, failures leading to update status in Aria Automation database, and migration status not being reported correctly by vCenter.  See below for various checks to identify where this workflow may be failing.

Resolution

Validate vCenter Events and Automation Logging

vCenter must post the event so that the Aria Automation service account has permission to read them:

  1. Check that the service account assigned to the Cloud Account can access vCenter and see the events.  Look for events in vCenter related to "VmRelocatedEvent" and "VmBeingRelocatedEvent".In Automation logs, check in the Provisioining-service-app logs for responses to these migrations that include "VmEmigratingEvent".

Checking that the event broker config maps contain the correct event types

The Event Broker service in Aria Automation must be properly patched and it's config maps must be updated.  If something failed during upgrade or the service has not been patched, we can see it by performing the following: 

  1. SSH into Aria Automation.
  2. Execute the following command:
    1. kubectl get configmaps -n prelude ebc-events-config -o json

Review the output for the "ebs.connect.enabled-vcenter-event-types" to ensure that we're collecting proper vCenter events. An example of this output:

"ebs.connect.enabled-vcenter-event-types": "VmMigratedEvent,VmEmigratingEvent,VmBeingRelocatedEvent,VmRelocatedEvent,VmRelocateFailedEvent,com.vmware.vc.vm.DstVmMigratedEvent,com.vmware.vc.vm.SrcVmMigratedEvent,com.vmware.vc.vm.SrcVmMigrateFailedEvent,VmFailedMigrateEvent"

 

  1. Wait for data to sync and validate that the migration shows successful.

Validate the migration state is being populated in the Aria Automation database:

When migration is detected and a reconcile attempt is made, the resource metadata is updated with results under custom properties.  Check in the UI under the deployment/resource/custom properties for the properties called "migrationMessage" and "migrationStatus" and if there are errors they should show up in the migrationMessage.  Example of a successful reconcile will include the following status:

Alternatively you can query the metadata details of the resource in the database:

  1. SSH into the Aria Automation appliance and execute the following commands:
    1. vracli dev psql provisioning-db
    2. \x
    3. select * from compute_state where name = 'COMPUTERNAME'

In the output, look for all instances of the custom properties related to 'migration' for information.

Comments

Popular posts from this blog

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
  "Cloud zone insights not available yet, please check after some time" message on Aria Automation https://knowledge.broadcom.com/external/article?articleNumber=314894 Products VMware Aria Suite Issue/Introduction Symptoms: The certificate for Aria operations has been replaced since it was initially added to Aria Automation as an integration. When accessing the Insights pane under  Cloud Assembly  ->  Infrastructure  ->  Cloud Zone  ->  Insights  the following message is displayed:   "Cloud zone insights not available yet, please check after some time." The  /var/log/services-logs/prelude/hcmp-service-app/file-logs/hcmp-service-app.log  file contains ssl errors similar to:   2022-08-25T20:06:43.989Z ERROR hcmp-service [host='hcmp-service-app-xxxxxxx-xxxx' thread='Thread-56' user='' org='<org_id>' trace='<trace_id>' parent='<parent_id>' span='<span_id>'] c.v.a.h.a.common.AlertEnu...