VCF Operations for Logs 9.0.x OVA deployment accepts non-compliant root password resulting in root login failure

Products

• VCF Operations

Issue/Introduction

During deployment of VCF Operations for Logs 9.0.x using the OVA directly through vCenter, the deployment wizard may accept a root password that does not meet the operating system password complexity requirements. After deployment completes, login to the root account may fail because the configured password is non-compliant with the underlying password policy.

Environment

• VCF Operations for Logs 9.0.x

Cause

The OVF template used during the OVA deployment only supports validation for minimum and maximum password length and password field designation. The OVF framework does not support validation for advanced password complexity requirements such as uppercase, lowercase, numeric, or special character enforcement.

As documented in the OVF specification (pages 28–29) , the OVF template schema does not provide a mechanism to enforce password complexity policies beyond basic length validation. Therefore, the deployment wizard accepting a non-compliant password is expected behavior from the OVF framework perspective and is considered a documentation limitation rather than a functional defect.

Resolution

Follow the How to reset the root password in VCF Operations for Logs to reset the root password through GRUB and configure a password that satisfies the operating system password complexity requirements.

VMware by Broadcom recommends deploying VCF Operations for Logs from VCF Fleet Management instead of deploying the OVA directly through vCenter, as VCF Fleet Management includes validation checks for the root password.

Additional Information

Deploying VCF Operations for logs
Default Password Requirements for VCF Components