Created attachment 890340 [details] run without tar file Description of problem: tar-in-opts execute failed when give a nonexistent directory path, then correct the path, but libguestfs appliance crashed. Version-Release number of selected component (if applicable): libguestfs-1.22.6-22.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. tar file dose not exist # guestfish -N fs -m /dev/sda1 tar-in-opts test.tar /test : tar-in-opts test.tar / libguestfs: error: open: test.tar: No such file or directory libguestfs: error: appliance closed the connection unexpectedly. This usually means the libguestfs appliance crashed. See http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs for information about how to debug libguestfs and report bugs. # the whole log is attached(run.log) 2. tar file exist # guestfish -N fs -m /dev/sda1 tar-in-opts test.tar /test : tar-in-opts test.tar / libguestfs: error: tar_in: /test: No such file or directory libguestfs: error: check_daemon_socket: read 0x44 from daemon, expected 0xffffeeee. Lost protocol synchronization (bad!) Actual results: libguestfs appliance closed Expected results: Only command execute failed, libguestfs appliance is alive Additional info: Same Problem exist in rhel6, although there is no libguestfs error message printed, appliance is not in running state. libguestfs-1.20.11-2.el6.x86_64
Patches posted: https://www.redhat.com/archives/libguestfs/2014-April/msg00077.html https://www.redhat.com/archives/libguestfs/2014-April/msg00078.html
Upstream fix: efd159a063410b3d9d13814222abed231ec42f90 Regression test: 50b207ca459a205efeec613ab04ff4c39dc6bee2 Leaving in POST state because this bug is open against RHEL.
Version: libguestfs-1.28.1-1.9.el7.x86_64 #guestfish -N fs -m /dev/sda1 tar-in-opts test.tar /test : tar-in-opts test.tar / Didn't crash. 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, 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://rhn.redhat.com/errata/RHBA-2015-0303.html