Created attachment 361289 [details] post section Description of problem: system is not registered to satellite after successful ks, hald stop in %post Version-Release number of selected component (if applicable): Satellite-5.3.0-RHEL5-re20090820.1 & updated architecture specific: ia64 How reproducible: always Steps to Reproduce: 1. create kickstart rhel54Server ia64 2. system is not registered after successful ks Actual results: kickstart contains in %post section: /etc/init.d/messagebus restart /etc/init.d/haldaemon restart % post section from /root/ks-post.log Stopping system message bus: [FAILED]^M Starting system message bus: [ OK ]^M Stopping HAL daemon: [FAILED]^M Starting HAL daemon: [FAILED]^M haldaemon is not started in %post for some reason Expected results: hal daemon starts in %post Additional info: its the same like bug 518342 but hald doesnt start on each ia64 what I tried.
Created attachment 361297 [details] kickstart for ia64
last action written in Satellite kickstart status is Last File Requested: /Server/Deployment_Guide-en-US-5.2-11.noarch.rpm kickstart status doesn't recognize that its already finished and Deployment_Guide-en-US-5.2-11.noarch.rpm was last downloaded package up to /root/install.log
So, I did a bunch of testing on this, and found it is unique to ia64, and it has this behavior for every ia64 system I tried. As a result, I'm going to say that this is not a Satellite bug, and instead is either a HAL or Anaconda bug. I'm going to flip it to HAL first, and if it needs to go to Anaconda, so be it. However, because 5.4 does in fact install (even though it does not register), the kickstart tree is clean. [root@test02-ia64 ~]# grep -i hal ks-post.log Stopping HAL daemon: [FAILED] Starting HAL daemon: [FAILED] Introspect error: The name org.freedesktop.Hal was not provided by any .service files Introspect error: The name org.freedesktop.Hal was not provided by any .service files
Please see Bug 495680 - CRM #1900142 hald & dbus-daemon stopped in %post of RHEL5 installations for more information.
(In reply to comment #0) > % post section from /root/ks-post.log > Stopping system message bus: [FAILED]^M > Starting system message bus: [ OK ]^M > Stopping HAL daemon: [FAILED]^M > Starting HAL daemon: [FAILED]^M This looks to me like the messagebus is crashing soon after start. Does 'dbus-monitor' work after you've restarted messagebus, or does it print a warning? Also, if dbus is working as expected, can you please attach the complete output of: killall -9 hald /usr/sbin/hald --verbose=yes --daemon=no Thanks. Richard.
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).