NFA Migrator Fails during upgrade with no new logging in migrator.log

Products

• Network Flow Analysis
• Network Observability

Issue/Introduction

While upgrading Network Flow Analysis (NFA) you may run into a scenario where you experiece a migrator failure in the middle of the upgrade. 
Upon reviewing the D:/CA/NFA/Migrator/migrator.log you may be suprised to see that the log has not updated since the last upgrade or fresh installation. Attempting the run the migrator again manually will result with no output. 

Cause

This happens when you change the 'root' user password in MySql to a complicated password which includes blank space chatacters in the encrypted version of the password. We found that if the encrypted version your custom password contains blank spaces, it breaks the migrator and it prevents it from writing to the log.

Resolution

This issue will be fixed in NFA 25.4.4.

As a workaround to complete your upgrade, please revert the 'root' users password to the default value: root@123

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/network-flow-analysis/25-4/installing/post-installation-or-upgrade-tasks/configure-mysql-user-password.html

Then re-run the migrator.vbs or migrator.sh and ensure the migrator runs and exits with a code 0 with the last frame including the insert query of the NFA version you are trying to upgrade to. If all is well, rename the D:/CA/NFA/console_movie.xml (collector_movie.xml on harvester) to include old in the file name and move the file to the D:/CA/NFA/Migrator directory.

At this point you can set your password back. If your next upgrade is to NFA 25.4.4+ you will not run into this issue again.