Bug 2051394
| Summary: | Missing error message of 'insufficient free space in the conversion server temporary directory' | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Xiaodai Wang <xiaodwan> |
| Component: | virt-v2v | Assignee: | Richard W.M. Jones <rjones> |
| Status: | CLOSED ERRATA | QA Contact: | tingting zheng <tzheng> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 9.0 | CC: | juzhou, lersek, mxie, rjones, tyan, tzheng, vwu |
| Target Milestone: | rc | Keywords: | Automation |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virt-v2v-1.45.98-1.el9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-17 13:42:09 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: | |||
| Deadline: | 2022-02-21 | ||
|
Description
Xiaodai Wang
2022-02-07 07:59:29 UTC
This is a regression caused by dropping some code when modularising virt-v2v. 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. Repeat the testing in comment 3 with latest virt-v2v version, clear error information is printed. So move the bug to VERIFIED. 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 |