Bug 1377810 - AMI RHEL-7.3_HVM_Beta-20160819 kernel panic with some instance types
Summary: AMI RHEL-7.3_HVM_Beta-20160819 kernel panic with some instance types
Keywords:
Status: CLOSED DUPLICATE of bug 1377988
Alias: None
Product: Cloud Image Validation
Classification: Red Hat
Component: images
Version: RHEL7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vratislav Hutsky
QA Contact: Vratislav Hutsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-20 16:16 UTC by Vratislav Hutsky
Modified: 2016-09-29 11:02 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-29 11:02:30 UTC
Target Upstream Version:


Attachments (Terms of Use)
system log of instance that won't boot (63.86 KB, text/plain)
2016-09-20 16:16 UTC, Vratislav Hutsky
no flags Details

Description Vratislav Hutsky 2016-09-20 16:16:24 UTC
Created attachment 1202961 [details]
system log of instance that won't boot

Description of problem:

AMI RHEL-7.3_HVM_Beta-20160819-x86_64 will not boot because of "Kernel panic - not syncing: Fatal exception". 

The problem only occurs with two instance types:
m3.large
c3.large

I gave it a try in four regions, the results were the same in all of them, wherever I used either m3.large or c3.large, the instance wouldn't boot.

How reproducible:
always

Steps to Reproduce:
1. Launch an instance of ami-5dff9c4a in US East region, select either m3.large or c3.large as Instance Type.
2. The instance won't pass internal Status Checks and will not be reachable. 
3. The system log says kernel panic, see attached log file.

Actual results:
The instance fails to boot.

Expected results:
The instance boots as normal.

Comment 1 Vratislav Hutsky 2016-09-29 11:02:30 UTC

*** This bug has been marked as a duplicate of bug 1377988 ***


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