Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of Problem:
When kill virt-p2v-server process during conversion of virt-p2v,the client has no messages prompted and no messages logged
Version-Release number of selected component:
virt-v2v-0.8.7-4.el6.x86_64
rubygem-virt-p2v-0.8.6-2.el6
How reproducible:
Always
Step to Reproduce:
1.Download the virt-p2v iso from brewweb.
2.Configured /usr/bin/virt-p2v-server as:
# Initialize logging
logmsg_init('syslog');
logmsg_level(DEBUG);
# Uncomment these 2 lines to capture debug information from the conversion
# process
$ENV{'LIBGUESTFS_DEBUG'} = 1;
3.Boot the host with virt-p2v from pxe,input the ip and password of conversion server
4.During the conversion of virt-p2v,kill virt-p2v-server process manually.
5.Check the virt-p2v client UI,the data stopped to transfer,but no messages printed as:virt-p2v-server exited.
6.Check /var/log/virt-p2v-server.*.log,there is nothing logged.
Check /var/log/messages,there is no messages logged as"virt-p2v-server exited".
Mar 30 12:56:44 tzheng-linux virt-v2v[3922]: p2v-server started.
Mar 30 12:56:44 tzheng-linux virt-v2v[3922]: Received: LIST_PROFILES
Mar 30 12:56:44 tzheng-linux virt-v2v[3922]: Sent: LIST 3#012rhev-sparse#012rhev-preallocated#012libvirt
Mar 30 12:57:17 tzheng-linux virt-v2v[3922]: Received: SET_PROFILE libvirt
Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Sent: OK
Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Received: METADATA 207
Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Read 207 bytes
Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Sent: OK
Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Received: PATH 16106127360 /dev/xvda
Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Pool: $VAR1 = bless( do{\(my $o = 32174736)}, 'Sys::Virt::StoragePool' );
Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Sent: OK
Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Received: CONTAINER RAW
Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Sent: OK
Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Received: DATA 16106127360
Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Read 4194304 bytes
Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Read 4194304 bytes
Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Read 4194304 bytes
Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Read 4194304 bytes
Mar 30 12:57:19 tzheng-linux virt-v2v[3922]: Read 4194304 bytes
Actual Results:
virt-p2v client has no messages prompted and no messages logged.
Expected Results:
There should be some messages prompted and it should be logged.
Additional info:
Comment 2RHEL Program Management
2012-05-03 04:48:51 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 3Richard W.M. Jones
2015-03-12 17:44:29 UTC
I'm closing this bug:
- virt-p2v has been rewritten for RHEL 7.2
- Unofficial previews of the new version are available:
http://oirase.annexia.org/virt-p2v/
- If a similar bug occurs with the new version of virt-p2v,
please open a new bug against Red Hat Enterprise Linux 7 / libguestfs
Description of Problem: When kill virt-p2v-server process during conversion of virt-p2v,the client has no messages prompted and no messages logged Version-Release number of selected component: virt-v2v-0.8.7-4.el6.x86_64 rubygem-virt-p2v-0.8.6-2.el6 How reproducible: Always Step to Reproduce: 1.Download the virt-p2v iso from brewweb. 2.Configured /usr/bin/virt-p2v-server as: # Initialize logging logmsg_init('syslog'); logmsg_level(DEBUG); # Uncomment these 2 lines to capture debug information from the conversion # process $ENV{'LIBGUESTFS_DEBUG'} = 1; 3.Boot the host with virt-p2v from pxe,input the ip and password of conversion server 4.During the conversion of virt-p2v,kill virt-p2v-server process manually. 5.Check the virt-p2v client UI,the data stopped to transfer,but no messages printed as:virt-p2v-server exited. 6.Check /var/log/virt-p2v-server.*.log,there is nothing logged. Check /var/log/messages,there is no messages logged as"virt-p2v-server exited". Mar 30 12:56:44 tzheng-linux virt-v2v[3922]: p2v-server started. Mar 30 12:56:44 tzheng-linux virt-v2v[3922]: Received: LIST_PROFILES Mar 30 12:56:44 tzheng-linux virt-v2v[3922]: Sent: LIST 3#012rhev-sparse#012rhev-preallocated#012libvirt Mar 30 12:57:17 tzheng-linux virt-v2v[3922]: Received: SET_PROFILE libvirt Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Sent: OK Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Received: METADATA 207 Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Read 207 bytes Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Sent: OK Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Received: PATH 16106127360 /dev/xvda Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Pool: $VAR1 = bless( do{\(my $o = 32174736)}, 'Sys::Virt::StoragePool' ); Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Sent: OK Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Received: CONTAINER RAW Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Sent: OK Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Received: DATA 16106127360 Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Read 4194304 bytes Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Read 4194304 bytes Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Read 4194304 bytes Mar 30 12:57:18 tzheng-linux virt-v2v[3922]: Read 4194304 bytes Mar 30 12:57:19 tzheng-linux virt-v2v[3922]: Read 4194304 bytes Actual Results: virt-p2v client has no messages prompted and no messages logged. Expected Results: There should be some messages prompted and it should be logged. Additional info: