Bug 518308
| Summary: | RHEL 5.4 trees contain RHN client tools linked to broken dbus | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Steve Salevan <ssalevan> |
| Component: | dbus | Assignee: | David Zeuthen <davidz> |
| Status: | CLOSED DUPLICATE | QA Contact: | desktop-bugs <desktop-bugs> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.4 | CC: | chakkerz, mclasen |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-08-19 20:21:31 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** This bug has been marked as a duplicate of bug 495680 *** I've got the same issue and i'm not authorized to see 495680. Any chance there is a resolution? Cheers chakkerz |
Description of problem: If a user kickstarts a machine to RHEL 5.4 using the latest trees available on WebQA, (re)registration to RHN will fail in post-kickstart due to dbus-related issues... from /var/log/up2date: Traceback (most recent call last): File "/usr/sbin/rhnreg_ks", line 216, in ? cli.run() File "/usr/share/rhn/up2date_client/rhncli.py", line 65, in run sys.exit(self.main() or 0) File "/usr/sbin/rhnreg_ks", line 145, in main other = other) File "/usr/share/rhn/up2date_client/rhnreg.py", line 427, in registerSystem auth_dict["smbios"] = hardware.get_hal_smbios() File "/usr/share/rhn/up2date_client/hardware.py", line 874, in get_hal_smbios computer = get_hal_computer() File "/usr/share/rhn/up2date_client/hardware.py", line 760, in get_hal_computer bus = dbus.SystemBus() File "/usr/lib/python2.4/site-packages/dbus/_dbus.py", line 260, in __new__ return Bus.__new__(cls, Bus.TYPE_SYSTEM, use_default_mainloop, private) File "/usr/lib/python2.4/site-packages/dbus/_dbus.py", line 99, in __new__ bus._connection = dbus_bindings.bus_get(bus_type, private) File "dbus_bindings.pyx", line 1692, in dbus_bindings.bus_get dbus_bindings.DBusException: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Version-Release number of selected component (if applicable): RHEL 5.4 How reproducible: Always Steps to Reproduce: 1. Sync a Satellite to the latest RHEL 5.4 tree content 2. Attempt to kickstart a machine to RHEL 5.4 via this Satellite Actual results: Kickstart succeeds but registration fails as above Expected results: Kickstart and registration succeed Additional info: