'Latest updates already installed on vCSA, Nothing to stage/install' while patching VCSA 8.0.2.00100 to 8.0.2.00300
search cancel

'Latest updates already installed on vCSA, Nothing to stage/install' while patching VCSA 8.0.2.00100 to 8.0.2.00300

book

Article ID: 338150

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:

  • Patching VCSA post attaching ISO gives below error.
  • In patch runner logs, we see similar entries

YYYY-MM-DDTHH:MM:SS.469Z vpostgres:Patch ERROR vmware_b2b.patching.executor.hook_executor Patch hook 'vpostgres:Patch' failed.
Traceback (most recent call last):
  File "/storage/seat/software-updatef3mu09yz/stage/scripts/patches/py/vmware_b2b/patching/executor/hook_executor.py", line 74, in executeHook
    executionResult = systemExtension(args)
  File "/storage/seat/software-updatef3mu09yz/stage/scripts/patches/libs/sdk/extensions.py", line 106, in __call__
    result = self.extension(*args)
  File "/storage/seat/software-updatef3mu09yz/stage/scripts/patches/libs/sdk/extensions.py", line 123, in _func
    return func(*args)
  File "/storage/seat/software-updatef3mu09yz/stage/scripts/patches/payload/components-script/vpostgres/__init__.py", line 225, in patch
    raise UserError(_(_T('vpostgres.patch.upgrade',
patch_errors.UserError: PostgreSQL failed to run upgrade command.
YYYY-MM-DDTHH:MM:SS.476Z ERROR vmware_b2b.patching.phases.patcher Patch hook Patch got ComponentWrapperError.
Traceback (most recent call last):
  File "/storage/seat/software-updatef3mu09yz/stage/scripts/patches/py/vmware_b2b/patching/phases/patcher.py", line 208, in patch
    _patchComponents(ctx, userData, statusAggregator.reportingQueue)
  File "/storage/seat/software-updatef3mu09yz/stage/scripts/patches/py/vmware_b2b/patching/phases/patcher.py", line 90, in _patchComponents
    executeComponentHook(Hook.Patch, ctx, c, userData, reportingQueue)
  File "/storage/seat/software-updatef3mu09yz/stage/scripts/patches/py/vmware_b2b/patching/executor/execution_facade.py", line 97, in executeComponentHook
    result = executeHook(c.patchScript, hook, args,
  File "/storage/seat/software-updatef3mu09yz/stage/scripts/patches/py/vmware_b2b/patching/executor/execution_facade.py", line 53, in executeHook
    result = executor.executeHook(scriptFile, hook, args, reportQueue, reportIdentifier)
  File "/storage/seat/software-updatef3mu09yz/stage/scripts/patches/py/vmware_b2b/patching/executor/hook_executor_process.py", line 119, in executeHook
    raise ex
patch_errors.ComponentError
YYYY-MM-DDTHH:MM:SS.482Z WARNING root stopping status aggregation...
YYYY-MM-DDTHH:MM:SS.489Z ERROR __main__ Patch vCSA failed

  • In VAMI UI and appliance shell, you see a message similar to: "Latest updates already installed on vCSA, Nothing to stage/install"
  • VAMI is accessable.
  • While checking current status of "software_update_state.conf"  in /storage/core we see entries similar to :-

{
    "state": "INSTALL_FAILED",
    "version": "8.0.2.00100",
    "latest_query_time": "YYYY-MM-DDTHH:MM:SSZ"

 
 



Environment

VMware vCenter Server Appliance 8.0.x, 7.0.x

Cause

This issue occurs due to failed patching activity, however Vcenter services are UP


When software_update_state.conf is not updated as "Successful" or "UP TO DATE"

 

Resolution

 

  1. Login to the appliance using ssh
  2. Create a backup copy of the file /etc/applmgmt/appliance/software_update_state.conf in a different location, e.g. in /storage/core:
    # cp /etc/applmgmt/appliance/software_update_state.conf /storage/core/software_update_state.conf
  3. Stop the VAMI service by running the command:
    # service-control --stop applmgmt
  4. Remove the file /etc/applmgmt/appliance/software_update_state.conf :
    # rm -i /etc/applmgmt/appliance/software_update_state.conf
  5. change into the folder /var/log/vmware/upgrade :
    # cd /var/log/vmware/upgrade
  6. verify that the following 3 files exist in this folder:
    prechecks-succeeded
    export-succeeded
    import-succeeded
  7. If these files do not exist, run the following 3 commands to create them:
    # touch prechecks-succeeded
    # touch export-succeeded
    # touch import-succeeded
  8. confirm that the files have been created:
    # ls -l   
    
    -rw-r--r-- 1 root root    0 Mar 11  2019 prechecks-succeeded
    -rw-r--r-- 1 root root    0 Mar 11  2019 import-succeeded
    -rw-r--r-- 1 root root    0 Mar 11  2019 export-succeeded
  9. Start the VAMI service using the following command:
     # service-control --start applmgmt
  10. Login to the VAMI to validate the access