Created attachment 455939 [details] PXE booting failure Description of problem: Once the system gets provisioned through Satellite UI kickstarting, there is prepared a system record (you can see it: "cobbler system list") which is syncing "accordingly" by cobbler sync to the /tftpboot/pxelinux.cfg/<system-MAC> and so later on PXE booting of that system (PXE server is our satellite) becomes impossible. Looking at the file: /tftpboot/pxelinux.cfg/01-54-52-00-40-d4-a8 one can see: --- DEFAULT local PROMPT 0 TIMEOUT 0 TOTALTIMEOUT 0 ONTIMEOUT local LABEL local LOCALBOOT 0 --- Not sure if this is the problem there or not. Version-Release number of selected component (if applicable): Recent Satellite 5.4.0 stage-signed ISO: Satellite-5.4.0-RHEL5-re20101025.0 How reproducible: from 2 attempts Steps to Reproduce: 0. make your network settings be configured to have the satellite as PXE server. 1.on registered system perform all necessary actions for preparing it to be provisioned (Provisioning entitlement, tools channel, appropriate ks profile, etc) 2. Provision that system by the prepared ks profile. 3. run rhn_check -vvv, wait until system gets provisioned 4. change boot mode to network. reboot Actual results: System falls in infinite loop of retrieving that pxelinux.cfg/01-54-52-00-40-d4-a8 When the "cobbler system remove --name=<systemname>; cobbler sync" runs, the booting issue resolves and system could be entered into the PXE menu and choose the provisioning profiles, etc. Expected results: PXE booting should be possible for the systems that had UI provisioned. Additional info: See attachment. Easy to reproduce on virtual systems, where on the host-side dhcpd server is setup and the next-server is redirected to the satellite.