Hide Forgot
Description of problem: Drop to shell and return to TUI, then view logs, it's empty and cannot quit the process. Version-Release number of selected component (if applicable): rhev-hypervisor-6.2-0.14 How reproducible: 100%. Steps to reproduce: 1. Drop to shell. 2. Type "setup" return to TUI. 3. Press F2 to view logs. Actual results: log content display empty and cannot quit the process. Expected results: View log successful. Additional info: In a fresh install rhevh, login with admin and press F2 to view log files, can also meet this issue sometimes. but drop to shell and return to TUI will reproduce this issue 100%
I tried this with upgraded 6.2-0.12 to 6.2-0.14 vm and did not encounter this problem. Are there any log files or stack traces?
Talked on IRC and this is reproducible when you've manually run the "setup" command. 1. boot node 2. login as admin 3. F2 4. view log file -- works 5. drop to shell 6. exit 7. view logs -- works 8. drop to shell 9. setup 10. F2 11. view logs -- fails QE will try to reproduce without running setup If it's just running setup, then perhaps we should disallow running setup manually? I don't see a use case for running setup manually
Created attachment 520106 [details] less Did some testing: 1. fresh install rhevh 2. login with admin 3. view log is fine 4. drop to shell and exit, view log is fine 5. drop to shell and run setup, view log hit the issue. so only manually run setup have this issue. Another testing is: 1. fresh install rhevh 2. login with admin 3. drop to shell. 4. #less /var/log/ovirt.log, screen is mess, see attachment.
NACK -- see https://www.redhat.com/archives/ovirt-devel/2011-August/msg00061.html
Tested on 6.2-0.15: drop to shell and manual run "setup", it display "Unable to run setup manually, Run \"exit\" to return to setup" now, this is ok. But `less /var/log/ovirt.log` also display "Unable to run setup manually, Run \"exit\" to return to setup", this should be still a problem.
Verified on 6.2-0.16.2: 1. view logs is ok after press F10. 2. drop to shell, `less /var/log/ovirt.log` is ok. 3. drop to shell, manual run "setup" is prevented and given a proper warning.
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-2011-1783.html