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.

Bug 980338

Summary: disk-format "qemu-img info: JSON parse error" when target file does not exist
Product: Red Hat Enterprise Linux 7 Reporter: bfan
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: leiwang, wshi
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libguestfs-1.22.4-2.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 980337 Environment:
Last Closed: 2014-06-13 12:15:21 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:
Bug Depends On: 981663    
Bug Blocks:    

Description bfan 2013-07-02 06:19:32 UTC
+++ This bug was initially created as a clone of Bug #980337 +++

Description of problem:
disk-format does not give an error when the file is inexistent


Version-Release number of selected component (if applicable):
libguestfs-1.20.9-6.el6.x86_64


How reproducible:
100%


Steps to Reproduce:
[root@]# guestfish -N fs mount /dev/sda1 / : list-partitions : disk-format /dev/sda2 : disk-format /dev/sda3
/dev/sda1
raw
libguestfs: error: realpath: No such file or directory



Actual results:
disk-format /dev/sda2 , returns "raw"


Expected results:
"disk-format /dev/sda2" should give a error message as "disk-format /dev/sda3"


Additional info:
also effect "disk-virtual-size"

Comment 1 Richard W.M. Jones 2013-07-05 12:38:56 UTC
Let's reuse this bug to fix the somewhat related problem:

$ guestfish disk-format /etc/nosuchfile
libguestfs: error: qemu-img info: JSON parse error: parse error: premature EOF
                                       
                     (right here) ------^

libguestfs: error: qemu-img info: /etc/nosuchfile: qemu-img info exited with error status 1.
To see full error messages you may need to enable debugging.
See http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs

Comment 4 bfan 2013-12-02 05:33:39 UTC
Verified with libguestfs-1.22.6-16.el7.x86_64

# guestfish disk-format /etc/nosuchfile
libguestfs: error: disk info: /etc/nosuchfile: No such file or directory

It gives a correct error message, change the status to verified

Comment 5 Ludek Smid 2014-06-13 12:15:21 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.