Bug 1721673

Summary:	after the undercloud installation finishes, the command line is left in a broken state
Product:	Red Hat OpenStack	Reporter:	Alex Schultz <aschultz>
Component:	python-tripleoclient	Assignee:	Alex Schultz <aschultz>
Status:	CLOSED ERRATA	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	high	Docs Contact:
Priority:	high
Version:	15.0 (Stein)	CC:	hbrock, jslagle, mburns
Target Milestone:	beta	Keywords:	Triaged
Target Release:	15.0 (Stein)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-tripleoclient-11.4.1-0.20190628190406.7d41f81.el8ost	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-21 11:23:21 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:

Description Alex Schultz 2019-06-18 20:38:39 UTC

Description of problem:
After installing the undercloud, the user's shell is left in a broken state such that a user needs to run a reset to be able to see what's being typed. This is likely caused by podman or ansible eating escape sequences during the installation.

Version-Release number of selected component (if applicable):


How reproducible:
Every time

Steps to Reproduce:
1. Run undercloud install to completion
2. attempt to type something on the command line
3.

Actual results:
The user's input is not shown and line breaks are ignored

Expected results:
Normal user input should appear

Additional info:

Comment 1 Alex Schultz 2019-06-18 20:39:54 UTC

A workaround is to run 'reset' after the installation.

Comment 5 Sasha Smolyak 2019-07-21 12:08:26 UTC

Fixed. Verified

Comment 9 errata-xmlrpc 2019-09-21 11:23:21 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.

https://access.redhat.com/errata/RHEA-2019:2811