vCenter upgrade pre-check fails with error 'Getting error: Auto Deploy service is not running or not configured properly'.
search cancel

vCenter upgrade pre-check fails with error 'Getting error: Auto Deploy service is not running or not configured properly'.

book

Article ID: 435708

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • When performing a vCenter Server upgrade pre-check, the process fails with the following error in the UI:
    • Auto Deploy service is not running or not configured properly.
  • The upgrade log file /var/log/vmware/upgrade/rbd_YYYY_MM_DD_HH_MM.log contains an error stack similar to the following:
    YYYY-MM-DDTHH:MM:SS.466Z INFO autodeploy.upgrade_util The config data is {'serviceport': '6501', 'managementport': '6502', 'cacheSize': '2'}
    YYYY-MM-DDTHH:MM:SS.469Z ERROR autodeploy.upgrade_util Unable to compute the vital cache size
    Traceback (most recent call last):
      File "/tmp/vmware-upgrade-temp-dirUjYQGit0gr/tmpZfsUQ0pMIr/payload/component-scripts/autodeploy/upgrade_util.py", line 671, in computeCacheSize
        vitalCacheSizeBytes = dbConnection.execute(
    sqlite3.OperationalError: no such table: cache_item_file
    YYYY-MM-DDTHH:MM:SS.469Z ERROR autodeploy.autodeploy_upgrader Unable to prepare the upgrade spec during the collectRequirement phase for autodeploy
    Traceback (most recent call last):
      File "/tmp/vmware-upgrade-temp-dirUjYQGit0gr/tmpZfsUQ0pMIr/payload/component-scripts/autodeploy/autodeploy_upgrader.py", line 121, in collectRequirements
        cacheSize = computeCacheSize(metadata, sourceVcVersion)
      File "/tmp/vmware-upgrade-temp-dirUjYQGit0gr/tmpZfsUQ0pMIr/payload/component-scripts/autodeploy/upgrade_util.py", line 671, in computeCacheSize
        vitalCacheSizeBytes = dbConnection.execute(
    sqlite3.OperationalError: no such table: cache_item_file
    YYYY-MM-DDTHH:MM:SS.469Z INFO autodeploy.autodeploy_upgrader --- Successfully finished the collectRequirements phase
    YYYY-MM-DDTHH:MM:SS.471Z INFO extensions The component script returned '{'coreRequirement': {'requiredSrcDiskSpace': 0.0, 'requiredDstDiskSpace': {}, 'exportEstimationTime': 0, 'importEstimationTime': 0}, 'dstPortSpecs': [], 'srcPorts': [], 'userOptionSpecs': [], 'installArguments': {}, 'extraArguments': {}, 'requirementMismatchSpecs': [{'text': Auto Deploy service is not running or not configured properly., 'description': None, 'resolution': Ensure that Auto Deploy is running on the source and configured properly., 'problemId': None, 'severity': 'ERROR'}]}'

Environment

  • VMware vCenter Server 8.x

Cause

  • This issue occurs because the Auto Deploy service attempts to migrate an invalid or legacy database from the directory /var/lib/rbd/db instead of the active database location

Resolution

To resolve this issue, copy the valid Auto Deploy database to the expected legacy location.

 IMPORTANT: Always test command updates first in a non-production environment. Take a backup or snapshot before implementing in production.

  1. Take a powered-off snapshot of the source vCenter Server Appliance (VCSA).
  2. Establish an SSH session to the VCSA as root.
  3. Navigate to the active database directory:
    cd /etc/vmware-rbd/
  4. Copy the database file to the legacy directory:
    cp db /var/lib/rbd
  5. Restart the vCenter upgrade pre-check from the installer.