When initiating a VirtualMachine migration through the web console, nodes marked as Ready,SchedulingDisabled (cordoned) appear as selectable and display status Ready.
If such a node is selected as the migration target, the migration is still triggered, ignores the unschedulable node and schedules the migration pod on a different worker.

The UI does not warn the user or reflect that the selected node cannot accept new workloads.

1. Have a VM on node A
2. Mark that nodeB as Ready,SchedulingDisabled from UI
3. Goto Migration->compute and select a node manually that is SchedulingDisabled.
4. Observe migration silently happens on other available node

This is wrong UI behavior. Either it should not show the node if it does, a user should be made aware of the state of node. screenshot attached

[cloud-user@ocp-psi-executor-xl numa]$ oc get nodes
NAME                                   STATUS                     ROLES                  AGE   VERSION
uit-test-day-05-dlwsd-master-0         Ready                      control-plane,master   30h   v1.33.5
uit-test-day-05-dlwsd-master-1         Ready                      control-plane,master   30h   v1.33.5
uit-test-day-05-dlwsd-master-2         Ready                      control-plane,master   30h   v1.33.5
uit-test-day-05-dlwsd-worker-0-4fdxl   Ready,SchedulingDisabled   worker                 29h   v1.33.5
uit-test-day-05-dlwsd-worker-0-8svxn   Ready                      worker                 29h   v1.33.5
uit-test-day-05-dlwsd-worker-0-9snqf   Ready                      worker                 29h   v1.33.5

4.20

1. Have a VM on node A
2. Mark that nodeB as Ready,SchedulingDisabled from UI
3. Goto Migration->compute and select a node manually that is SchedulingDisabled.
4. Observe migration silently happens on other available node

This is wrong UI behavior. Either it should not show the node if it does, a user should be made aware of the state of node. screenshot attached 

migration goes silently against users choice of node.

user shhould know