Bug 1135105
| Summary: | Should send data message for file copy of 0 size | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Marc-Andre Lureau <marcandre.lureau> |
| Component: | mingw-virt-viewer | Assignee: | Default Assignee for SPICE Bugs <rh-spice-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | SPICE QE bug list <spice-qe-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.6.0 | CC: | cfergeau, dblechte, desktop-qa-list, djasa, fidencio, gklein, rbalakri, rh-spice-bugs, sherold, tjamrisk, tpelka, victortoso, yeylon, ykaul, ylavi |
| Target Milestone: | ovirt-3.6.0-rc | ||
| Target Release: | 3.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | mingw-virt-viewer-2.0-1.el7ev | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the SPICE client did not send a data message when transferring zero-sized files by drag and drop. Because the guest agent expects to receive a message, it would keep a file open, causing a leak. This has been fixed by adding a transfer message for zero-sized files to prevent guests from leaking file descriptors in the guest agent during the copy.
|
Story Points: | --- |
| Clone Of: | 1135099 | Environment: | |
| Last Closed: | 2016-03-09 20:08:59 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Spice | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1135099, 1181289 | ||
| Bug Blocks: | |||
|
Description
Marc-Andre Lureau
2014-08-28 20:07:51 UTC
Well-known problem, qa_ack+ If this bug requires doc text for errata release, please provide draft text in the doc text field in the following format: Cause: Consequence: Fix: Result: I'm sorry Dayle, we as QE are not responsible for filling doc text. 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/RHEA-2016-0377.html |