Failed to migrate vCenter "Internal error occurs during Export of VMware Service Lifecycle Manager"

[NarinNil]

Hi,

I found the problem on stage 2 when trying to migrate from Windows vCenter 6.5 to VCSA 6.7 or VCSA 7.0.
They said "Internal error occurs during Export of VMware Service Lifecycle Manager" as below picture.
I got the same error both migration to VCSA 6.7 or VCSA 7.0.

I've checked the VMware Service Lifecycle Manager is running on the source vCenter.
Of course, I've verified my source vCenter working properly and I tried to restart it but no luck and stuck at this step.
Could anybody face this problem like me? please give me some advice, thanks.

---------------

[nhuotariHBS]

Hi, did you ever resolve this? I have the exact same error.

[nhuotariHBS]

I just ran into this issues doing the same upgrade from 6.7 to 7.0u3h and I was able to find some info in the logs:

WARNING vmon Failed to open file /etc/vmware/vmware-vmon/svcCfgfiles/backup. Err [Errno 21] Is a directory: '/etc/vmware/vmware-vmon/svcCfgfiles/backup'

My fix was to move this backup folder to another location (can likely delete as well)

mv /etc/vmware/vmware-vmon/svcCfgfiles/backup /tmp

Re-run the upgrade from stage 2

Ran without any more problems!

[cs1200]

Ran into this issue during a 6.7 Windows to 7.0.3h VCSA migration. Can confirm that moving vmware-vmon/svcCfgfiles/backup to a different directory fixed the issue - thank you!

[lakul]

Hello, I suspect to have the same problem but would like to confirm it first. In which log did you find this message?
In case I really have the same error, where can I delete the directory? The installation runs on a web based GUI. Do I have to log in to the current vCenter host via SSH?
Is it possible to start directly from Stage 2 again?
Thanks a lot for your help!

[Lalegre]

@NarinNil,

The best way would be getting the latest updated log on the following path on the new appliance deployed: /var/log/vmware/upgrade

Also, could you please let us know what is your source build and your destination build of the VCSA? Because there is a vSphere-back in time restriction issue that is also a reason for this error: https://kb.vmware.com/s/article/67077

[lakul]

Dear Lalegre,
thank you very much for your very quick reply.
I want to upgrade from version 6.7.0, 19195723 to version 7.0.3-18700403. I am using the ISO VMware-VCSA-all-7.0.3-18700403.
I searched all logs in the var\log\vmware\upgrade directory, but unfortunately I did not find any message containing e.g. the string svcCfgfiles.
A search for Failed returned the following results:

  \var\log\vmware\upgrade\Export_com.vmware.vcIntegrity_2023_05_27_19_58.log (1 Treffer)
	Row 66: 2023-05-27T17:58:30.477Z ERROR __main__ Upgrade Phase 'vcIntegrity:Export' failed. Exception: list index out of range
  \var\log\vmware\upgrade\export-upgrade-runner.log (6 Treffer)
	Row 574: 2023-05-27T17:58:30.640Z INFO upgrade.states.component_states vcIntegrity:Export: 2023-05-27T17:58:30.477Z ERROR __main__ Upgrade Phase 'vcIntegrity:Export' failed. Exception: list index out of range
	Row 590: 2023-05-27T17:58:30.642Z ERROR upgrade.states.component_states vcIntegrity:Export: Remote script failed with an error [InternalError()]
	Row 591: 2023-05-27T17:58:30.642Z ERROR upgrade.states.component_states vcIntegrity:Export: failed with internal error. For details take a look at Export_com.vmware.vcIntegrity_2023_05_27_19_58.log.
	Row 592: 2023-05-27T17:58:30.649Z WARNING wf.wf_processor State Export com.vmware.vcIntegrity has failed.
	Row 593: 2023-05-27T17:58:30.649Z ERROR wf.wf_processor Workflow execution has failed
	Row 604: 2023-05-27T17:58:30.934Z ERROR UpgradeRunner Upgrade mode export failed
  \var\log\vmware\upgrade\requirements-upgrade-runner.log (1 Treffer)
	Row 4534: 2023-05-27T17:57:17.374Z ERROR upgrade.states.preupgrade_state Failed to get Site Name.
  \var\log\vmware\upgrade\upgrade-export.log (1 Treffer)
	Row 1728: 2023-05-27T17:58:38.817Z ERROR upgrade_commands Export failed. Check export-upgrade-runner.log log for details.
  \var\log\vmware\upgrade\upgrade-requirements.log (1 Treffer)
	Row   96: May 27 19:33:17 vcenter.example.local sshd[41017]: Failed password for root from 192.168.11.108 port 49408 ssh2
  \var\log\vmware\upgrade\vcdb_warning.log (2 Treffer)
	Row 5381: DB ver:670 SOURCE:   VPX_VM.FAILED_DMOTION, DATA TYPE:numeric, DATA SIZE:1, NULLABLE:NO, DEFAULT:0 ====> EXPECTED: VPX_VM.FAILED_DMOTION, DATA TYPE:NUMERIC, DATA SIZE:1, NULLABLE:NO, DEFAULT:0
  \var\log\vmware\upgrade\vcdb_req.out (1 Treffer)
	Row  7301: INSERT INTO MGRD_EXP_TABLES_COLUMNS VALUES ('VPX_VM','FAILED_DMOTION','T','NUMERIC',1,'NO','0');
  \var\log\vmware\upgrade\bootstrap.log (1 Treffer)
	Row 1735: 2023-05-27T17:58:38.817Z ERROR upgrade_commands Export failed. Check export-upgrade-runner.log log for details.

Unfortunately, I can't figure it out. Do you have any idea?
Thanks and greetings

[Lalegre]

@lakul,

I believe this could be because of the vSphere Back-in Time but to be sure, could you please share the proper VCSA Build? The one you shared with me is an ESXi one. For getting the vCenter one you could go to the vCenter object into the vSphere Client, click on Summary and you will see the version there.

[lakul]

Oh sorry, my apologies.
I have
Version 6.7.0
Build 20504362

[lakul]

I can't find my revision number 20504362 in the matrix, only 20540798, so I'm looking in the last row, so upgrading to version 18700403 would not be possible at all. I would need at least version 20845200. Unfortunately I found only version 18700403 as download in my account.

[lakul]

I found the correct version in the download center and will try again this weekend.

One more question. I have tried 3 times so far and they all failed. Each attempt created folders on my storage named VMware vCenter Manager and VMware vCenter Manager_1 and VMware vCenter Manager_2. Certainly one folder for each attempt. Among other things, these folders contain many VMDK files and occupy an extremely large amount of space. Can I delete these folders?