Bug 1987091 - after upgrade from 4.8.0-477 to 4.8.0-480, source provider for template shows "Unknown"
Summary: after upgrade from 4.8.0-477 to 4.8.0-480, source provider for template show...
Keywords:
Status: CLOSED DUPLICATE of bug 1972966
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.9.0
Assignee: Yaacov Zamir
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-28 20:56 UTC by Matthias Muench
Modified: 2021-08-04 10:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-04 10:21:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Matthias Muench 2021-07-28 20:56:32 UTC
Description of problem:
Virtualization => Templates 
The Source provider column for templates with provided boot resources in version 4.8.0-477 was shown as "Available" with a green check mark but after update to 4.8.0-480, the column still shows the green check mark but now "Unavailable".  

Version-Release number of selected component (if applicable):
previous (created the source provider):  4.8.0-477
updated to: 4.8.0-480

How reproducible:
n/a

Steps to Reproduce:
1. create the source provider for Red Hat Enterprise Linux 8.0+ VM template by providing URL to download 
2. wait for completion - green check mark and VM can be created and shows "... available .." (exact term is missing)
3. update to 480 version

Actual results:
The previously Available entry changed to "Unknown"


Expected results:
After upgrade, the entry stays as "...available..."


Additional info:
The result is from OpenShift Virtualization 4.8.0 hackfest - limited (unsupported) environment given.

must-gather: https://drive.google.com/file/d/1oarBORWNTXcmT2HGVenTajBmy0VvXqoZ/view?usp=sharing

Comment 1 Yaacov Zamir 2021-08-04 10:21:00 UTC

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


Note You need to log in before you can comment on or make changes to this bug.