Migration App UI v1.16.3 / Agent v3.14.0 Release Date: 12/20/22
Self-Healing Jobs
Previously, when experiencing connection interruptions, migration jobs would fail, requiring the Migration Operator to continue restarting the job. With this release, we implemented several things to ensure that once the Migration Operator sets a migration command in motion, the app will continue to reconnect in the case of an interruption, until the job is completed.
New Support Log Upload for Help Tickets
Now when a Migration Operator submits a Support ticket from within Migration App, all the necessary local logs will be included with the ticket submission.
The dialog box that is presented after the user selects “Help” will be auto-populated with Agent Name and Job Name, as appropriate or available within that context. What this means is that since you can select "Help" from different places within the User Interface, you’ll see a slightly different dialog box, depending on where you are.
- If the user selects "Help" from the Migration Dashboard, the user will be prompted to select both the appropriate Agent Name and Job Name from the dropdowns in the dialog box.
- If the user selects "Help" from the three dots next to Agent name, the Agent will be pre-populated, but the user will be prompted to select the appropriate Job Name from the dropdown in the dialog box.
- If the user selects "Help" from the three dots next to Job name, the Job name will be pre-populated, but the user will be prompted to select the appropriate Agent Name from the dropdown in the dialog box.
- If the user selects "Help" from the Migration Details page, both Agent Name and Job Name will be populated.
Issues Addressed
Some Migrations Failing with 2100 when Auto Scheduler Runs
Some migrations were failing with "Failed to load disk based hash map (#2100)". Workaround was to re-run the job. This is a corner case that can happen when there are a high number of concurrent migrations running. Now it has been fixed so that the system retries until the failed migration succeeds.
1100 Error while Running Existing Migration after Agent Auto Retirement
We received multiple tickets reporting user getting error 1100 when trying to run a pre-existing migration after the auto retirement of agents. This was happening because either the migration details were not present in the migration_info.json file or the migration_info.json file itself was not present. We put a workaround in place to remedy this.