Aria Operations 8.18x and later drift configuration template shows as non-compliant

Products

• VMware Aria Suite

Issue/Introduction

Drift configuration is a new feature introduced in Aria Operations 8.18, which allows to view and monitor all vCenter instances and their configuration specifications and compare configuration drifts or deviation from the original specification in vCenter.

with configuration Drifts a template is created in Aria Operations to monitor drift, when a drift a occurs, you can view the deviation from the configuration drift dashboard.

Certain drift configurations will show:

NON-COMPLIANT

this knowledge base article will answer the reason, why a drift template that matches the server specification in vCenter will show as NON-COMPLIANT

 

Environment

Aria Operations Manager 8.18

Cause

The reason why drift configuration templates shows as NON-COMPLIANT is as follows:

 

Drift configuration template containing these fields:

location_password

backup_password

will show as NON-COMPLIANT.

Currently the behavior in Aria Operations 8.18 is as follows:

1. Aria Operations will not store any passwords in the configuration template for security reasons.
2. VC is configured with the passwords in backup settings

Drift check will show NON_COMPLIANCE, because VC has valid password, and Template has blank password and cannot store that information.

Resolution

To work around the issue, omit having the two password fields in the drift configuration template.

 

Additional Information

This issue will be resolve in a future Aria Operations release, that will ignore, password fields in Config template are ignored during drift check, to allow drift check and show compliant.