Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1845197

Summary:	Error is displayed in VM template disk tab when UI-created PVC is in same namespace
Product:	OpenShift Container Platform	Reporter:	Phillip Bailey <phbailey>
Component:	Console Kubevirt Plugin	Assignee:	Phillip Bailey <phbailey>
Status:	CLOSED DUPLICATE	QA Contact:	Guohua Ouyang <gouyang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.5	CC:	aos-bugs, gouyang, yzamir
Target Milestone:	---
Target Release:	4.5.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1845189	Environment:
Last Closed:	2020-06-08 18:43:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Phillip Bailey 2020-06-08 15:48:21 UTC

+++ This bug was initially created as a clone of Bug #1845189 +++

Description of problem:
An error is displayed in the disks tab if a PVC created through the PVC wizard is in the same namespace as the VM template.


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


How reproducible:


Steps to Reproduce:
1. Navigate to Storage > Persistent Volume Claims
2. Click the 'Create Persistent Volume Claim' button
3. Complete the form and click the 'Create' button
4. Navigate to Workloads > Virtualization > Virtual Machine Templates
5. Create a VM template in the same workspace (the PVC you created need not be used)
6. Go to the VM templates overview page and click the Disks tab

Actual results:
An error that says "Oh no! Something went wrong." is displayed along with a stack trace.


Expected results:
The list of disks should be displayed.


Additional info:
This appears to occur because PVCs created through the PVC wizard don't have the metadata.ownerReferences property. This causes an NPE, which then causes the error.

Comment 2 Yaacov Zamir 2020-06-08 18:43:40 UTC


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