I found a bug in the new Aria Operations Configuration Drift management feature.

This is not necessarily a new bug, but rather an additional insight into an existing issue. Recently, I conducted testing on Configuration Drift in Aria Operations versions 8.18.1 and 8.18.3. Upon running the confirmation audit for the first time, the results returned as "Non-Compliant"—despite no apparent changes being made.

Curious about this behavior, I reached out to VMware engineering, who confirmed that this issue has been observed before—though not exactly in the same way. The relevant knowledge base article can be found here: Broadcom KB 378922. According to the KB, two specific fields, location_password and backup_password, are known to trigger a non-compliant status.

However, after further troubleshooting, I demonstrated to VMware that additional fields beyond these two are contributing to the issue. Given the vast number of fields within the audit JSON file, manually identifying all problematic fields would be extremely time-consuming.

I anticipate that VMware will release a hotfix to address this issue. I will update this post once I receive confirmation.