Bug 1044895

Summary:	[hosted engine] - TEXT - 'screen' in installation dialogue is not specific enough
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Pavel Stehlik <pstehlik>
Component:	ovirt-hosted-engine-setup	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED ERRATA	QA Contact:	movciari
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	aberezin, aburden, dfediuck, iheim, oschreib
Target Milestone:	---	Keywords:	EasyFix, ZStream
Target Release:	3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:	ovirt-3.4.0-alpha1	Doc Type:	Bug Fix
Doc Text:	* The recommendation to use a screen session for users executing the self-hosted engine deployment script via a SSH connection has been updated to improve lucidity.	Story Points:	---
Clone Of:
Clones:	1046146 (view as bug list)		Environment:
Last Closed:	2014-06-09 14:47:43 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:
Bug Blocks:	1046146, 1078909, 1142926

Description Pavel Stehlik 2013-12-19 08:23:46 UTC

Description of problem:
This BZ is about ppl who never heard about command 'screen', but rather have 2 screens on their table and running PuTTY. See msg below:

" It has been detected that this program is executed through an SSH connection without using screen.
 Continuing with the installation may lead to broken installation if the network connection fails.
 It is highly recommended to abort the installation and run it inside a screen session."

Proposal:
"...using command 'screen'."


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

How reproducible:
100%

Steps to Reproduce:
1. hosted-engine --deploy
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Sandro Bonazzola 2013-12-23 07:53:04 UTC

Merged on upstream master branch for 3.4.0 rebase.

Comment 6 errata-xmlrpc 2014-06-09 14:47:43 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-0505.html