1 2 Previous Next 15 Replies Latest reply on Mar 19, 2019 5:35 AM by DaIceMan

    Upgrade from 5.5 latest to 6.0U2m using migration assistant fails in pre upgrade checks

    Lurker

      Hello

       

      I have two vCenter Servers, Production and Recovery Site, both Windows boxes, apart of same SSO domain, in linked mode and both at the latest build of 5.5. I am trying to upgrade my recovery site first to 6.0U2 using the migration assistant to create an appliance. The upgrade is failing in the pre-upgrade checker with the below errors in the migration-assistant.log:

       

      2016-11-02 13:16:27.406Z| migration-assistant-4191364| E: LaunchUpgradeRunnerCommon: Failed to run pre-upgrade phase: "C:\mig58D2.tmp\PFiles\VMware\CIS\python\python.exe" "C:\mig58D2.tmp\PFiles\VMware\CIS\cis_upgrade_runner\UpgradeRunner.py" --mode=requirements --configFile="C:\Users\MS_VCE~1\AppData\Local\Temp\UpgradeRunnerInput.json" --logDir="C:\Users\MS_VCE~1\AppData\Local\Temp\vcsMigration"  --locale=en --outputFile="C:\Users\MS_VCE~1\AppData\Local\Temp\UpgradeRunnerPreupgradeOutput.json"

      2016-11-02 13:16:27.406Z| migration-assistant-4191364| I: RemoveDirectoryIfEmpty: Successfully deleted empty directory C:\mig58D2.tmp.

      2016-11-02 13:16:27.407Z| migration-assistant-4191364| I: LaunchUpgradeRunnerCommon: Successfully deleted file: C:\Users\MS_VCE~1\AppData\Local\Temp\UpgradeRunnerInput.json

      2016-11-02 13:16:27.407Z| migration-assistant-4191364| I: Leaving function: LaunchUpgradeRunnerCommon

      2016-11-02 13:16:27.407Z| migration-assistant-4191364| I: ParseExportEstimatesFromPreUpgradeOutput: Component 'upgrade_framework': Export disk req [0 MB], Export time estimate [0 mins] and Import time estimate [0 mins].

       

       

      Error: Failed to discover a system name that is compatible with both your VMware vCenter Server certificate and your VMware Single Sign-On certificate that can be used to migrate to a VMware vCenter Server Appliance with an embedded Platform Services Controller.

      2016-11-02 13:16:27.439Z| migration-assistant-4191364| I: ParsePreUpgradeOutput: Resolution: Regenerate your VMware vCenter Server SSL certificate and your VMware Single Sign-On SSL certificate to have a common system name that can be used to migrate your system to VMware vCenter Server Appliance with Platform Services Controller. DHCP IP Address cannot be used as a system name to migrate to a VMware vCenter Server Appliance.

       

      So I have done my due diligence and replaced the certs on the vCenter (Embedded deployment with external/remote SQL DB) but I am still getting the same error. I can confirm the certificates have been regenerated and applied successfully. Also did a complete uninstall and re-install to no avail.

       

      Thoughts?

        • 1. Re: Upgrade from 5.5 latest to 6.0U2m using migration assistant fails in pre upgrade checks
          scott28tt Champion
          Community WarriorsUser ModeratorsVMware Employees

          Moderator note: Product questions/issues should be posted in the relevant area for that product - thread moved to vCenter Server.

          • 2. Re: Upgrade from 5.5 latest to 6.0U2m using migration assistant fails in pre upgrade checks
            jwingfield Lurker

            Have you identified a fix for this? I'm running into essentially the same issue, and I too have replaced the certs and even included the FQDNs, IP addresses, and Netbios names of both my vCenter server and SSO server in the Subject Alternative Name field of all of the certificates. The error persists though.

             

            2016-11-13 19:58:58.527Z| migration-assistant-4191364| E: ParsePreUpgradeOutput: Error: Failed to discover a system name that is compatible with your VMware vCenter Server SSL certificate that can be used to migrate to a VMware vCenter Server Appliance.

            2016-11-13 19:58:58.527Z| migration-assistant-4191364| I: ParsePreUpgradeOutput: Resolution: Regenerate your VMware vCenter Server SSL certificate to contain a system name that can be used to migrate your system to a VMware vCenter Server Appliance. DHCP IP Addresses cannot be used as a system name when migrating to a VMware vCenter Server Appliance.

            2016-11-13 19:58:58.527Z| migration-assistant-4191364| I: ParsePreUpgradeOutput: Populated AppNetPnid from PreUpgradeOutput: [].

            2016-11-13 19:58:58.527Z| migration-assistant-4191364| I: ParsePreUpgradeOutput: Certificate values retrieved IP Addresses: [] DNS Names: [].

            2016-11-13 19:58:58.527Z| migration-assistant-4191364| E: LaunchUpgradeRunnerPreUpgradePhase: Failed to parse preupgrade output.

            • 3. Re: Upgrade from 5.5 latest to 6.0U2m using migration assistant fails in pre upgrade checks
              mbrkic Hot Shot

              Hi,

              Has anyone figured this out yet? We are facing the same issue. We have an SR open with VMware and they are currently asking us to reinstall the Inventory Services, which according to the comment by O.P. most likely will not make a difference.

               

              Cheers,

              Milos

              • 4. Re: Upgrade from 5.5 latest to 6.0U2m using migration assistant fails in pre upgrade checks
                sanjeebkumar Enthusiast
                VMware Employees

                Can you post the migration assistant log? It should be in %temp%

                • 5. Re: Upgrade from 5.5 latest to 6.0U2m using migration assistant fails in pre upgrade checks
                  mbrkic Hot Shot

                  Here is the migration log. I changed the FQDN names and IPs to generic ones (for example vCenter-FQDN for the actual fqdn for vCenter server etc.).

                   

                  2016-11-16 21:02:02.405Z| migration-assistant-4191364| I: MAInit: stdout successfully changed to UTF-8 mode

                  2016-11-16 21:02:02.420Z| migration-assistant-4191364| I: SetMALocale: UI language id of machine 1033 is supported.

                  2016-11-16 21:02:02.420Z| migration-assistant-4191364| I: GetInstallParameter: Retrieving the data for vmdir.domain-name

                  2016-11-16 21:02:02.420Z| migration-assistant-4191364| W: GetPdtConfigDirPath: %VMWARE_CFG_DIR% environment variable expanded to [%VMWARE_CFG_DIR%]

                  2016-11-16 21:02:02.420Z| migration-assistant-4191364| I: ReadRegistryString: Registry value SOFTWARE\VMware, Inc.\vCenter Server\VMWARE_COMMONAPPDATA was not found

                  2016-11-16 21:02:02.420Z| migration-assistant-4191364| E: GetPdtConfigDirPath: Failed to get the Product Config directory path.

                  2016-11-16 21:02:02.420Z| migration-assistant-4191364| E: GetInstallDefaultsDirPath: Failed to get the install-defaults directory path.

                  2016-11-16 21:02:02.420Z| migration-assistant-4191364| I: GetInstallParameter: PropertyName=[vmdir.domain-name] : Value=[]

                  2016-11-16 21:02:02.420Z| migration-assistant-4191364| I: ParseCommandLineOptions: MA launched without passing command line parameters.

                  2016-11-16 21:02:02.452Z| migration-assistant-4191364| I: MAInit: Initializing Migration Assistant...

                  2016-11-16 21:02:02.452Z| migration-assistant-4191364| I: MAInit: Ctrl handler successfully set.

                  2016-11-16 21:02:02.467Z| migration-assistant-4191364| I: SanityCheckAdminPrivilege: Launching user retrieved successfully: 'DOMAIN\USERNAME'

                  2016-11-16 21:02:02.467Z| migration-assistant-4191364| I: SanityCheckAdminPrivilege: Process has admin privilege.

                  2016-11-16 21:02:02.499Z| migration-assistant-4191364| I: MAInit: Automated VUM upgrade disabled.

                  2016-11-16 21:02:02.499Z| migration-assistant-4191364| I: GetProductCodeFromUpgradeCode: Product {E1F05550-4238-4378-87F0-105147A251D9} installed with UpgradeCode {6ABA1091-7FFA-4342-91BC-D92A489B26E2}

                  2016-11-16 21:02:02.499Z| migration-assistant-4191364| I: GetProductCodeFromUpgradeCode: No products found for UpgradeCode {36A7C7D1-03E4-487E-9AAC-773CF118B4D8}

                  2016-11-16 21:02:02.499Z| migration-assistant-4191364| I: GetProductCodeFromUpgradeCode: No products found for UpgradeCode {84920751-2BCC-4924-A34B-31D4BAAD586C}

                  2016-11-16 21:02:02.499Z| migration-assistant-4191364| I: GetProductCodeFromUpgradeCode: No products found for UpgradeCode {869AA968-0000-FFFF-0011-110011001100}

                  2016-11-16 21:02:02.499Z| migration-assistant-4191364| I: GetProductCodeFromUpgradeCode: No products found for UpgradeCode {7E776B22-715F-40C2-9A29-878664F3D94D}

                  2016-11-16 21:02:02.514Z| migration-assistant-4191364| I: Entering function: RetrieveVpxdServiceAccountUser

                  2016-11-16 21:02:02.514Z| migration-assistant-4191364| I: QueryServiceConfigW: Successfully retrieved the Service Config for vpxd service

                  2016-11-16 21:02:02.514Z| migration-assistant-4191364| I: Leaving function: RetrieveVpxdServiceAccountUser

                  2016-11-16 21:02:46.030Z| migration-assistant-4191364| W: ValidateVcAdminCredentials: vim.fault.InvalidLogin

                  2016-11-16 21:02:46.030Z| migration-assistant-4191364| W: ValidateVcAdminCredentials: Failed to validate VC credentials. Host:localhost, Port:443, TunnelPath:, User:Administrator@vsphere.local.

                  2016-11-16 21:03:15.296Z| migration-assistant-4191364| I: ValidateVcAdminCredentials: Successfully validated VC credentials for Host:localhost, Port:443, TunnelPath:, User:Administrator@vsphere.local.

                  2016-11-16 21:03:20.952Z| migration-assistant-4191364| I: RetrieveServiceAccountToken: LookupAccountSid returned accountName=[VCService] domainName=[CLOUD].

                  2016-11-16 21:03:21.124Z| migration-assistant-4191364| I: RemoveDirectoryAndContents: Deleting directory: C:\Users\milosb_adm\AppData\Local\VMware\Migration-Assistant\PythonURExtractDir

                  2016-11-16 21:03:21.140Z| migration-assistant-4191364| E: RemoveDirectoryAndContents: Failed to delete directory: C:\Users\milosb_adm\AppData\Local\VMware\Migration-Assistant\PythonURExtractDir, Error: 124

                  2016-11-16 21:03:21.140Z| migration-assistant-4191364| I: PythonUpgradeRunnerExtractor::ExtractPythonAndUpgradeRunner: Extracting python msi.

                  2016-11-16 21:04:22.203Z| migration-assistant-4191364| I: PythonUpgradeRunnerExtractor::ExtractPythonAndUpgradeRunner: Installing upgrade runner msi.

                  2016-11-16 21:05:08.062Z| migration-assistant-4191364| I: GetNumHosts: Aggregated host count: 40

                  2016-11-16 21:05:08.140Z| migration-assistant-4191364| I: GetNumVMs: Aggregated vm count: 100

                  2016-11-16 21:05:08.234Z| migration-assistant-4191364| I: GetNumVMs: Aggregated vm count: 200

                  2016-11-16 21:05:08.250Z| migration-assistant-4191364| I: GetNumVMs: Aggregated vm count: 300

                  2016-11-16 21:05:08.265Z| migration-assistant-4191364| I: GetNumVMs: Aggregated vm count: 400

                  2016-11-16 21:05:08.281Z| migration-assistant-4191364| I: GetNumVMs: Aggregated vm count: 500

                  2016-11-16 21:05:08.281Z| migration-assistant-4191364| I: GetNumVMs: Aggregated vm count: 600

                  2016-11-16 21:05:08.297Z| migration-assistant-4191364| I: GetNumVMs: Aggregated vm count: 700

                  2016-11-16 21:05:08.312Z| migration-assistant-4191364| I: GetNumVMs: Aggregated vm count: 800

                  2016-11-16 21:05:08.312Z| migration-assistant-4191364| I: GetNumVMs: Aggregated vm count: 900

                  2016-11-16 21:05:08.312Z| migration-assistant-4191364| I: GetNumVMs: Aggregated vm count: 944

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: GetInventorySize: Inventory size retrieved. Hosts:40, VMs:944

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: wmain: Inventory size retrieved. Num of Hosts: 40, Num of VMs: 944

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: RunPreMigrationChecks: Running Prechecks...

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: LaunchUpgradeRunnerPreUpgradePhase: Changed the status of pre-upgrade checks to: RUNNING

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: Entering function: LaunchUpgradeRunnerCommon

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Handling property SSO_PASSWORD

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Substituting [SSO_PASSWORD] = ***

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Handling property VC_URL

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: GetJsonProperty: Property 'VC_URL' is not a json object

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: GetJsonProperty: Json was: //127.0.0.1:443

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Substituting [VC_URL] = '//127.0.0.1:443'

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Handling property SSO_USERNAME

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: GetJsonProperty: Property 'SSO_USERNAME' is not a json object

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: GetJsonProperty: Json was: Administrator@vsphere.local

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Substituting [SSO_USERNAME] = 'Administrator@vsphere.local'

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Handling property VPXD_SA_USER

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: GetJsonProperty: Property 'VPXD_SA_USER' is not a json object

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: GetJsonProperty: Json was: CLOUD\VCService

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Substituting [VPXD_SA_USER] = 'DOMAIN\SERVICEUSER'

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Handling property VPXD_SA_PASSWORD

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: GetJsonProperty: Property 'VPXD_SA_PASSWORD' is not a json object

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: GetJsonProperty: Json was: ***

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Substituting [VPXD_SA_PASSWORD] = ***

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Handling property VC_SSL_THUMBPRINT

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: GetJsonProperty: Property 'VC_SSL_THUMBPRINT' is not a json object

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: GetJsonProperty: Json was:

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Substituting [VC_SSL_THUMBPRINT] = ''

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Handling property VC_VERSION

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Substituting [VC_VERSION] = '5.5'

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Handling property MIGRATION_TYPE

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: GetJsonProperty: Property 'MIGRATION_TYPE' is not a json object

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: GetJsonProperty: Json was: management

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Substituting [MIGRATION_TYPE] = 'management'

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Handling property USER_OPTIONS

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: JsonResolveProperty: Substituting [USER_OPTIONS] with json object

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: CreateShortSymbolicLink: Symbolic link 'C:\migDDEF.tmp' created for path 'C:\Users\milosb_adm\AppData\Local\VMware\Migration-Assistant\PythonURExtractDir'.

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: LaunchUpgradeRunnerCommon: File C:\Users\MILOSB~1\AppData\Local\Temp\UpgradeRunnerPreupgradeOutput.json does not exist.

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: Entering function: LaunchProcAndMonitorStatus

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: LaunchProcAndMonitorStatus: Launching ""C:\migDDEF.tmp\PFiles\VMware\CIS\python\python.exe" "C:\migDDEF.tmp\PFiles\VMware\CIS\cis_upgrade_runner\UpgradeRunner.py" --mode=requirements --configFile="C:\Users\MILOSB~1\AppData\Local\Temp\UpgradeRunnerInput.json" --logDir="C:\Users\MILOSB~1\AppData\Local\Temp\vcsMigration"  --locale=en --outputFile="C:\Users\MILOSB~1\AppData\Local\Temp\UpgradeRunnerPreupgradeOutput.json"" in "C:\migDDEF.tmp\PFiles\VMware\CIS\python\"

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: LaunchProcAndMonitorStatus: Launched process with pid 1160 tid 7296

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: Entering function: MonitorStatusFile

                  2016-11-16 21:05:08.328Z| migration-assistant-4191364| I: MonitorStatusFile: Started execution of process

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: MonitorStatusFile: Other process terminated with 0, exiting

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: MonitorStatusFile: Process exited with a '0' exit code; no status monitoring so assuming success

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: MonitorStatusFile: called parse callback 0 times

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: MonitorStatusFile: No need to wait for process to complete

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: MonitorStatusFile: Process's job tree still hasn't terminated, waiting

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: MonitorStatusFile: Wait on process's job tree has completed: 0

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: Leaving function: MonitorStatusFile

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| W: LaunchProcAndMonitorStatus: Job still alive, terminating

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: Leaving function: LaunchProcAndMonitorStatus

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: RemoveDirectoryIfEmpty: Successfully deleted empty directory C:\migDDEF.tmp.

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: LaunchUpgradeRunnerCommon: Successfully deleted file: C:\Users\MILOSB~1\AppData\Local\Temp\UpgradeRunnerInput.json

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: Leaving function: LaunchUpgradeRunnerCommon

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseExportEstimatesFromPreUpgradeOutput: Component 'com.vmware.license': Export disk req [102 MB], Export time estimate [7 mins] and Import time estimate [5 mins].

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseExportEstimatesFromPreUpgradeOutput: Component 'com.vmware.vpxd': Export disk req [1 MB], Export time estimate [1 mins] and Import time estimate [1 mins].

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseExportEstimatesFromPreUpgradeOutput: Component 'com.vmware.vcdb': Export disk req [2048 MB], Export time estimate [7 mins] and Import time estimate [25 mins].

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseExportEstimatesFromPreUpgradeOutput: Component 'com.vmware.vco': Export disk req [83 MB], Export time estimate [1 mins] and Import time estimate [1 mins].

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseExportEstimatesFromPreUpgradeOutput: Component 'com.vmware.is': Export disk req [1024 MB], Export time estimate [20 mins] and Import time estimate [60 mins].

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseExportEstimatesFromPreUpgradeOutput: Component 'com.vmware.sps': Export disk req [0 MB], Export time estimate [1 mins] and Import time estimate [1 mins].

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseExportEstimatesFromPreUpgradeOutput: Component 'upgrade_framework': Export disk req [0 MB], Export time estimate [0 mins] and Import time estimate [0 mins].

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParsePreUpgradeOutput: Retrieved infra node address: [VUM-FQDN] and sso.sts.url [https://VUM-FQDN:7444/sts/STSService/vsphere.local].

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParsePreUpgradeOutput: VC machine/cert parameters. AppNetPnid: [vCenter-FQDN], CertIPs: [], CertFQDNs: [].

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParsePreUpgradeOutput: Database settings: Type='external'

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| E: SelectAppNetPnid: No IPs or FQDNs present in the certificate.

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| E: ParsePreUpgradeOutput: Error: Failed to discover a system name that is compatible with your VMware vCenter Server SSL certificate that can be used to migrate to a VMware vCenter Server Appliance.

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParsePreUpgradeOutput: Resolution: Regenerate your VMware vCenter Server SSL certificate to contain a system name that can be used to migrate your system to a VMware vCenter Server Appliance. DHCP IP Addresses cannot be used as a system name when migrating to a VMware vCenter Server Appliance.

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParsePreUpgradeOutput: Populated AppNetPnid from PreUpgradeOutput: [].

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParsePreUpgradeOutput: Certificate values retrieved IP Addresses: [] DNS Names: [].

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| E: LaunchUpgradeRunnerPreUpgradePhase: Failed to parse preupgrade output.

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: LaunchUpgradeRunnerPreUpgradePhase: Changed the status of pre-upgrade checks to: FINISHED

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: RunPreMigrationChecks: Upgrade Runner prechecks returned status: 0

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: Processing pre-upgrade for component com.vmware.license

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: No mismatch to process.

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: Processing pre-upgrade for component com.vmware.vpxd

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: Processing pre-upgrade for component com.vmware.vcdb

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: No mismatch to process.

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: Processing pre-upgrade for component com.vmware.vco

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: No mismatch to process.

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: Processing pre-upgrade for component com.vmware.is

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: No mismatch to process.

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: Processing pre-upgrade for component com.vmware.sps

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: No mismatch to process.

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: Processing pre-upgrade for component upgrade_framework

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: No mismatch to process.

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: Parsed 1 error messages.

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: Error messages: Error: vCenter CA cerfificate not verified. Stopping.

                  Resolution: Please use the vCenter Upgrade Logs to get more details of this error.

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: Parsed 1 warning messages.

                  2016-11-16 21:05:53.125Z| migration-assistant-4191364| I: ParseErrorsWarningsFromPreUpgradeOutput: Warning messages: Warning: This vCenter Server has extensions registered that cannot be upgraded to or may not work with the new vCenter Server.

                   

                  Extensions:

                   

                  vShield Manager (by VMware Inc.) on https://vCenter-FQDN/sdk/vimService 

                  VMware vCenter vCO plugin on https://vCO-IP:8281 

                  VMware vCenter vCO plugin on https://vCO-IP:8281 

                  VMware vSphere Update Manager Extension on https://VUM-FQDN:8084/vci/sdk 

                  Zerto Replication Plugin (by Zerto, Inc.) on https://ZVM-IP:9669/ZvmService/GuiPageServer/pubsplugin.xml 

                   

                  Resolution: Please ensure extensions are compatible with the new vCenter Server and re-register extensions with the new vCenter Server after upgrade.

                  Please refer to the vSphere documentation on extensions, and the upgrade and interoperatbility guides.

                  2016-11-16 21:05:53.141Z| migration-assistant-4191364| I: CreateEmptyZipFile: Successfully created empty zip file

                  • 6. Re: Upgrade from 5.5 latest to 6.0U2m using migration assistant fails in pre upgrade checks
                    mbrkic Hot Shot

                    Hi,

                    In case someone runs into this again - we resolved this by recreating the self signed certificates for vCenter Service, Inventory Service and the Web Client Service. Below are the main steps we followed.

                     

                    Set up three directories for the three services (vCenter, IS, and WC) and create an openssl.cnf file in each directory that contains the following:

                     

                    [req]

                    default_bits = 2048

                    default_keyfile = rui.key

                    distinguished_name = req_distinguished_name

                    #Don't encrypt the key

                    encrypt_key = no

                    prompt = no

                    string_mask = nombstr

                    x509_extensions = v3_req

                     

                    [ req_distinguished_name ]

                    countryName = CA

                    stateOrProvinceName = Ontario

                    localityName = Toronto

                    1. 0.organizationName = Company Name

                    organizationalUnitName = vCenterServer

                    emailAddress = ssl-certificates@company.com

                    commonName = vCenter-FQDN

                     

                    [v3_req]

                    # Extensions to add to a certificate request

                    basicConstraints = CA:FALSE

                    keyUsage = digitalSignature, keyEncipherment, dataEncipherment

                    extendedKeyUsage = serverAuth, clientAuth

                    subjectAltName = @alt_names

                     

                    [alt_names]

                    1. DNS.1 = vCenter-Short
                    2. DNS.2 = vCenter-FQDN
                    3. IP.1 = vCenter-IP

                     

                    Note that I changed the FQDNs and IPs above (e.g., vCenter-IP is the actual IP of the vCenter).

                    The organizationalUnitName attribute must be set differently for each service - (vCenterServer, vCenterWebClient, vCenterInventoryService).

                     

                    Once you have these three config files for the three services create the certs and keys by running the following command in each directory (you may need to change the location of openssl):

                    "c:\Program Files\VMware\Infrastructure\Inventory Service\bin\openssl.exe" req -nodes -new -x509 -keyout rui.key -out rui.crt -days 3650 -config openssl.cnf

                     

                    Now you should have a rui.key and rui.crt file in each of the three directories. You should be able to look at those certs in Windows and see the subjectAltName containing two DNS entries (short and long) and an IP entry.

                     

                    Rename the rui.crt file to rui.pem for all three certs.

                     

                    Now, download the SSL Certificate Automation Tool 5.5 and closely follow the process from KB 2057340 to replace the certificates with the ones you just created.

                     

                    Make sure you edit the ssl-environment.bat file with the locations of the different certs that you previously created, for the different services.

                     

                    Be patient . The steps take a while as they restart the different processes and services. After each step the menu to select the next step came back so we could proceed.

                     

                    Once we did all this and the certs were successfully updated the migration assistant precheck ran without issues. We have not proceed to the the vCenter upgrade yet, but the assistant was ready for the upgrade step.

                     

                    Let me know if anyone needs more details, and I can post them.

                     

                    Cheers,

                    Milos

                    • 7. Re: Upgrade from 5.5 latest to 6.0U2m using migration assistant fails in pre upgrade checks
                      Sparkie_E Lurker

                      Going to give this a go.

                      Had a call open with support for about 4 weeks now......Cheers!

                      • 8. Re: Upgrade from 5.5 latest to 6.0U2m using migration assistant fails in pre upgrade checks
                        secops Novice

                        Has anyone resolved this error, without having to replace all the signed certs back to self-signed?

                         

                        Thanks.

                        • 9. Re: Upgrade from 5.5 latest to 6.0U2m using migration assistant fails in pre upgrade checks
                          SiKr Lurker

                          @mbrkic Thank you very much for your detailed step by step guide!

                           

                          Worked like a charm.

                           

                          Greetings,

                          Simon

                          • 10. Re: Upgrade from 5.5 latest to 6.0U2m using migration assistant fails in pre upgrade checks
                            avsopov Lurker

                            You could also check if cacert.pem contains BASE64 encoded CA certificate.

                             

                            I solved the problem without switching back to self-signed certificates by replacing cacert.pem with a correct one.

                            • 11. Re: Upgrade from 5.5 latest to 6.0U2m using migration assistant fails in pre upgrade checks
                              carlosCRO Lurker

                              Could you you describe what did you do exactly? I got the same issues with pre-upgrade checks and I do not want to switch back to self-signed certificates-

                              Kind regards,

                              Nenad

                              • 12. Re: Upgrade from 5.5 latest to 6.0U2m using migration assistant fails in pre upgrade checks
                                sc_2111 Enthusiast

                                I'm having the following error while updating the IS cert using the migration tool

                                The leaf certificate doesn't have any CN or subjectAltName that macthes the public address of the current machine

                                 

                                It suggest to set the ssl_tool_no_cert_san_check

                                 

                                did you set it ?

                                thanks

                                • 13. Re: Upgrade from 5.5 latest to 6.0U2m using migration assistant fails in pre upgrade checks
                                  akorppi Lurker

                                  Thaks mbric. Your detailed steps worked for us.

                                  • 14. Re: Upgrade from 5.5 latest to 6.0U2m using migration assistant fails in pre upgrade checks
                                    newtom71 Lurker

                                    I'm not using certificates and I get this error, any ideas?

                                    1 2 Previous Next