Description of problem: All migrations involving a PVC are reporting a PvUsageAnalysisFailed warning in the migration plan. Even if there is no problem with the free space and the PVCs are correctly mounted. Version-Release number of selected component (if applicable): SOURCE CLUSTER: AWS OCP 3.11 (MTC 1.5.1) TARGET CLUSTER: AWS OCP 4.9 (MTC 1.6.0) REPLICATION REPOSITORY: AWS S3 How reproducible: Alwasy Steps to Reproduce: 1. Deploy an application with a PVC oc new-project test-django oc new-app django-psql-persistent 2. Create a migration plan for this application Actual results: The migration plan is reporting this warning - category: Warn lastTransitionTime: "2021-08-23T10:10:14Z" message: 'Failed to compute PV resizing data for the following volumes. PV resizing will be disabled for these volumes and the migration may fail if the volumes are full or their requested and actual capacities differ in the source cluster. Please ensure that the volumes are attached to one or more running Pods for PV resizing to work correctly: [pvc-89f48bf6-03f9-11ec-8b27-0e6e082efb59]' reason: NotDone status: "True" type: PvUsageAnalysisFailed We can check that the PVC is correctly mounted and that it has no free space problems: $ oc get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE postgresql Bound pvc-89f48bf6-03f9-11ec-8b27-0e6e082efb59 1Gi RWO gp2 12m $ oc get pods NAME READY STATUS RESTARTS AGE django-psql-persistent-1-bfdcl 1/1 Running 0 11m django-psql-persistent-1-build 0/1 Completed 0 12m postgresql-1-s4dgx 1/1 Running 0 12m $ oc rsh postgresql-1-s4dgx sh-4.2$ df -h Filesystem Size Used Avail Use% Mounted on overlay 31G 6.7G 24G 23% / tmpfs 3.6G 0 3.6G 0% /dev tmpfs 3.6G 0 3.6G 0% /sys/fs/cgroup /dev/mapper/rhel-root 31G 6.7G 24G 23% /etc/hosts shm 64M 4.0K 64M 1% /dev/shm /dev/xvdby 976M 48M 913M 5% /var/lib/pgsql/data <<<<------------------- MOUNTED VOLUME tmpfs 3.6G 16K 3.6G 1% /run/secrets/kubernetes.io/serviceaccount tmpfs 3.6G 0 3.6G 0% /proc/acpi tmpfs 3.6G 0 3.6G 0% /proc/scsi tmpfs 3.6G 0 3.6G 0% /sys/firmware sh-4.2$ Expected results: There should be no warnings Additional info:
This was fixed in a PR that was submitted after the image build that was used here, and before this BZ was created, so it did not kick in the usual BZ automation. I'm manually moving this to MODIFIED to reflect that it has been merged into the v1.6.0 release branch, but has not been built yet. https://github.com/konveyor/mig-controller/pull/1175
verified with MTC 1.6.0 Image: registry.redhat.io/rhmtc/openshift-migration-controller-rhel8@sha256:d1bb94853b42abef96ec2c63600ebac41b0163d88fc25571f7b40c6c1d2f8c40
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Migration Toolkit for Containers (MTC) 1.6.0 security & bugfix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:3694