Bug 1772912 - VM Wizard cannot find datavolume when creating VM from a templated created from URL
Summary: VM Wizard cannot find datavolume when creating VM from a templated created fr...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.3.0
Assignee: Filip Krepinsky
QA Contact: Radim Hrazdil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-15 14:43 UTC by Radim Hrazdil
Modified: 2020-01-23 11:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-23 11:13:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 3438 0 'None' closed Bug 1772912: fix URL source for VM Templates 2020-10-16 09:43:50 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:13:26 UTC

Description Radim Hrazdil 2019-11-15 14:43:33 UTC
Description of problem:
When a user selects a template created using URL provision method in VM Wizard, an error is raised saying that expected datavolume doesn't exist, but the datavolume actually does exist.

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-10-29-140935

How reproducible:
100

Steps to Reproduce:
1. Create a VM Template using URL provision method
2. Open VM Wizard and select the template created in step 1
3.

Actual results:
Could not select Provision Source. Datavolume <templatename>-rootdisk does not exist.

Expected results:


Additional info:

Comment 2 Radim Hrazdil 2019-11-19 11:32:33 UTC
Verified

Comment 4 errata-xmlrpc 2020-01-23 11:13:05 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, 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/RHBA-2020:0062


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