Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1058744

Summary:	rhevm-log-collector garbles the tty when multiple hosts are gathered and ssh is called with the "-t" flag
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	ovirt-engine-log-collector	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED ERRATA	QA Contact:	Jiri Belka <jbelka>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.3.0	CC:	acathrow, adahms, iheim, knesenko, kroberts, lyarwood, pprakash, pstehlik, Rhev-m-bugs, yeylon
Target Milestone:	---	Keywords:	Patch, ZStream
Target Release:	3.3.1
Hardware:	All
OS:	Linux
Whiteboard:	integration
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, when the rhevm-log-collector utility was run for multiple hypervisor hosts, it resulted in a garbled TTY and "stty sane" had to be run to recover the TTY. Now, the TTY is not garbled.	Story Points:	---
Clone Of:	1041749	Environment:
Last Closed:	2014-03-03 13:19:00 UTC	Type:	---
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:	1041749
Bug Blocks:

Comment 1 Sandro Bonazzola 2014-01-28 13:22:48 UTC

pushed to upstream 3.3 branch

Comment 2 Sandro Bonazzola 2014-01-28 13:46:24 UTC

Merged on upstream 3.3 branch

Comment 4 Jiri Belka 2014-02-04 13:01:40 UTC

ok, rhevm-log-collector-3.3.1-6.el6ev.noarch

terminal OK after getting info from 2 hosts.

Comment 5 Jiri Belka 2014-02-04 13:02:49 UTC

FYI my engine-log-collector was not putting '-t' in ssh commands, at least I haven't see it.

Comment 6 Sandro Bonazzola 2014-02-04 15:30:18 UTC

(In reply to Jiri Belka from comment #5)
> FYI my engine-log-collector was not putting '-t' in ssh commands, at least I
> haven't see it.

we solved using -n instead of -t.

Comment 8 errata-xmlrpc 2014-03-03 13:19:00 UTC

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-0242.html