Bug 207724 - pirut - traceback with a failed connection to yum-updatesd
pirut - traceback with a failed connection to yum-updatesd
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: pirut (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-09-22 14:18 EDT by Michal Jaegermann
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-09-22 14:33:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2006-09-22 14:18:35 EDT
Description of problem:

Connection to yum-updatesd may fail.  One of reasons may be that
yum-updatesd is simply not running.  Pirut should be able to handle
such condition without throwing tracebacks like that:

Unable to connect to yum-updatesd...
Traceback (most recent call last):
  File "/usr/bin/puplet", line 179, in updates_avail_handler
    num =
self._countUpdates(self.updatesObject.GetUpdateInfo(dbus_interface="edu.duke.linux.yum"))
  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 edu.duke.linux.yum was not provided by any
.service files

Version-Release number of selected component (if applicable):
pirut-1.1.16-1
Comment 1 Jeremy Katz 2006-09-22 14:33:20 EDT
Fixed

Note You need to log in before you can comment on or make changes to this bug.