Upgrade to 8.18.7 stuck on stage 8 in disconnected environments of Aria Operations
search cancel

Upgrade to 8.18.7 stuck on stage 8 in disconnected environments of Aria Operations

book

Article ID: 444860

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • When attempting to upgrade VMware Aria Operations from 8.18.6 to 8.18.7, the process may hang or become stuck for several hours at the following stages: "8 of 14 - Certificate renewed" or "7 of 14 -Preapply Validated"



  • The following errors can be seen in the respective log files:
    • /var/log/vmware/vcops/vcops_upgrade_<timestamp>.log
      DEBUG - b2b -updateCoordinator - runScript - Script command: "/usr/bin/tdnf list installed | grep photon_vasecurity"
    • /storage/vcops/log/pakManager/vcopsPakManager.root.apply_os_update.log
      DEBUG - Script command: "/usr/bin/tdnf list installed | grep photon_vasecurity"
DEBUG - stdout: ""
DEBUG - stdout: ""
2026-06-16T23:41:55 DEBUG - stdout: ""
DEBUG - stderr: "Error(1229) : Timeout was reached
Error: Failed to synchronize cache for repo 'VMware Photon Linux 5.0 (x86_64) Snapshot for Updates'

Environment

Aria Operations 8.18.6

Cause

During the upgrade, a check is made to an online repository. If internet access is unavailable (such as in disconnected Aria Operations environments), the upgrade process cannot resolve this dependency and gets stuck.

Resolution

Follow the Steps below to resolve the issue.

Workaround

  1. Roll back the Aria Operations appliance(s) to the snapshot taken prior to initiating the upgrade.

  2. Temporarily enable internet access for the appliance to https://packages.broadcom.com port 443.

  3. Re-attempt the upgrade to 8.18.7.

If internet access cannot be enabled in disconnected Aria Operations environments please follow the alternative workaround instructions below:

Alternative Workaround:

  1. Log in to the primary node as root in 2 separate SSH sessions

  2. In the first SSH session, start a tail on the vcops_upgrade_<timestamp>.log file

    tail -f $(ls /var/log/vmware/vcops/vcops_upgrade_2026*.log | tail -n 1)

  3. Validate that the last line in the file reads

    DEBUG - b2b -updateCoordinator - runScript - Script command: "/usr/bin/tdnf list installed | grep <some_package>

  4. In the second SSH session, kill the tdnf process

    pkill -f 'tdnf list installed'

  5. In the first SSH session, validate that the log file progresses and shows the same line but with a new package name

    DEBUG - b2b -updateCoordinator - runScript - Script command: "/usr/bin/tdnf list installed | grep <different_package>

  6. Repeat steps 4 and 5 (usually requires 5 times) until the log file in the first SSH session indicates

    INFO - b2b -updateCoordinator - programExit - Done upgrading to build: 0, exit code: 0

  7. Validate that the node automatically reboots in about 30 seconds

  8. Repeat steps 1 through 7 on the remaining nodes in the cluster in this order: primary replica node, then the data nodes, then the witness node

  9. Validate that the upgrade progresses in the Software Update tab in the Aria Operations Admin UI.

  10. After the upgrade is complete, repeat steps 1 through 7 on any cloud proxies that do not have direct connection to the internet.

This issue will be fixed in a future releases of Aria Operations.

Additional Information

Subscribe to this KB or refer the release notes for future product releases for any updates.

Powered by Wolken Software