When creating a plan with a VM that has a critical concern (relevant for few of the concern types),then the plan status is marked as ready on backend and therefore on UI. 
An example for such a concern:
"The guest filesystem '/boot/efi' has 8 MB of free space, but a minimum of 10 MB is required for conversion. Free up space on this filesystem before migration".

1. This is confusing since the user sees a critical icon next to one of the concerns but the plan status indicated that the plan is valid for migration.

2. Only when starting the migration, the following error occurs on plan level:
"View critical concerns currently impacting your migration plan. All critical concerns must be addressed before the plan can be started."

Since the UI should no guess by itself if the plan status is " not ready" or "ready" due to its VMs concerns, I assume that this logic should be included on backend.

2.11

Always