Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

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.

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.