Bug 629519 - Kickstart installs fail with kernel panic when mounting /mnt/sysimage
Summary: Kickstart installs fail with kernel panic when mounting /mnt/sysimage
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Spacewalk
Classification: Community
Component: Release
Version: 1.1
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jan Pazdziora
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space16
TreeView+ depends on / blocked
 
Reported: 2010-09-02 07:51 UTC by Claus
Modified: 2018-11-14 13:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-02 12:23:23 UTC
Embargoed:


Attachments (Terms of Use)
screenshot of the kernel pacic and kickstart file used (621.46 KB, application/zip)
2010-09-02 07:51 UTC, Claus
no flags Details

Description Claus 2010-09-02 07:51:25 UTC
Created attachment 442559 [details]
screenshot of the kernel pacic and kickstart file used

Description of problem:
Kickstart installs fail with kernel panic when mounting /mnt/sysimage
Tried different kickstart files, and also different boot options.
To get a readable error output, for the attached screenshot, I used this boot options:
nousbstorage selinux=0 noapic nmi_watchdog=1 ks=http:/....

I tested it on an esx server, an lenovo t5000 laptop and an HP 8100 workstations. All faild with the same error. Blanc installation with the install dvd works on all tested hw versions.
Also installation from a second spacewalk server, running v1.0 works.

the spacewalk server is a fresh, blank installation.
Tried to install:
rehl 5.5 32bit client
rhel 5.5 64bit client
centos 5.5 32bit
centos 5.5 64bit
centos 5.4 32bit

Version-Release number of selected component (if applicable):
spacewalk 1.1
oracle-xe 10.2.0.1-1.0
centos 5.5

How reproducible:
deploy a client with kickstart from a fresh installed 1.1 spacewalk server

Steps to Reproduce:
1.install spacewalk. 
2.create channels for rhel5.5 client 32bit
3.create a kickstart for installation. (defaut settings are fine)
4.boot a client with install disk and boot with the ks= option to utilize kickstart and spacewalk.
  
Actual results:
client panics

Expected results:
client installs

Additional info:

Comment 1 Jan Pazdziora 2010-10-27 08:32:17 UTC
Mass-aligning under space12, so that we don't lose track of this bugzilla. This however does not mean that we plan (will be able to) address this bug in Spacewalk 1.2.

Comment 2 Jan Pazdziora 2010-11-19 16:02:48 UTC
Mass-moving to space13.

Comment 3 Jan Pazdziora 2011-02-28 18:33:17 UTC
Taking.

Comment 4 Jan Pazdziora 2011-02-28 18:36:09 UTC
I am afraid there is not much we can do to help, on Spacewalk's side. Once the machine started to kickstart, we are really in the realm of the operating system booting.

What happens if you try to boot the virtual machine from CD/DVD device, for example?

Comment 5 Claus 2011-03-01 09:48:32 UTC
(In reply to comment #4)
> I am afraid there is not much we can do to help, on Spacewalk's side. Once the
> machine started to kickstart, we are really in the realm of the operating
> system booting.
> 
> What happens if you try to boot the virtual machine from CD/DVD device, for
> example?

Hi Jan!
Installing the VM with the ISO works.
Can then join the server and work with it.
Cheers
 Claus

Comment 6 Miroslav Suchý 2011-04-11 07:31:22 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 7 Miroslav Suchý 2011-04-11 07:36:23 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 8 Jan Pazdziora 2011-07-20 11:48:47 UTC
Aligning under space16.

Comment 9 Jan Pazdziora 2011-08-19 11:31:28 UTC
(In reply to comment #0)

> 4.boot a client with install disk and boot with the ks= option to utilize
> kickstart and spacewalk.

I missed this step in your original bug report.

Can you instead of booting from the install disk kickstart the machine fully from the Spacewalk server, by reprovisioning or PXE booting it?

Also, during the kickstart session that fails, what is in the /var/log/httpd/*_log on the Spacewalk server?

Comment 10 Jan Pazdziora 2011-09-02 12:23:23 UTC
Closing as it looks like the issue is no longer live. Please reopen if you are able to do the reprovisioning and have the logs.

Thank you,

Jan


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