Updates using online repositories fails if updates are attempted with the token which does not have entitlement for the specific product version
search cancel

Updates using online repositories fails if updates are attempted with the token which does not have entitlement for the specific product version

book

Article ID: 391459

calendar_today

Updated On:

Products

VMware vCenter Server 7.0 VMware vCenter Server 8.0

Issue/Introduction

  • vCenter Server patching fails with any of the following error message after updating the token by following the steps in KB VCF Authenticated downloads Configuration Update Instructions:

    Error copying packages:



    Update is not staged:



    [Errno 2] No such file or directory: '/storage/updatemgr/software-updatexxxxxx/stage/update/patching_backup_config.json':



    Error in method invocation Timeout happens while sending message to microservice:


     

Environment

7.x
8.x

Cause

  • The token does not have the entitlement for the specific version selected
  • The token is expired

Resolution

Cleanup the update state with the below steps and retry the update with a valid token:

  1. Delete the patching db:

    rm /storage/db/patching.db

  2. Check if the file: /storage/core/software-update/stage/stageDir.json is present, and check its content - 

    cat /storage/core/software-update/stage/stageDir.json

  3. If above file is present, it would give a stagedir location something similar to "/storage/<subdir>/software-updatexxxx". If so, delete this folder and files with command:

    rm -rf /storage/<subdir>/software-updatexxxx
    rm -rf /storage/core/software-update/stage/stageDir.json

  4. Clean up the state file

    rm /etc/applmgmt/appliance/software_update_state.conf

  5. Configure valid token based on the entitlement -  VCF Authenticated downloads Configuration Update
  6. Retry the vCenter Server patching

Additional Information

This issue can also occur due to an incorrect Download Token generated against the incorrect Site ID. 
The vCenter license must be tied to the same Site ID used to generate the Download Token.