Bug 1091805
| Summary: | tar-in-opts execute failed that cause libguestfs appliance crashed | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | bfan |
| Component: | libguestfs | Assignee: | Pino Toscano <ptoscano> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.5 | CC: | huzhan, leiwang, lkong, mbooth, ptoscano, wshi, yuliu |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libguestfs-1.20.11-3.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: Running tar-in guestfish command, or using the tar_in guestfs API, with a non-existing input tar or to a non-existing destination directory.
Consequence: Crash of the libguestfs appliance.
Fix: Improve the error checking.
Result: tar-in cleanly returns an error.
|
Story Points: | --- |
| Clone Of: | 1091803 | Environment: | |
| Last Closed: | 2014-10-14 06:35:16 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: | 1091803 | ||
| Bug Blocks: | |||
|
Description
bfan
2014-04-28 05:53:51 UTC
Upstream fix: efd159a063410b3d9d13814222abed231ec42f90 Regression test: 50b207ca459a205efeec613ab04ff4c39dc6bee2 Leaving in POST state because this bug is open against RHEL. Verified with libguestfs-1.20.11-4.el6.x86_64 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 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 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. http://rhn.redhat.com/errata/RHBA-2014-1458.html |