Bug 1143861

Summary:	[oVirt-node] can't get out of the menu
Product:	[Retired] oVirt	Reporter:	Liron Aravot <laravot>
Component:	ovirt-node	Assignee:	Douglas Schilling Landgraf <dougsland>
Status:	CLOSED WONTFIX	QA Contact:	bugs <bugs>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.5	CC:	bugs, dfediuck, ecohen, fdeutsch, gklein, laravot, lsurette, mgoldboi, ovirt-bugs, rbalakri, yeylon
Target Milestone:	---
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	node
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1143871 (view as bug list)		Environment:
Last Closed:	2015-02-26 16:12:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Node	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Liron Aravot 2014-09-18 07:33:02 UTC

Description of problem:
Currently it seems like there's no convinient way to get out of the ovirt node menu.
For example, when failing in the hosted engine setup, it's hard to get to the logs. There's no way to get out from the menu to read the logs. So the workaround is to reboot the machine and interrupt the startup to read the log.

How reproducible:
always

Expected results:
should be able to exit from the menu.

Comment 1 Douglas Schilling Landgraf 2014-09-19 01:46:23 UTC

(In reply to Liron Aravot from comment #0)
> Description of problem:
> Currently it seems like there's no convinient way to get out of the ovirt
> node menu.
> For example, when failing in the hosted engine setup, it's hard to get to
> the logs. There's no way to get out from the menu to read the logs. So the
> workaround is to reboot the machine and interrupt the startup to read the
> log.
> 
> How reproducible:
> always
> 
> Expected results:
> should be able to exit from the menu.

Hello Liron,

From menu could you please try to press F2 ? Is it what you expect? 
Might be a good idea to add a string to users with "F2 to rescue shell"

Comment 2 Douglas Schilling Landgraf 2014-09-25 18:13:19 UTC

Hi again Liron,

Is that ok if we put a message to users about F2 into diagnostic page?
What do you say?

Comment 3 Douglas Schilling Landgraf 2014-10-02 18:56:35 UTC

Reducing Priority/Severity as we are waiting Liron's response.

Comment 4 Sandro Bonazzola 2014-10-17 12:14:37 UTC

Moving pending bugs not fixed in 3.5.0 to 3.5.1.

Comment 5 Sandro Bonazzola 2015-01-21 16:08:40 UTC

oVirt 3.5.1 has been released, re-targeting to 3.6.0 as not marked as urgent / high severity or priority

Comment 6 Fabian Deutsch 2015-02-26 16:12:57 UTC

(In reply to Liron Aravot from comment #0)
> Description of problem:
> Currently it seems like there's no convinient way to get out of the ovirt
> node menu.

That is intended, bcause we do not support doing stuff outside the TUI.

> For example, when failing in the hosted engine setup, it's hard to get to
> the logs. There's no way to get out from the menu to read the logs. So the
> workaround is to reboot the machine and interrupt the startup to read the
> log.

Please open a separate bug/rfe toretrieve the informations about a failed HE setup easier.