Bug 1849555

Summary:	Confuse message in VM status during cdi import process
Product:	OpenShift Container Platform	Reporter:	Guohua Ouyang <gouyang>
Component:	Console Kubevirt Plugin	Assignee:	Phillip Bailey <phbailey>
Status:	CLOSED ERRATA	QA Contact:	Guohua Ouyang <gouyang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.5	CC:	aos-bugs, gouyang, phbailey, tjelinek, yzamir
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 16:08:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Guohua Ouyang 2020-06-22 08:28:34 UTC

Description of problem:
Create VM from URL, the cdi import process shows in VM status, the conclusion messages looks like below: 

- "The virtual machine is being imported."
- "The virtual machine could not be imported."

It causes confuse as we also have procedure of importing VM from VMware/RHV. This is about the CDI is importing image to VM rootdisk.

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

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Phillip Bailey 2020-07-01 19:31:51 UTC

Guohua,

Here are the current importing messages I see. I feel like these are sufficient. If you don't, could you please provide an example of what you think it should say? Thanks!

export const IMPORTING_VMWARE_MESSAGE = 'The virtual machine is being imported. Disks will be converted to the libvirt format.';
export const IMPORTING_ERROR_VMWARE_MESSAGE = 'The virtual machine could not be imported.';
export const IMPORTING_OVIRT_MESSAGE = 'The virtual machine is being imported.';
export const IMPORTING_ERROR_OVIRT_MESSAGE = 'The virtual machine could not be imported.';
export const IMPORTING_CDI_MESSAGE =
  'The virtual machine is being imported. Disks are being copied from the source image.';
export const IMPORTING_CDI_ERROR_MESSAGE = 'The virtual machine could not be imported.';
export const VMI_WAITING_MESSAGE =
  'The virtual machine is waiting for resources to become available.';
export const STARTING_MESSAGE =
  'This virtual machine will start shortly. Preparing storage, networking, and compute resources.';
export const IMPORT_CDI_PENDING_MESSAGE =
  'The importer pod is waiting for resources to become available.';

Comment 2 Guohua Ouyang 2020-07-02 02:49:12 UTC

I feel confusion because both "IMPORTING_CDI_MESSAGE" and "IMPORTING_VMWARE_MESSAGE" are "The virtual machine is being imported"/'The virtual machine could not be imported.'.

In my opinion, there should have some difference between "CDI import" from "RHV/Vmware import", otherwise we can place "URL" into "Import with Wizard", not "New with Wizard".

Maybe we can have some:

export const IMPORTING_VMWARE_MESSAGE = 'The virtual machine is being imported from VMware. Disks will be converted to the libvirt format.';
export const IMPORTING_OVIRT_MESSAGE = 'The virtual machine is being imported from RHV.';
export const IMPORTING_CDI_MESSAGE =
  'The source image is being imported into rootdisk via CDI.';

Comment 3 Yaacov Zamir 2020-07-02 05:04:45 UTC

@Philip hi, do you think this BZ is related to https://bugzilla.redhat.com/show_bug.cgi?id=1843532 ?

Comment 4 Phillip Bailey 2020-07-06 15:23:48 UTC

@Yaacov I think the naming issue is definitely related to the discussion in that BZ's comments. I have updated those comments with the findings from our chat conversation [1].

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1843532#c5

Comment 5 Tomas Jelinek 2020-07-10 05:48:57 UTC

This is being actively worked on, adding upcoming sprint.

Comment 8 Guohua Ouyang 2020-08-26 07:30:10 UTC

it displays "Importing (CDI)" for cdi importing now.

Comment 10 errata-xmlrpc 2020-10-27 16:08:40 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 (OpenShift Container Platform 4.6 GA Images), 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:4196