vCenter is unable to complete pre-check with "internal error" during upgrade
search cancel

vCenter is unable to complete pre-check with "internal error" during upgrade

book

Article ID: 345216

calendar_today

Updated On:

Products

VMware vCenter Server VMware vCenter Server 6.0 VMware vCenter Server 7.0

Issue/Introduction

  • vCenter upgrade fails with internal errors during pre-checks in upgrade stage 2, caused by stale extension com.vmware.migrate-connector.127.0.0.1 from a previous migration/upgrade.

  • In vCenter - /var/log/vmware/upgrade/requirements-upgrade-runner.log, the following error appears:

YYYY-MM-DDThh:mm:ssZ INFO output.requirements_result_producer Persisting preupgrade result :[
    {
        "requirements": {
            "installArguments": {},
            "userOptionSpecs": [],
            "coreRequirement": {
                "requiredSrcDiskSpace": 0.0,
                "requiredDstDiskSpace": {},
                "exportEstimationTime": 0,
                "importEstimationTime": 0
            },
            "requirementMismatchSpecs": [
                {
                    "description": null,
                    "severity": "ERROR",
                    "text": {
                        "localized": "Internal error occurs during execution of upgrade process.",
                        "translatable": "Internal error occurs during execution of upgrade process.",
                        "id": "ur.internal.text"
                    },
                    "resolution": {
                        "localized": "Please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request.",
                        "translatable": "Please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request.",
                        "id": "ur.internal.resolution"
                    },
                    "problemId": null
                }
            ],
            "dstPortSpecs": [],
            "extraArguments": {
                "legacySsoIps": null,
                "legacySsoFqdn": null,
                "legacyStsUrl": null,
                "legacySsoAdminEndpoint": null,
                "legacySsoHttpsPort": null,
                "legacyCpuCores": 4
            },
            "srcPorts": []
        },
        "name": "upgrade_framework",
        "optional": false,
        "installedOn": "localhost"
    }
]

YYYY-MM-DDThh:mm:ssZ INFO deployer.migration_env_deployer Updating extension -- com.vmware.migrate-connector.127.0.0.1
YYYY-MM-DDThh:mm:ssZ ERROR UpgradeRunner Upgrade Runner has encountered an exception
Traceback (most recent call last):
  File "/tmp/vmware-upgrade-temp-dir59Ig5fFWHm/tmp7d8uBv3e9X/UpgradeRunner.py", line 1889, in main
    envDeployer.setup(srcTargets, destTargets, isRegVcExt)
  File "/tmp/vmware-upgrade-temp-dir59Ig5fFWHm/tmp7d8uBv3e9X/py/deployer/migration_env_deployer.py", line 563, in setup
    self._setupTargets(srcTargetsToSetup, False, isRegVcExt)
  File "/tmp/vmware-upgrade-temp-dir59Ig5fFWHm/tmp7d8uBv3e9X/py/deployer/migration_env_deployer.py", line 535, in _setupTargets
    self._registerTargetAsExtension(targetConfig)
  File "/tmp/vmware-upgrade-temp-dir59Ig5fFWHm/tmp7d8uBv3e9X/py/deployer/migration_env_deployer.py", line 345, in _registerTargetAsExtension
    _registerExtension(srcSi, extKey, extCertificate)
  File "/tmp/vmware-upgrade-temp-dir59Ig5fFWHm/tmp7d8uBv3e9X/py/deployer/migration_env_deployer.py", line 78, in _registerExtension
    em.UpdateExtension(ext)
  File "/tmp/vmware-upgrade-temp-dir59Ig5fFWHm/tmp7d8uBv3e9X/libs/pyVmomi.zip/pyVmomi/VmomiSupport.py", line 556, in <lambda>
    self.f(*(self.args + (obj,) + args), **kwargs)
  File "/tmp/vmware-upgrade-temp-dir59Ig5fFWHm/tmp7d8uBv3e9X/libs/pyVmomi.zip/pyVmomi/VmomiSupport.py", line 368, in _InvokeMethod
    return self._stub.InvokeMethod(self, info, args)
  File "/tmp/vmware-upgrade-temp-dir59Ig5fFWHm/tmp7d8uBv3e9X/libs/pyVmomi.zip/pyVmomi/SoapAdapter.py", line 1481, in InvokeMethod
    raise obj # pylint: disable-msg=E0702
pyVmomi.VmomiSupport.vmodl.fault.SystemError: (vmodl.fault.SystemError) {
   dynamicType = <unset>,
   dynamicProperty = (vmodl.DynamicProperty) [],
   msg = 'lookup.fault.EntryNotFoundFault',
   faultCause = <unset>,
   faultMessage = (vmodl.LocalizableMessage) [],
   reason = 'Invalid fault'
}

Environment

  • VMware vCenter Server Appliance 6.7.x
  • VMware vCenter Server 7.0.x
  • VMware vCenter Server 8.0

Cause

The "com.vmware.migrate-connector.127.0.0.1" is an extension that is registered to the appliance during migration/upgrade process. It is expected to automatically remove itself once the process is complete.
 
However in this case, in a previous migration/upgrade, the extension was not removed causing issues in subsequent upgrade during pre-checks.

Resolution

Unregister the extension "com.vmware.migrate-connector.127.0.0.1" from either the vCenter MOB or the vCenter UI.

From the vCenter MOB (Managed Object Browser)

Note: If vCenter Server is in linked mode, perform this procedure on the vCenter Server that is used to install the plugin initially, then restart the vCenter Server services on the linked vCenter Server.

Prerequisite: Take a snapshot of the vCenter before making any changes. If this is a linked mode environment, powered off cold snapshots of all vCenters are required..

  1. In a web browser, navigate to:

    https://<vCenter_Server_name_or_IP>/mob

    where <vCenter_Server_name_or_IP> is the name of the vCenter Server or its IP address. Log in with the vCenter SSO admin credentials.

    Note: If receiving the error "HTTP Status 401 - Unauthorized" in the browser, refer to the following KB: "HTTP Status 401 - Unauthorized", accessing vCenter MOB fails from Edge & Chrome browsers

  2. Click Content.

  3. Click ExtensionManager.

  4. Select and copy the name of the plug-in to remove from the list of values under Properties

    Example: com.vmware.migrate-connector.127.0.0.1

  5. Click UnregisterExtension. A new window appears.

  6. Paste the key of the plugin and click Invoke Method. This removes the plugin and results in void.

  7. Close the window.

  8. Refresh the Managed Object Type:ManagedObjectReference:ExtensionManager window to verify that the plugin is removed successfully.

    Note: If the plugin still appears in the UI, a restart of the vSphere Client may be required.

To disable the plugin through the Client PlugIn manager within the vSphere Web Client 5.1 and later

  1. Log in to the vSphere Web Client with an vCenter Server Administrative user.
  2. When the error appears, click No.
  3. Navigate to Administration > Client Plug-Ins.
  4. Locate the client plug-in to disable.
  5. Right-click this entry and select Disable.
  6. Click Yes on the pop-up box for disabling the plugin.

Reference KB Cannot remove or disable unwanted plug-ins from vCenter Server and vCenter Server Appliance for additional details.

Powered by Wolken Software