Description of problem: During the testing of persistent volume (PV) resizing functionality as part of a migration process, it was observed that the PvCapacityAdjustmentRequired warning fails to appear in the migration plan after the pv_resizing_threshold is adjusted to 41% and the plan is refreshed. Version-Release number of selected component (if applicable): MTC 1.8.3 --- OCP 4.11 -> OCP 4.15 How reproducible: Always Steps to Reproduce: 1. In the source cluster, create a PersistentVolumeClaim (PVC) using the default storage class, requesting 1Gi of storage. 2. Deploy a pod in the source cluster that uses this PVC and populate the volume with files to consume at least 60% of its capacity. 3.Confirm the data consumption and PVC status using OpenShift CLI commands. 4.Enable the Direct Volume Migration (DVM) PV resizing feature in the 5.MigrationController configuration. 6.Create a migration plan for the namespace using DVM, ensuring no errors or warnings are present. 7. In the controller cluster, configure a new pv_resizing_threshold to 41%. 8.Refresh the migration plan to reflect the new threshold setting. Actual results: After setting the pv_resizing_threshold to 41% and refreshing the migration plan, the expected PvCapacityAdjustmentRequired warning did not appear in the migration plan Expected results: Upon setting the pv_resizing_threshold to 41% and refreshing the migration plan, a PvCapacityAdjustmentRequired warning should be displayed Additional info: https://polarion.engineering.redhat.com/polarion/#/project/MigrationToolkitCont/workitems?query=id%3AMTC%5C-148