'Drift check failed' error while running Configuration Drift in Aria Operations
search cancel

'Drift check failed' error while running Configuration Drift in Aria Operations

book

Article ID: 397615

calendar_today

Updated On: 06-18-2025

Products

VMware Aria Suite

Issue/Introduction

  • Navigating through Aria Operations UI > Operations > Configuration Drifts, the drift status check displays the error: "Drift check failed."

  • /storage/log/vcops/log/adapter/configadapter/configadapter.log  show 500 Internal Server Error message "Component AuthManagement is unavailable"

com.vmware.adapter3.vcf.unifiedconfig.task.DriftHandler.handleTask - Failed to get the drift results
[2000] com.vmware.adapter3.vcf.unifiedconfig.exception.VcfUnifiedConfigAdapterException: Caught rest client exception while calling api https://##.##.##.##:443/config-modules/api/vcenter/configuration/v1/scan-drifts: 500 Internal Server Error: "{"schema_version":"1.0-DRAFT","id":"#########################","name":"config_modules_vmware.controllers.vcenter.vc_profile","timestamp":"2025-05-07T03:55:06.787438","description":"Compliance check completed successfully","status":"FAILED","errors":[{"timestamp":"2025-05-07T03:55:06.787502","source":{"server":"##.##.##.##","type":"vcenter","endpoint":"https://vCenter IP/rest/cis/tasks/######################:com.vmware.appliance.vcenter.settings.v1.config"},"error":{"message":"Component AuthManagement is unavailable"},"remediation":{"message":"Check component on vcenter"}}],"target":{"hostname":"##.##.##.##","type":"vcenter"}}"
[2001] at com.vmware.adapter3.vcf.unifiedconfig.client.vc.ConfigModuleClient.execute(ConfigModuleClient.java:184) ~[VcfUnifiedConfigAdapter.jar:?]
[2002] at com.vmware.adapter3.vcf.unifiedconfig.client.vc.ConfigModuleClient.getDrift(ConfigModuleClient.java:151) ~[VcfUnifiedConfigAdapter.jar:?]
[2003] at com.vmware.adapter3.vcf.unifiedconfig.collect.strategy.configmodule.VCenterConfigModuleStrategy.getDrift(VCenterConfigModuleStrategy.java:45) ~[VcfUnifiedConfigAdapter.jar:?]
[2004] at com.vmware.adapter3.vcf.unifiedconfig.service.ConfigRetrieverService.lambda$getDrift$1(ConfigRetrieverService.java:87) ~[VcfUnifiedConfigAdapter.jar:?]
[2005] at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(Unknown Source) ~[?:?]
[2006] at java.util.stream.ReferencePipeline$2$1.accept(Unknown Source) ~[?:?]
[2007] at java.util.HashMap$EntrySpliterator.forEachRemaining(Unknown Source) ~[?:?]

....
[2024] Caused by: org.springframework.web.client.HttpServerErrorException$InternalServerError: 500 Internal Server Error: "{"schema_version":"1.0-DRAFT","id":"######################","name":"config_modules_vmware.controllers.vcenter.vc_profile","timestamp":"2025-05-07T03:55:06.787438","description":"Compliance check completed successfully","status":"FAILED","errors":[{"timestamp":"2025-05-07T03:55:06.787502","source":{"server":"##.##.##.##","type":"vcenter","endpoint":"vCenter IP/rest/cis/tasks/######################.vmware.appliance.vcenter.settings.v1.config"}
,"error":{"message":"Component AuthManagement is unavailable"},"remediation":{"message":"Check component on vcenter"}}],"target":{"hostname":"##.##.##.##","type":"vcenter"}}"

  • vCenter /var/log/vmware/infraprofile/infraprofile-svcs.log shows error  Duplicate key Roles

2025-04-30T15:28:49.328+10:00 [ForkJoinPool.commonPool-worker-3 [] INFO  com.vmware.appliance.infraprofile.plugins.compliance.ComplianceProvider  opId=] Getting compliance result of Authentication Management module.
2025-04-30T15:28:49.329+10:00 [ForkJoinPool.commonPool-worker-3 [] ERROR com.vmware.appliance.infraprofile.plugins.AuthenticationManagementPlugin  opId=] Error occurred while getting compliance
java.lang.IllegalStateException: Duplicate key Roles (com.vmware.appliance.vcenter.settings.v1.config.components.authmanagement.roles) => {
    id = <null>,
    name = ################# ReadOnly,
    description = <null>,
    privilegeIds = [####.Readonly.EventsView, ####.Readonly.ManageView, ####.Readonly.MonitorView, ####.Readonly.TroubleshootingView, ####.Readonly.InfrastructureView, ####.Readonly.ProvisioningView]
}

 

Environment

 Aria Operations 8.18.3

Cause

The failure was triggered due to the presence of duplicate roles identified during the drift status check in Aria Operations.

Resolution

Please follow the steps below to resolve this issue

1.Open the vSphere Client (vCenter).

2.Navigate to: Administration > Access Control > Roles.

3.Review the list and identify any duplicate roles.

4.Select any duplicate role(s) and click Delete to remove them.  These are any duplicate roles, not just those associated with Aria Operations.

5.Log in to Aria Operations.

6.Go to: Operations > Configuration Drifts.

7.Select the relevant vCenter and click Detect Drift to run a drift check and validate the drift status..