Bug 1957547 - [RFE]VM name is not auto filled in dev console
Summary: [RFE]VM name is not auto filled in dev console
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Gilad Lekner
QA Contact: Guohua Ouyang
Depends On:
TreeView+ depends on / blocked
Reported: 2021-05-06 01:26 UTC by Guohua Ouyang
Modified: 2022-03-10 16:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:03:38 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10763 0 None open Bug 1957547: [RFE]VM name is not auto filled in dev console 2022-01-05 16:17:14 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:04:05 UTC

Description Guohua Ouyang 2021-05-06 01:26:57 UTC
Created attachment 1780055 [details]
VM name is empty

Description of problem:
VM name is not auto filled in dev console

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

How reproducible:

Steps to Reproduce:
1. have a template source available
2. create a VM in dev console

Actual results:
VM name is not auto filled in dev console

Expected results:
VM name is auto filled.

Additional info:

Comment 1 Yaacov Zamir 2021-05-18 08:52:58 UTC
RFE, will be tracked and solved as a JIRA story: https://issues.redhat.com/browse/CNV-12017

Comment 4 Guohua Ouyang 2022-01-10 02:46:00 UTC
verified on master, the name in devconsole is auto-filled

Comment 7 errata-xmlrpc 2022-03-10 16:03:38 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.10.3 security 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.


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