Test & Automate: Verify transform remaps workload PVC reference after SC conversion (same namespace)

[msajidmansoori12]

Summary

Automate the MTA 8.3 Storage Class Conversion scenario that verifies Crane rewrites a workload PVC reference after a same-cluster, same-namespace PVC rename and StorageClass conversion.

This is a sub-issue of #661 (E2E test coverage for StorageClass conversion).

Polarion

• MTA-911 — [CLI][CRN] Verify transform step remaps workload PVC references after SC conversion (same namespace)
• https://polarion.engineering.redhat.com/polarion/#/project/MTAPathfinder/workitem?id=MTA-911

App

MongoDB single-PVC Deployment from k8s-apps-deployer.

Scope

• Same cluster and same namespace: mta-911-pvc-rename
• Non-admin source context with namespace-admin RBAC, using the existing e2e helpers
• Transfer mongodb-data to mongodb-data-new with a different StorageClass
• Run export and transform before apply
• Inspect the transformed Deployment directly
• Apply in the same namespace and verify MongoDB data remains intact

Acceptance Criteria

• Source MongoDB contains the expected seeded and test data before transfer.
• Destination PVC mongodb-data-new exists and uses a StorageClass different from the source.
• The transformed Deployment contains claimName: mongodb-data-new.
• The transformed Deployment does not contain the exact stale claim name claimName: mongodb-data.
• The applied workload mounts mongodb-data-new and MongoDB data count matches the source.
• No app.konveyor.io/created-for-pvc helper resources remain after transfer.
• The test cleans up the namespace, temporary StorageClass, application, and temporary files.

Related

• MTA-900: single PVC StorageClass conversion
• MTA-901: PVC rename and StorageClass conversion across namespaces
• MTA-902: StatefulSet PVC recreate conversion