Red Hat Bugzilla – Bug 807714
v7 1.5 R12 requires udisks package not in RHEL5
Last modified: 2015-01-04 18:02:27 EST
Description of problem:
v7 1.5 introduces udisks as a HAL replacement. There is no udisks package in RHEL5
Version-Release number of selected component (if applicable):
If installed ignoring dependancies on udisks, the follow traceback occurs:
[root@dell-pe1950-02 ~]# v7 plan --server gnichols.usersys.redhat.com
found interface for udisks
Introspect error: The name org.freedesktop.UDisks was not provided by any .service files
Traceback (most recent call last):
File "/usr/bin/v7", line 45, in ?
success = v7.do(args)
File "/usr/share/v7/lib/v7/hardwaretest.py", line 194, in do
result = self.commands[self.command]()
File "/usr/share/v7/lib/v7/hardwaretest.py", line 323, in doPlan
tests = self.planner.plan()
File "/usr/share/v7/lib/v7/planner.py", line 114, in plan
File "/usr/share/v7/lib/v7/planner.py", line 129, in __loadDevices
File "/usr/share/v7/lib/v7/udisksDeviceDetector.py", line 49, in getDevices
for devicePath in self.interface.EnumerateDevices():
File "/usr/lib64/python2.4/site-packages/dbus/proxies.py", line 25, in __call__
ret = self._proxy_method (*args, **keywords)
File "/usr/lib64/python2.4/site-packages/dbus/proxies.py", line 102, in __call__
reply_message = self._connection.send_with_reply_and_block(message, timeout)
File "dbus_bindings.pyx", line 455, in dbus_bindings.Connection.send_with_reply_and_block
dbus_bindings.DBusException: The name org.freedesktop.UDisks was not provided by any .service files
Reproduced in v7-1.5-12.el5.noarch and verified in v7-1.5-13.el5.noarch.
Could the code be updated to not list out the introspect error? It seems like maybe the udisk detection is returning true and then failing.
Created attachment 574608 [details]
hardwaretest patch to pass product information into device planning
Created attachment 574609 [details]
planner patch to only use udisks on RHEL 6 and beyond, and all other products
Additional fixes verified in R14.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
no tech note needed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.