Bug 881033 - instance won't boot having updated kernel
Summary: instance won't boot having updated kernel
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Cloud Image Validation
Classification: Red Hat
Component: images
Version: RHEL6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: mkovacik
QA Contact: mkovacik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-28 13:16 UTC by mkovacik
Modified: 2013-05-15 08:45 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-15 08:45:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
AWS EC2 messages Screen (64.97 KB, text/plain)
2012-11-28 13:16 UTC, mkovacik
no flags Details

Description mkovacik 2012-11-28 13:16:49 UTC
Created attachment 653516 [details]
AWS EC2 messages Screen

Description of problem:
see summary

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

How reproducible:
always

Steps to Reproduce:
1. instantiate ami-c18c1bfb
2. log-in to hte instance and do yum update -y kernel
3. reboot the instance
4. kernel panic
  
Actual results:
kernel panic: no root device having updated the kernel

Expected results:
kernel-update works as expected

Additional info:
## last few boot-up lines; See the attached log for full AWS EC2 screen

udev: starting version 147
dracut: Starting plymouth daemon
dracut Warning: No root device "block:/dev/disk/by-label/_\x2f" found

dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.


dracut Warning: Signal caught!

dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.32-279.14.1.el6.x86_64 #1
Call Trace:
 [<ffffffff814fd98a>] ? panic+0xa0/0x168
 [<ffffffff81070c42>] ? do_exit+0x862/0x870
 [<ffffffff8117d0a5>] ? fput+0x25/0x30
 [<ffffffff81070ca8>] ? do_group_exit+0x58/0xd0
 [<ffffffff81070d37>] ? sys_exit_group+0x17/0x20
 [<ffffffff8100b0f2>] ? system_call_fastpath+0x16/0x1b


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