Bug #2496
closed
CentOS deployment is not working. Kernel Panic on starting deploy machine
Description
Hi,
I have already asked in the irc channel but no one really had a clue what could be the cause for this. I have tried to deploy CentOS 6.2 and 6.4 on a virtual (VMWare) and a bare metal host. Both show a kernel panic on startup. Installing CentOS from CD works fine. I have done a fresh install of foreman 1.1 and compared the provisioning templates they are the same. Maybe something on my production install is messed up?
Updated by Ohad Levy almost 11 years ago
- Status changed from New to Feedback
this sounds like a broken kernel / initrd, try removing the files from your tftp dir /tftpboot/boot/centos-..?
they would be auto fetched when toggling build.. if your mirror is slow, it might be that your machine will fetch the files prior to finishing the download, (only for the first time when you add the new os), so check that there are no more wget processes running on that machine.
Updated by Oliver Weinmann almost 11 years ago
Hi,
that's what I thought too. I have deleted the files under /var/lib/tftpboot/boot and changed to our local mirror. The kernel panic doesn't appear on the first boot, but on the first boot after the machine is deployed.
By the way the foreman-proxy log is always displaying an error for the download of the initrd and kernel:
D, [2013-05-14T09:47:47.574117 #5938] DEBUG -- : Starting task (total: 0): wget --timeout=10 --tries=3 --no-check-certificate nv -c http://gedainst/osmirror/Linux/CentOS/6.4/os/x86_64/images/pxeboot/vmlinuz -O "/var/lib/tftpboot/boot/CentOS-6.4-x86_64-vmlinuz" : Starting task (total: 0): wget --timeout=10 --tries=3 --no-check-certificate
D, [2013-05-14T09:47:47.630120 #5938] DEBUG -nv -c http://gedainst/osmirror/Linux/CentOS/6.4/os/x86_64/images/pxeboot/initrd.img -O "/var/lib/tftpboot/boot/CentOS-6.4-x86_64-initrd.img" : [7446] 2013-05-14 09:47:49 URL:http://gedainst/osmirror/Linux/CentOS/6.4/os/x86_64/images/pxeboot/vmlinuz [4043888/4043888]
E, [2013-05-14T09:47:49.109974 #5938] ERROR -> "/var/lib/tftpboot/boot/CentOS-6.4-x86_64-vmlinuz" [1] : [2640] 2013-05-14 09:47:50 URL:http://gedainst/osmirror/Linux/CentOS/6.4/os/x86_64/images/pxeboot/initrd.img [32495283/32495283] -> "/var/lib/tftpboot/boot/CentOS-6.4-x86_64-initrd.img" [1]
E, [2013-05-14T09:47:50.558610 #5938] ERROR -
but the files are successfully downloaded:
root@gedadvl06:/var/lib/tftpboot/boot# du -sh *
31M CentOS-6.4-x86_64-initrd.img
3.9M CentOS-6.4-x86_64-vmlinuz
Regards,
Oliver
Updated by Ohad Levy almost 11 years ago
thats odd, please do md5 checksum to validate
Updated by Oliver Weinmann almost 11 years ago
They are identical. :(
root@gedadvl06:/var/lib/tftpboot/boot# md5sum CentOS-6.4-x86_64-vmlinuz
e390e699cfbfcbf6603e7e80aaf40853 CentOS-6.4-x86_64-vmlinuz
root@gedadvl06:/var/lib/tftpboot/boot# md5sum CentOS-6.4-x86_64-initrd.img
1c7d04190b27858e1b8abc9866cf359f CentOS-6.4-x86_64-initrd.img
root@gedadvl06:/var/lib/tftpboot/boot# md5sum CentOS-6.4-x86_64-vmlinuz
e390e699cfbfcbf6603e7e80aaf40853 CentOS-6.4-x86_64-vmlinuz
boot# md5sum initrd.img
1c7d04190b27858e1b8abc9866cf359f initrd.img
root@gedappl01:/mnt/ds-san-02/vol/osmirror/Linux/CentOS/6.4/os/x86_64/images/pxeboot# md5sum vmlinuz
e390e699cfbfcbf6603e7e80aaf40853 vmlinuz
Updated by Oliver Weinmann almost 11 years ago
Hi,
can you confirm that this is not a bug and really a configuration problem on my end?
i.e. can you please try to deploy a centos 6.2 / 6.4 box?
Best Regards,
Oliver
Updated by Greg Sutcliffe almost 11 years ago
I just built a CentOS 6.4 machine with no issues, using the default Foreman Kickstart. I used this mirror:
http://anorien.csc.warwick.ac.uk/mirrors/centos/$major.$minor/os/$arch
And my installer md5sums are:
1c7d04190b27858e1b8abc9866cf359f /var/lib/tftpboot/boot/Centos-6.4-x86_64-initrd.img e390e699cfbfcbf6603e7e80aaf40853 /var/lib/tftpboot/boot/Centos-6.4-x86_64-vmlinuz
So we have the same md5sums - what platform are you installing on? I was using a Libvirt KVM machine, for the record.
Updated by Oliver Weinmann almost 11 years ago
Hi,
thanks for testing.
I used a VMWare Vsphere 5.0 VM and a bare metal IBM eSeries x366.
Updated by Oliver Weinmann almost 11 years ago
Hi,
can you send me the contents of your partitioning template?
I just deployed on a third host and I saw some debug messages coming up... Maybe my partitioning template is wrong?
Best Regards,
Oliver
Updated by Oliver Weinmann almost 11 years ago
- Status changed from Feedback to Closed
I have once more copy and pasted the prov template from a fresh install and now it works. :)
Sorry for the confusion.