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.
Bug 1227621 - Log file saved on conversion server even "Enable server-side debugging" is not ticked
Summary: Log file saved on conversion server even "Enable server-side debugging" is no...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs
Version: 7.2
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard: P2V
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-03 07:19 UTC by tingting zheng
Modified: 2015-09-06 08:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-06 08:51:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description tingting zheng 2015-06-03 07:19:50 UTC 
Description:
Log file saved on conversion server even "Enable server-side debugging" is not ticked.

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.Boot host from virt-p2v iso.
2.After virt-p2v client is launched,fill correct conversion server ip,user name and password.
3.After connected to the conversion server,make sure "Enable server-side debugging" is not ticked.
4.When the conversion starts,there is message shows on virt-p2v client:"Log files and ebug information is saved to this directory on the conversion server:/tmp/virt-p2v-****".
5.On conversion server,check under /tmp,there is new log file created.

Actual results：
As description.

Expected results:
If untick "Enable server-side debugging",no log created on conversion server.

Additional info:
Comment 2 Richard W.M. Jones 2015-09-03 15:37:07 UTC 
I suspect there is a bit of confusion here, and this is NOTABUG.

When you tick the box, it enables full debugging information
(ie. 'virt-v2v -v -x').

If the box is NOT ticked, the log is still written, but it won't
contain any debug information.

In any case, I cannot reproduce this bug (upstream, but the relevant
code hasn't changed for a year).  With the box not ticked, I get a
log file:

$ ls -l
total 20
-rw-r--r--. 1 root root    5 Sep  3 16:34 name
-rw-r--r--. 1 root root 1122 Sep  3 16:34 physical.xml
-rw-r--r--. 1 root root    2 Sep  3 16:35 status
-rw-r--r--. 1 root root   29 Sep  3 16:34 time
-rw-r--r--. 1 root root  458 Sep  3 16:35 virt-v2v-conversion-log.txt

but the log file contains only the basic information and no
debugging, which is the expected behaviour.

$ cat virt-v2v-conversion-log.txt
[   0.0] Opening the source -i libvirtxml /tmp/virt-p2v-20150903-laoznquu/physical.xml
[   0.0] Creating an overlay to protect the source from being modified
[   0.5] Opening the overlay
[  74.7] Initializing the target -o local -os /var/tmp
[  74.7] Inspecting the overlay
virt-v2v: error: no root device found in this operating system image.
[...]
Comment 3 tingting zheng 2015-09-06 08:09:19 UTC 
(In reply to Richard W.M. Jones from comment #2)
> I suspect there is a bit of confusion here, and this is NOTABUG.
> 
> When you tick the box, it enables full debugging information
> (ie. 'virt-v2v -v -x').
> 
> If the box is NOT ticked, the log is still written, but it won't
> contain any debug information.
> 
> In any case, I cannot reproduce this bug (upstream, but the relevant
> code hasn't changed for a year).  With the box not ticked, I get a
> log file:
> 
> $ ls -l
> total 20
> -rw-r--r--. 1 root root    5 Sep  3 16:34 name
> -rw-r--r--. 1 root root 1122 Sep  3 16:34 physical.xml
> -rw-r--r--. 1 root root    2 Sep  3 16:35 status
> -rw-r--r--. 1 root root   29 Sep  3 16:34 time
> -rw-r--r--. 1 root root  458 Sep  3 16:35 virt-v2v-conversion-log.txt
> 
> but the log file contains only the basic information and no
> debugging, which is the expected behaviour.
> 
> $ cat virt-v2v-conversion-log.txt
> [   0.0] Opening the source -i libvirtxml
> /tmp/virt-p2v-20150903-laoznquu/physical.xml
> [   0.0] Creating an overlay to protect the source from being modified
> [   0.5] Opening the overlay
> [  74.7] Initializing the target -o local -os /var/tmp
> [  74.7] Inspecting the overlay
> virt-v2v: error: no root device found in this operating system image.
> [...]

I just misunderstood that if tick the box,no log will be wrriten to p2v server.
Pls close it as "NOTABUG".
Comment 4 Richard W.M. Jones 2015-09-06 08:51:15 UTC 
Thanks Tingting - closing per comment 2 & comment 3.
Note You need to log in before you can comment on or make changes to this bug.