Migrate to Containers - December 6th, 2022 [Announcement, Deprecate, Feature, Fix, Issue]

## Announcement On Dec 6, 2022 we released Migrate to Containers 1.14.0. ## Feature Support for refactoring applications running on JBoss Enterprise Application Platform or [WildFly](https://www.wildfly.org/about/) application platform to containers, which lets you deploy the application as containers on GKE, GKE Autopilot clusters, Anthos clusters, and Cloud Run, released for Public Preview. See [Migrate JBoss Servers](https://cloud.google.com/migrate/containers/docs/migrating-overview#migrate%5Fa%5Fjboss%5Fserver). ## Feature Support for refactoring Apache 2 Linux based applications to containers, which lets you deploy Apache 2 application components as containers on GKE, GKE Autopilot clusters, Anthos clusters, and Cloud Run, released for Public Preview. See [Migrate Apache 2 Servers](https://cloud.google.com/migrate/containers/docs/migrating-overview#migrate%5Fan%5Fapache%5Fserver). ## Feature Enhanced control on the verbosity of backend logs. You can now use the `migctl logging set-verbosity <verbosity>` command, where verbosity `0` corresponds to info logs only and verbosity `1` shows debug logs. See [migctl reference](https://cloud.google.com/migrate/containers/docs/migctl-reference). ## Deprecate Containerization from AWS and Azure sources and local processing in AWS cluster are now deprecated and planned to be supported until April 2023\. ## Fix The following issues were fixed: * Windows IIS modernization - In case IIS files are not accessible to BUILTIN/Administrators, the discovery phase of IIS modernization will fail. * Support migration of Windows IIS sites where Administrator user has no permissions to access the IIS configuration files. * On Linux migrations, if the migration plan YAML is missing the Image section, the task will fail with a panic instead of an indicative message. ## Issue The following are open issues: * migctl migration status sometimes prints an error message before the migration table. This message does not indicate a concrete problem and can be ignored. * UI fails when performing "Processing Cluster Add" having Resource Location Org Policy. To overcome that, the processing cluster installation should be done using migctl and the target region should be provided using `--gcp-region`. * Two migrations from different M2VM sources on the same VM can affect each other. When using M2VM sources, users should avoid creating multiple Migration objects from different sources at the same time for the same VM. * Creation of multiple source providers at the same time may cause timeouts. If this happens users should delete and recreate source provider objects that failed to be created. * Replicated VM deletion can hang depending on other object deletion. To prevent this from happening users should delete M2VM source after deleting the corresponding Migration objects. Otherwise, if this happens users should delete the M2VM replications manually. * migctl setup uninstall failure - source snapshot is not deleted. This is happening when the corresponding source provider was already deleted. If this happens users should recreate the corresponding source provider and after migrations are removed to proceed with uninstalling. * Starting a migration from the UI page "Sources & Candidates" might get stuck on a "retrying" step. If this happens users should create a Migration using the VM name as input.