Bug 1653688 - VM List -> create VM from yaml has incorrect yaml
Summary: VM List -> create VM from yaml has incorrect yaml
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 1.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 1.4
Assignee: Vojtech Szocs
QA Contact: Radim Hrazdil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-27 12:07 UTC by Tomas Jelinek
Modified: 2019-02-26 13:24 UTC (History)
5 users (show)

Fixed In Version: 1.4.0-11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-26 13:24:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt web-ui pull 181 0 None None None 2019-01-21 18:20:46 UTC
Red Hat Product Errata RHEA-2019:0417 0 None None None 2019-02-26 13:24:20 UTC

Description Tomas Jelinek 2018-11-27 12:07:42 UTC 
Description of problem:
You can not just click "create vm from yaml" and save. The provided yaml is not complete.

Expected results:
The provided yaml will be complete
Comment 1 Vojtech Szocs 2018-11-27 12:11:19 UTC 
This is already fixed in my KubeVirt extension PoC for openshift/console project.

I will open a PR once I finalize some initial integration tests (for now, a simple VM CRUD scenario). If you need more details, let me know.
Comment 2 Vojtech Szocs 2019-01-21 18:17:04 UTC 
PR posted: https://github.com/kubevirt/web-ui/pull/181
Comment 3 Rastislav Wagner 2019-01-23 14:52:43 UTC 
https://github.com/kubevirt/web-ui/pull/184
Comment 4 Radim Hrazdil 2019-01-29 15:35:27 UTC 
Verified that example VM yaml can be directly used to create a VM.
Version 1.4.0-11.
Comment 7 errata-xmlrpc 2019-02-26 13:24:16 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/RHEA-2019:0417
Note You need to log in before you can comment on or make changes to this bug.