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"
D, [2013-05-14T09:47:47.630120 #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/initrd.img -O "/var/lib/tftpboot/boot/CentOS-6.4-x86_64-initrd.img"
E, [2013-05-14T09:47:49.109974 #5938] ERROR - : [7446] 2013-05-14 09:47:49 URL:http://gedainst/osmirror/Linux/CentOS/6.4/os/x86_64/images/pxeboot/vmlinuz [4043888/4043888] > "/var/lib/tftpboot/boot/CentOS-6.4-x86_64-vmlinuz" [1]
E, [2013-05-14T09:47:50.558610 #5938] ERROR - : [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]

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

thats odd, please do md5 checksum to validate

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

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

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.

Hi,

thanks for testing.

I used a VMWare Vsphere 5.0 VM and a bare metal IBM eSeries x366.

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