Bug 2228606

Summary: DataSource becomes not-ready if default StorageClass modified without deleting PVCs
Product: Container Native Virtualization (CNV) Reporter: Sarah Bennert <sbennert>
Component: StorageAssignee: Alex Kalenyuk <akalenyu>
Status: CLOSED DUPLICATE QA Contact: Natalie Gavrielov <ngavrilo>
Severity: high Docs Contact:
Priority: high    
Version: 4.14.0CC: akalenyu, dafrank
Target Milestone: ---   
Target Release: 4.14.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-13 12:55:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sarah Bennert 2023-08-02 20:22:57 UTC 
Description of problem:
Changing the default StorageClass to one that supports snapshots, without deleting initial PVCs, eventually causes DataSources to become non-ready.

Version-Release number of selected component (if applicable):
4.14.0

How reproducible:
100%

Steps to Reproduce:
1. Deploy w/ hostpath-csi-basic default StorageClass
2. Alter default StorageClass to snapshot supported SC (ocs-storagecluster-ceph-rbd)
3. Wait for reconciliation to update DataSource to snapshot

Actual results:
DataSource source changed to snapshot, but shows not-ready because original PVC source still exists.


Expected results:
DataSource does not change from PVC source to Snapshot source until original PVC source deleted.
- or -
Original PVC converted to snapshot


Additional info:
W/A: Delete PVC source to recreate for snapshot
- or -
Revert default StorageClass and update DataSource(s) manually to use original PVC
Comment 1 dalia 2023-09-13 12:41:47 UTC 
Alex, look like this one missed 4.14.0 and need to be pushed to 4.14.1, do we need a known issue in the 4.14 release notes
Comment 2 Alex Kalenyuk 2023-09-13 12:55:17 UTC 
(In reply to dalia from comment #1)
> Alex, look like this one missed 4.14.0 and need to be pushed to 4.14.1, do
> we need a known issue in the 4.14 release notes

Handled in https://bugzilla.redhat.com/show_bug.cgi?id=2227066

*** This bug has been marked as a duplicate of bug 2227066 ***