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.
(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"
Hi again Liron, Is that ok if we put a message to users about F2 into diagnostic page? What do you say?
Reducing Priority/Severity as we are waiting Liron's response.
Moving pending bugs not fixed in 3.5.0 to 3.5.1.
oVirt 3.5.1 has been released, re-targeting to 3.6.0 as not marked as urgent / high severity or priority
(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.