Description of problem: Let's assume there is a Fedora system (for my case x86_64) registered to the SW. And there is setup PXE booting for that system to load from that specific SW. (cobbler sync, tftp settings, the stuff needed to make SW to serve PXE provisining) Having F13 channel with all kickstart stuff there (ks distribution, profile) the initiation of another re-provisioning with the same release/arch hangs up on installation phase "Running pre-install scripts" *** the issue is: when i remove the /usr/share/rhn/systemid (force unregister the system) , re-provisioning just works~~~ *** Version-Release number of selected component (if applicable): SW 1.1 spacewalk-java-1.1.41-1.el5 spacewalk-html-1.1.6-1.el5 spacewalk-oracle-1.1.6-1.el5 spacewalk-schema-1.1.19-1.el5 cobbler-2.0.3.1-3.el5 How reproducible: always (on Fedora x86_64 for my case) Steps to Reproduce: 1. Configure SW 1.1 to server PXE booting 2. Prepare F13 x86_64 channel + kickstart distrib/profile there 3. cobbler sync 4. make registration of F13 x86_64 (through activation key) - that would require to setup rhn-setup package there 5. make the network changes on that F13 to have SW 1.1 as PXE booting server (i did my test on KVM guest by configuring its host's dhcpd configuration) 6. reprovision that system 7. process just hangs up on "running anaconda 13.42, ..." Actual results: impossible to PXE reprovision the system (Fedora tried so far) when it's registered to SW. Expected results: no problem with PXE reprovisioning Additional info:
did tried with RHEL6 - worked. needs to be made a try with F13 too.
just checked once more: the problem still exists for F13.
Mass-moving to space13.
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.
Aligning under space16.
(In reply to comment #0) > 7. process just hangs up on "running anaconda 13.42, ..." So it never even starts the graphical installer?
No, it just hanged on that "black screen" of the "running anaconda"
(In reply to comment #0) > Actual results: > impossible to PXE reprovision the system (Fedora tried so far) when it's > registered to SW. Is this specific to PXE reprovision? In other words, does it also happen when you just schedule the kickstart via Spacewalk's WebUI and do rhn_check on the Fedora box? Isn't this KVM related? If you do this in other virtualization environment and on bare metal, do you see the bug? What is in the Spacewalk httpd log during that kickstart (sans the WebUI accesses)?
I was now able to reprovision Fedora 15 via PXE. Closing as CURRENTRELEASE.