Red Hat Bugzilla – Bug 491978
Kickstarts do not report status via WebUI past 'Reboot System' step
Last modified: 2009-09-10 14:15:16 EDT
Description of problem:
If a user initiates a kickstart on a 530 Satellite, the WebUI will not report status past the "Reboot System" step, though the kickstart will proceed, downloading packages and the like.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a kickstart profile
2. Kickstart a system with the WebUI, using this profile
3. Watch the session status
Session status does not proceed past "Reboot System" step, though the kickstart process proceeds to steps which produce status appropriately
Session status advances to appropriate steps upon new status updates from anaconda
Upon further testing, it appears that the kickstart process itself does not proceed, receiving 404 errors when anaconda attempts to retrieve the KS file and packages. Furthermore, errors appear in catalina.out, which has been attached.
mmccune believes that these additional problems are all part of the issue initially reported, so I'm aligning this bug to sat530-qa-blockers and 472595.
Spacewalk 0.5 released.
Stage validated with Satellite 5.3.0 Gold and RHEL 5.3 kickstart, channel synced from hosted.
After the "Reboot System" item with a check and after packages are installed, "Register system to RHN Satellite" and "Kickstart complete" items get a green check as well.
Moving to RELEASE_PENDING.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.