“Scan entity” task hung at 0% , while upgrading the ESXi host using a baseline created from an offline bundle.
search cancel

“Scan entity” task hung at 0% , while upgrading the ESXi host using a baseline created from an offline bundle.

book

Article ID: 414820

calendar_today

Updated On:

Products

VMware vSphere ESXi VMware vCenter Server

Issue/Introduction

  •  Issue while upgrading the ESXi host using a baseline created from an offline bundle. During the remediate operation, the “Scan entity” task hung at 0%.





  • On the vCenter server /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log below is the error: 

    YYYY-MM-DDTHH:MM:SS.Z error vmware-vum-server[555043] [Originator@6876 sub=DownloadMgr] [downloadMgr 705] Executing download job {139624823759424} throws error: curl_easy_perform() failed: cURL Error: Timeout was reached, Resolving timed out after 60000 milliseconds^M
    YYYY-MM-DDTHH:MM:SS.Z info vmware-vum-server[555043] [Originator@6876 sub=DownloadMgr] [downloadMgr 807] Download failed but destination file /tmp/vci8tGin4 exists and is valid. Ignoring error^M
    .
    .
    YYYY-MM-DDTHH:MM:SS.Z error vmware-vum-server[565036] [Originator@6876 sub=Default] [updateDownloaderImpl 116] File download error: Downloading file: https://hostupdate.vmware.com/software/VUM/PRODUCTION/iovp-main/vmw-depot-index.xml failed, 0 byte downloaded.^M
    YYYY-MM-DDTHH:MM:SS.Z verbose vmware-vum-server[554889] [Originator@6876 sub=VcIntegrity] [vcIntegrity 786] Restart: 1, Initializing vcIntegrity: 1, Started to accept request: 1.^M

Environment

VMware vCenter 7.0.x
VMware vCenter 8.0.x
VMware ESXi 7.0.x
VMware ESXi 8.0.x

Cause

The issue occurred because the old VMware patch download source URLs were still enabled.
As vCenter continued attempting to communicate with these outdated URLs, the “Scan entity” task was unable to progress and hung at 0%.

Resolution

    1. Ensure to disable any of the old URLs as leaving these will cause vCenter to continue to try and reach them resulting in errors.

    2. Disable the default repositories following the below steps: 

        • Log into vSphere client
        • On the vSphere Client Home page, Navigate to Lifecycle Manager.
        • Click 'settings' tab. Under 'settings' tab,
        • Go to Administration → Patch Setup.
        • Disable default vLCM URLs by clicking "Disable" button

          Note:           The default URLs cannot be removed and delete button will be greyed out, it can only be Disabled.


    3. Restart update manager service from an SSH session to vCenter Server

      service-control --restart vmware-updatemgr

    4. Retry the remediation of the baseline. The process should now progress successfully beyond the “Scan entity” task without getting hung.

Additional Information

Powered by Wolken Software