2051394 – Missing error message of 'insufficient free space in the conversion server temporary directory'

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 2051394 - Missing error message of 'insufficient free space in the conversion server temporary directory'

Summary: Missing error message of 'insufficient free space in the conversion server te...

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Deadline:	2022-02-21
Product:	Red Hat Enterprise Linux 9
Classification:	Red Hat
Component:	virt-v2v
Sub Component:
Version:	9.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	low
Severity:	low
Target Milestone:	rc
Target Release:	---
Assignee:	Richard W.M. Jones
QA Contact:	tingting zheng
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2022-02-07 07:59 UTC by Xiaodai Wang
Modified:	2022-05-17 13:44 UTC (History)
CC List:	7 users (show)
Fixed In Version:	virt-v2v-1.45.98-1.el9
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2022-05-17 13:42:09 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	RHELPLAN-111299	0	None	None	None	2022-02-07 08:10:26 UTC
Red Hat Product Errata	RHEA-2022:2566	0	None	Closed	[BZ] logger from util-linux incorrectly handles long messages	2022-05-27 16:03:59 UTC

Description Xiaodai Wang 2022-02-07 07:59:29 UTC

Description of problem:
Missing error message of 'insufficient free space in the conversion server temporary directory'

Version-Release number of selected component (if applicable):
virt-v2v-1.45.97-3.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Make sure the convertion server has less than 1G disk space.
2. Run virt-v2v command and check the messages.

Actual results:
Not error printed as in RHEL8.
https://github.com/libguestfs/virt-v2v/blob/992af0707ad54d39ec707da6daa6c4ca7c3fc69a/v2v/v2v.ml#L273

Expected results:


Additional info:

Comment 1 Richard W.M. Jones 2022-02-07 09:30:35 UTC

This is a regression caused by dropping some code when modularising virt-v2v.

Comment 2 Richard W.M. Jones 2022-02-07 10:11:38 UTC

https://github.com/libguestfs/virt-v2v/commit/18b11018d2c5411693d120add445031758eee5ce

Comment 3 tingting zheng 2022-02-11 09:10:48 UTC

The bug can be reproduced with:
virt-v2v-1.45.97-4.el9 

Steps:
1.Make sure there is not enough space under "/var/tmp".
# df -h /var/tmp
Filesystem                              Size  Used Avail Use% Mounted on
/dev/mapper/rhel_dell--per740--35-root   70G   70G  132M 100% /

2.Use virt-v2v to convert guest.
# virt-v2v -ic vpx://root@$vcenter/data/$esxi/?no_verify=1 -o rhv-upload -of raw -os nfs_data -oc https://$rhv/ovirt-engine/api -op /home/rhvpasswd -oo rhv-cafile=/home/rhv_upload_ca.pem -oo rhv-cluster=NFS -oo rhv-direct --mac 00:50:56:ac:fb:75:network:ovirtmgmt $guest -it vddk -io vddk-libdir=/home/vddk -io vddk-thumbprint=***  -ip /home/passwd
[   1.9] Opening the source
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
[   9.6] Inspecting the source
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
nbdkit: vddk[1]: error: pwrite: No space left on device
virt-v2v: error: inspection could not detect the source guest (or physical 
machine).

Assuming that you are running virt-v2v/virt-p2v on a source which is 
supported (and not, for example, a blank disk), then this should not 
happen.

No root device found in this operating system image.

If reporting bugs, run virt-v2v with debugging enabled and include the 
complete output:

  virt-v2v -v -x [...]


Tested with:
virt-v2v-1.45.98-1.el9.x86_64

Repeat the above command, there is clear error information printed.

# virt-v2v -ic vpx://root@$vcenter/data/$esxi/?no_verify=1 -o rhv-upload -of raw -os nfs_data -oc https://$rhv/ovirt-engine/api -op /home/rhvpasswd -oo rhv-cafile=/home/rhv_upload_ca.pem -oo rhv-cluster=NFS -oo rhv-direct --mac 00:50:56:ac:fb:75:network:ovirtmgmt $guest -it vddk -io vddk-libdir=/home/vddk -io vddk-thumbprint=***  -ip /home/passwd 
virt-v2v: error: insufficient free space in the conversion server temporary 
directory /var/tmp (131.7M).

Either free up space in that directory, or set the LIBGUESTFS_CACHEDIR 
environment variable to point to another directory with more than 1GB of 
free space.

See also the virt-v2v(1) manual, section "Minimum free space check in the 
host".

If reporting bugs, run virt-v2v with debugging enabled and include the 
complete output:

  virt-v2v -v -x [...]

Refer to the above comments,the bug has been fixed, add Verifed:Tested filed.

Comment 7 tingting zheng 2022-02-15 14:20:40 UTC

Repeat the testing in comment 3 with latest virt-v2v version, clear error information is printed.

So move the bug to VERIFIED.

Comment 9 errata-xmlrpc 2022-05-17 13:42:09 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 (new packages: virt-v2v), 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/RHEA-2022:2566

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