Bug 1226794

Summary: "Doing conversion……" still shows after cancel the conversion from virt-p2v client
Product: Red Hat Enterprise Linux 7 Reporter: tingting zheng <tzheng>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: juzhou, mzhan, ptoscano, xiaodwan
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: P2V
Fixed In Version: libguestfs-1.28.1-1.38.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 07:01:32 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 tingting zheng 2015-06-01 06:39:52 UTC
Description
"Doing conversion……" still shows after cancel the conversion from virt-p2v client

Version:
libguestfs-1.28.1-1.37.el7.x86_64
virt-v2v-1.28.1-1.37.el7.x86_64
livecd-p2v-201505191242.iso	

How reproducible:
100%

Steps to Reproduce:
1.Launch virt-p2v client from virt-p2v iso.

2.After connect virt-v2v server and fill the cpu/memory/output info,start conversion.

3.During the conversion,click "Cancle conversion".After the conversion canceled,"Doing conversion……" still shows,which is very confusing for users.

Actual results:
As description.

Expected results:
No such info as "Doing conversion……" shows after canceled the conversion.

Additional info:

Comment 4 tingting zheng 2015-06-10 09:41:00 UTC
Tested with:
livecd-p2v-201506091319.iso
virt-v2v-1.28.1-1.38.el7.x86_64
libguestfs-1.28.1-1.38.el7.x86_64

During the conversion,click "Cancle conversion".After the conversion canceled,the info on virt-p2v client shows as:"Conversion cancelled by user".

Refer to the above comments,move the bug to VERIFIED.

Comment 6 errata-xmlrpc 2015-11-19 07:01:32 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://rhn.redhat.com/errata/RHBA-2015-2183.html