Bug 621403 - firstboot menu shown in rhevh after reboot
Summary: firstboot menu shown in rhevh after reboot
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node (Show other bugs)
(Show other bugs)
Version: 6.0
Hardware: All Linux
high
medium
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-04 23:03 UTC by Mike Burns
Modified: 2016-04-26 13:59 UTC (History)
4 users (show)

Fixed In Version: ovirt-node-1.9.3-7.3.gitc41536c.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-11 14:52:18 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
patch (848 bytes, patch)
2010-08-09 14:35 UTC, Joey Boggs
no flags Details | Diff

Description Mike Burns 2010-08-04 23:03:34 UTC
Description of problem:
After installing and rebooting rhevh, boot should be to login screen, but instead goes to firstboot menu again.  

Version-Release number of selected component (if applicable):
ovirt-node-1.9.3-6.3.gitc41536c.el6

How reproducible:
always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Workaround by choosing option 11 in firstboot menu after reboot to exit menu

Comment 2 Joey Boggs 2010-08-09 14:35:57 UTC
Created attachment 437613 [details]
patch

Comment 5 Vivian Bian 2010-08-20 16:55:19 UTC
checked with rhev-hypervisor-6.0-12

steps:
1.install RHEVH locally 
2.reboot 


Actual result:
Red Hat Enterprise Virtualization Hypervisor release 6.0 (12.el6)
Kernel 2.6.32-66.el6.x86_64 on an x86_64 (/dev/ttyS0)
localhost.localdomain login: 

There is no firstboot menu whon in rhevh after reboot . So set bug status to VERIFIED

Comment 6 releng-rhel@redhat.com 2010-11-11 14:52:18 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.