vCenter Server 8.x staging fails with Error in method invocation timeout
search cancel

vCenter Server 8.x staging fails with Error in method invocation timeout

book

Article ID: 424499

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

vCenter staging fails with Error in method invocation timeout happens while waiting for task out file to appear

You encounter the following error message in the UI:

Error: Internal error occurs during execution of update process. Resolution: Send upgrade log files to VMware technical support team for further assistance.

When reviewing the /var/log/vmware/applmgmt/PatchRunner.log file, you observe a FileNotFoundError indicating a missing staging directory

2026-03-31T11:14:39.379Z INFO vmware_b2b.patching.phases.discoverer RPM stage dir is /storage/core/software-update/updates/8.0.3.00800/patch_runner/../../../stage/stageDir.json
2026-03-31T11:14:39.380Z ERROR vmware_b2b.patching.phases.discoverer Discovery hook got Exception.
Traceback (most recent call last):
  File "/storage/core/software-update/updates/8.0.3.00800/scripts/patches/py/vmware_b2b/patching/phases/discoverer.py", line 610, in discover
    _validateStorageForRpmInstallation(stageDir, fmwMismatches)
  File "/storage/core/software-update/updates/8.0.3.00800/scripts/patches/py/vmware_b2b/patching/phases/discoverer.py", line 481, in _validateStorageForRpmInstallation    rpmList = [(os.path.join(rpmStageDir, f)) for f in os.listdir(rpmStageDir) \
FileNotFoundError: [Errno 2] No such file or directory: '/storage/seat/software-updatexxxxxxx/stage'
2026-03-31T11:14:39.392Z ERROR __main__ Discovery of vCSA patching components failed

Environment

vCenter server 8.x

Cause

The patching workflow failed during the staging phase because the required configuration file, stage_operation, was renamed within the /storage/core/software-updates directory. Consequently, the patching task was unable to locate the necessary configuration file, resulting in a 'File not found' error during the staging operation.

Resolution

  • SSH to the vCenter Server appliance
  • Rename the incorrect file to the correct file name "stage_operation" 

  • Stop the appliance management service:

    service-control --stop applmgmt

  • Remove the update files:

    rm -rf /storage/core/software-update/updates/*
    rm -rf /storage/core/software-update/stage/*
    rm -rf /storage/db/patching.db

  • Move the staged configuration files:

    mv /etc/applmgmt/appliance/software_update_state.conf /storage/core

  • Restart the appliance management service:

    service-control --start applmgmt

  • Log back into the vCenter Server Management Interface (VAMI) at https://<vcenter-fqdn>:5480 and initiate the staging process again.