vCenter Server Update Fails with "[errno 2] No such file or directory: '/storage/updatemgr/software-update-stage/update/patching_backup_config.json'. " and "Timeout" Errors When ISO is Attached via Remote Console
search cancel

vCenter Server Update Fails with "[errno 2] No such file or directory: '/storage/updatemgr/software-update-stage/update/patching_backup_config.json'. " and "Timeout" Errors When ISO is Attached via Remote Console

book

Article ID: 407105

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

During a vCenter Server appliance update, the installation fails and gets stuck at 33%. The update process displays the error message: [errno 2] No such file or directory: '/storage/updatemgr/software-update-stage/update/patching_backup_config.json'

In /var/log/vmware/applmgmt/update_microservice.log

RPMDownload failed after repeated attempts. Exception while copying packages
'####-##-## 10:21:50,490 - 923277 - dbfunctions_target::
', 'end_time' = DATETIME('now')], status = ?
WHERE 'phase = ?' with parameters
le copying packages', 'failed', 'Downloading RPMs')
####-##-## 10:21:50,494 - 923277 - task_manager_target::
'com.vmware.appliance.stage_error', 'default_message' = 'Error copying packages', 'args' = [ ],
: 'update_bb_target::
ion [Exception RPM download failed after repeated attempts. Exception while copying packages')]
####-##-## 10:21:50,497 - 923277 - dbfunctions_target::
config = ?' with parameters ('stage_duration(in mins)', ?)
####-##-## 10:21:50,49 - 923277 - dbfunctions_target:

Environment

vCenter 7.x

vCenter 8.x

Cause

The update fails because the ISO file, used for the patch, was attached to the vCenter via the remote console. This method is unreliable and can lead to a loss of connection to the ISO file, causing the update to fail.

 

 

Resolution

 

  • Revert the vCenter VM to its pre-update snapshot.

  • Upload the update ISO file directly to a datastore accessible by the vCenter.

  • Edit the settings of the vCenter VM to attach the ISO file from the datastore.

  • Restart the update process.

 

Additional Information