Migration warnings
This page describes the warnings that you might get after you run the
analyze command.
Types of warnings
After you run the analyze command, Migrate to Containers might provide warnings
specific to your migration type.
There are two possible types of warnings:
MigrationBlockerwarnings: These warnings block your migration, and you must address them. You cannot generate the artifacts of a migration while there are activeMigrationBlockerwarnings.Normalwarnings: These are non-blocking warnings that you can decide to address. Even though warnings of typeNormaldon't block the generation of artifacts, they might cause the migration process to fail, or cause the migrated workload to fail when run.
How to read the warnings
If there are warnings, they appear in the warnings.yaml file in the output
directory of the analyze command.
Each warning message contains the following fields:
- type: The type of warning, either
MigrationBlockerorNormal. - reason: The cause of the warning.
- mitigation: The description of the warning and possible actions to resolve it.
For example, the following is a FileTooBig warning for Linux.
- message: The source VM file-system contains file(s) which are too big to be part of the generated container image
mitigation: Please edit the migration plan to either filter them out, or export them to a data volume
reason: FileTooBig
type: MigrationBlocker