Bug 1881268

Summary: Image uploading failed but wizard claim the source is available
Product: OpenShift Container Platform Reporter: Guohua Ouyang <gouyang>
Component: Console Kubevirt PluginAssignee: Gilad Lekner <glekner>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: high Docs Contact:
Priority: high    
Version: 4.6CC: aos-bugs, glekner, gouyang, ycui, yzamir
Target Milestone: ---   
Target Release: 4.7.0   
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: 2021-02-24 15:18:56 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 Guohua Ouyang 2020-09-22 02:26:05 UTC
Description of problem:
When image upload is failed with 'Data Volume failed to initiate upload', the DV and PVC is created in 'pending' status anyway, and on wizard general step, select the target OS, it shows `Source available`. 

Suggestion:
1. I guess cdi don't have the ability to delete the pvc/dv once image uploading is failed, on UI, it maybe alert user need to delete the pvd/dv manually.
2. On wizard, it should not claim the source is available if pvc/dv is pending.

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

How reproducible:


Steps to Reproduce:
1. When image uploading is failed with 'Data Volume failed to initiate upload'
2. Check PVC/DV
3. Check wizard

Actual results:
DV/PVC is created even with upload failed.
UI claim the source is available

Expected results:
If upload failed, it should clean the PVC/DV or alert user need to clean it manually, and UI should not claim the source is available.

Additional info:

Comment 2 Guohua Ouyang 2020-12-16 03:24:45 UTC
verified on 4.7.0-0.nightly-2020-12-13-202314

Comment 5 errata-xmlrpc 2021-02-24 15:18:56 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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-2020:5633