OPERATIONAL DEFECT DATABASE
...
...
Migrating to vRealize Automation 7.5.x or 7.6 fails on the "Migrate infrastructure node" step.In the /var/log/vmware/vcac/mseq.migration.log file, you see entries similar to: [2019-05-04 12:11:48.644571] Invoke script/usr/lib/vcac/tools/migration/sequence/migration/scripts/M97-migrate-iaas-node [2019-05-04 12:12:04.732032] Script invocation completed with code 1 [2019-05-04 12:12:05.044191] Traceback (most recent call last): File "/usr/lib/vcac/tools/migration/framework/mcore.py", line 470, in __execute task.execute(self.__context) File "/usr/lib/vcac/tools/migration/sequence/migration/execute", line 110, in execute raise Exception('Task finished with an error. See migrate.log files from the log bundle created and accessible from the VAMI console. {}'.format(self.__message)) Exception: Task finished with an error. See migrate.log files from the log bundle created and accessible from the VAMI console. [2019-05-04 12:12:05.044271] [<ID>:Failed] Migrate infrastructure node In the 'IaaS Management Agents' All.log file, you see traces of the migrate-node command actually succeeding similar to: [UTC:2019-05-04 10:26:59 Local:2019-05-04 12:26:59] [Debug]: [sub-thread-Id="30" context="" token=""] Command is executed - ID: <ID> Type: migrate-node Status: Completed Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
This issue occurs due to an issue with the command framework that the migration uses in vRealize Automation 7.5.x and 7.6 when the virtual appliance timezone is different than UTC.
This is a known issue affecting upgrades to VMware vRealize Automation 7.5.x or 7.6.Currently, there is no resolution.
To work around this issue, set the virtual appliance timezone to UTC prior to the migration.
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
