[rhos-list] Foreman Host Provisioning fails looking for vmlinuz

Crag Wolfe cwolfe at redhat.com
Tue Jul 23 16:09:13 UTC 2013


On 07/19/2013 08:28 AM, Chris Lunsford (clunsfor) wrote:
> Hi.
> I'm trying out the Foreman Technology Preview and am running into an issue with the host provisioning.
>
> The soon-to-be controller node boots and receives an IP address from foreman and pulls its pxelinux file.  But it fails with this error:
> "Could not find kernel image: boot/RedHat-6.4-x86_64-vmlinuz".
>
> The file is present, but appears to be empty:
>
> [root at rhos-foreman boot]# pwd
> /var/lib/tftpboot/boot
> [root at rhos-foreman boot]# ls -al
> total 8
> drwxr-xr-x. 2 foreman-proxy root 4096 Jul 19 09:49 .
> drwxr-xr-x. 4 root          root 4096 Jul 18 16:18 ..
> -rw-r--r--. 1 root          root    0 Jul 19 09:49 RedHat-6.4-x86_64-initrd.img
> -rw-r--r--. 1 root          root    0 Jul 19 09:49 RedHat-6.4-x86_64-vmlinuz
> [root at rhos-foreman boot]#
>
> Was this an error in the configuration process, or am I supposed to supply these files myself?
>
> Thanks,
> Chris Lunsford
>

Those files get written/pulled down after you specify your RHEL 64 
installation media in the Foreman UI (More->Provisioning->Installation 
Media) -- you should not write them to the filesystem yourself.  So, it 
looks like for whatever reason, it could not find those files in the 
right subdir (I think images/pxeboot/) of the http/nfs/ftp path you 
provided.  I'd start looking there.

--Crag




More information about the rhos-list mailing list