-
Bug
-
Resolution: Done-Errata
-
Critical
-
OADP 1.2.0
-
False
-
-
False
-
oadp-operator-bundle-container-1.2.1-2
-
ToDo
-
-
-
0
-
0
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
No
Description of problem:
During the backup process some of the mirrored PVCs has incorrect storage class.
Mirrored PVC snapcontent-*-pvc can have inconsistent storageclass from configmap options for volsync
Version-Release number of selected component (if applicable):
1.2.0
How reproducible:
100%
Steps to Reproduce:
1.Deploy an application with multiple PVCs.
2. Initiate a backup process.
3. Check the storage class of every mirrored PVCs (snapcontent-*-pvc) in openshift-adp namespace during backup that it matches storageclass set in volumeOptions in DPA.
Actual results:
The mirrored PVCs may have an inconsistent storage class, which does not match values set in dpa storageClass volumeOptions.
Expected results:
The mirrored PVCs should have the same storage class as the source PVC.
Additional info:
https://issues.redhat.com/browse/OADP-1821
https://github.com/migtools/volume-snapshot-mover/pull/236
https://github.com/migtools/volume-snapshot-mover/issues/235
- relates to
-
OADP-1821 Allow users to map volume options per user defined storage class in the DPA
- Closed
- links to
- mentioned on