Cloud Proxy Config Modules Unhealthy After Upgrading Aria Operations to 8.18.7 from 8.18.6

Products

• VCF Operations

Issue/Introduction

• After upgrading VMware Aria Operations to version 8.18.7, the Cloud Proxy displays unhealthy Config Modules, triggering the alert "Issue with the Config Modules container".
• The cprc.upgrade.py.log.1 upgrade logs show read-only file system errors during the package extraction phase:

chown: changing ownership of '/storage/db/vmware-vrops-cprc-upgrade-working-dir/<REDACTED_SECRETS>/iso/product/config-modules-docker_1.1-0_i386.rpm': Read-only file system
<REDACTED_PII> - root - ERROR - CMD: [chown -v -R admin:admin /storage/db] failed with exit code: 1

 

• Subsequent Docker daemon journal logs (events.log) confirm the container is failing to initialize because the image is missing locally, and it attempts to pull from an inaccessible host:

level=error msg="Handler for POST /v1.50/auth returned error: Get \"https://<REDACTED_HOSTNAM

Environment

VMware Aria Operations 8.18.7

Cause

A transient storage fault during the upgrade forces the Guest OS into a read-only state, truncating the extraction of the config-modules-docker RPM package. Following a reboot, automated lifecycle scripts purge the upgrade directory before the container image can be loaded into the local Docker cache. The Docker daemon then defaults to pulling the image from a hardcoded, inaccessible internal registry, causing the configuration modules subsystem to fail permanently.

Resolution

Broadcom support is aware of this behavior and a corrected PAK will be available in a future release 8.18.8 to prevent the Docker daemon from defaulting to the internal registry.

Additional Information

For general Config Module container issues not related to a read-only filesystem fault, see: Troubleshooting the "Issue with the Config Modules container" alert in Aria Operations (424933)