Bug 1056572
| Summary: | [host-deploy] terminate event is not received by engine although sent by host | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | ovirt-engine | Assignee: | Alon Bar-Lev <alonbl> |
| Status: | CLOSED ERRATA | QA Contact: | Tareq Alayan <talayan> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.2.0 | CC: | aberezin, acathrow, adahms, alonbl, bazulay, emesika, gklein, iheim, lpeer, pkliczew, pstehlik, Rhev-m-bugs, yeylon |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 3.3.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | infra | ||
| Fixed In Version: | is34 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, apache-sshd would not flush streams or close streams after a command had been executed. This would result in data not being written to stream readers. With this update, the flush action has been made explicit, making it possible to correctly write data.
|
Story Points: | --- |
| Clone Of: | 1051035 | Environment: | |
| Last Closed: | 2014-03-03 13:31:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1051035 | ||
| Bug Blocks: | |||
|
Comment 2
Tareq Alayan
2014-02-06 15:50:35 UTC
(In reply to Tareq Alayan from comment #2) > Can you please help in how to verify this fix? I have no idea! I have not succeeded in reproducing that on my setup. I can only guess that the chance is higher as the communication between engine and host is faster, same host is best... Please note that this issue exists in 3.2 as well, and we got no confirmed customer report regarding it. moved to verified. Ran automatic sanity test on with no problems. no clear way to reproduce manually, 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-0227.html |