Bug 1914301 - User VM Template source should show the same provider as template itself
Summary: User VM Template source should show the same provider as template itself
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.7
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.7.0
Assignee: Rastislav Wagner
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-08 14:57 UTC by Rastislav Wagner
Modified: 2021-02-24 15:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:51:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 7773 0 None closed Bug 1914301: Use custom template provider as provider for source too 2021-01-13 09:44:41 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:51:51 UTC

Description Rastislav Wagner 2021-01-08 14:57:38 UTC
Description of problem:
Custom VM template with provider specified should have the same provider for its boot source too


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

How reproducible:
always

Steps to Reproduce:
1. Create custom VM Template, specify provider
2. go to VM Templates list, boot source should show the same value as template provider (if none was specified it should show just `Available`)

Comment 2 Guohua Ouyang 2021-01-13 10:44:53 UTC
verified on lastet OCP 4.7

Comment 5 errata-xmlrpc 2021-02-24 15:51:25 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


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