Bug 1215612 - Upgrading to Satellite 6.1 from 6.0.4 cause kernel panic
Summary: Upgrading to Satellite 6.1 from 6.0.4 cause kernel panic
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Other
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-27 09:54 UTC by jnikolak
Modified: 2017-02-23 20:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-28 04:14:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
kernel_panic (20.04 KB, image/png)
2015-04-27 09:54 UTC, jnikolak
no flags Details

Description jnikolak 2015-04-27 09:54:07 UTC
Created attachment 1019286 [details]
kernel_panic

The satellite upgrade completed, but after a reboot, I receive a panic

I was following this guide here 
--> https://access.redhat.com/solutions/1351933 


The upgrade also generated three set of errors.

When I tried to start mongod
- 1) errors -> http://pastebin.test.redhat.com/278964
- 2) I then logged out of ssh and logged back in started mongod and went through this document here -> https://access.redhat.com/solutions/1351933 
This generated errors here 
--> http://pastebin.test.redhat.com/278944

- 3) I then rebooted the satellite server and noticed a kernel panic
Before I rebooted I was able to get login screen and confirmed i was upgraded to 6.1.0 from 6.0.4 

Kernel panic - not synching: VFS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper Not tainted 2.6.32-504.16.2.el6.x86_64

Call Trace:
See screenshot

Comment 1 RHEL Program Management 2015-04-27 10:03:23 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 jnikolak 2015-04-28 04:14:34 UTC
closing bug, because we found that booting from older kernel

2.6.32-504.3.3 resolved the issue.
2.6.32.504.15 was creating the kernel panic.


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