Bug 2215285

Summary:	SSP resets datasource reference to initial state
Product:	Container Native Virtualization (CNV)	Reporter:	Alex Kalenyuk <akalenyu>
Component:	Storage	Assignee:	Adam Litke <alitke>
Status:	CLOSED ERRATA	QA Contact:	dalia <dafrank>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.14.0	CC:	yadu
Target Milestone:	---	Keywords:	TestBlocker
Target Release:	4.14.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	CNV v4.14.0.rhel9-1088, kubevirt-ssp-operator-rhel9 v4.14.0-76	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-08 14:05:51 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 Alex Kalenyuk 2023-06-15 10:24:27 UTC

Description of problem:
With the introduction of snapshot sources for DataImportCrons,
it can be observed that the SSP keeps resetting the DataSource

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

How reproducible:
100%

Steps to Reproduce:
1. Ceph-rbd DataImportCrons
2. oc get datasource -n openshift-virtualization-os-images rhel9 -o yaml -w
3.

Actual results:
DataSource keeps flapping between some default PVC reference and snapshot reference

Expected results:
DataSource references a snapshot

Additional info:

Comment 1 dalia 2023-08-09 09:58:34 UTC

verified on OpenShift Virtualization   4.14.0

Comment 2 dalia 2023-08-09 09:58:35 UTC

verified on OpenShift Virtualization   4.14.0

Comment 4 errata-xmlrpc 2023-11-08 14:05:51 UTC

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 (Important: OpenShift Virtualization 4.14.0 Images security and bug fix 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-2023:6817