The current implementation of storageclass conversion relies on a mechanism that spawns a distinct and new pvc with a different name than the original pvc using a convention of a "-new" suffix. It has been observed by users to cause problems in the scenario where you have an operated workload that has certain expectations about the resources that it owns and their names. In this case, MTC cannot update workloads managed by operators because of two issues: quiescing, and naming conventions.