+++ This bug was initially created as a clone of Bug #688637 +++
Created attachment 486039 [details]
pup crash dump
Description of problem:
The update tool (pup) failed during this morning's update. I have attached the crash dump.
Version-Release number of selected component (if applicable): 3.2.22
Not reproducible on my system -- pup now reports that there are no new updates available.
Steps to Reproduce:
1. Click Apply Updates button in the Package Updater.
Package updater retrieves packages, installs them, and fails at what appears to be near the end of the cleanup phase.
successful completion without a crash :)
I have attached the crash "dump" from pup.
--- Additional comment from firstname.lastname@example.org on 2011-03-21 14:39:03 EDT ---
File "/usr/lib/python2.4/site-packages/rhn/transports.py", line 704, in send_http
File "/usr/lib64/python2.4/httplib.py", line 810, in request
self._send_request(method, url, body, headers)
File "/usr/lib64/python2.4/httplib.py", line 833, in _send_request
File "/usr/lib64/python2.4/httplib.py", line 804, in endheaders
File "/usr/lib64/python2.4/httplib.py", line 685, in _send_output
File "/usr/lib64/python2.4/httplib.py", line 664, in send
File "/usr/lib/python2.4/site-packages/rhn/SSL.py", line 217, in write
sent = self._connection.send(data)
SysCallError: (104, 'Connection reset by peer')
...we can't really do anything above the rhn layer, as we aren't expecting to hit the network in posttrans (plus we'd have no idea what to do). I guess you probably want to retry, and/or ignore.
--- Additional comment from email@example.com on 2011-08-23 10:09:23 EDT ---
I would say this is valid BZ.
We should catch all exception and re-raise them is YumBaseError - or some Exception which inherit from YumBaseError, then pulp - or yum or whoever. Should do its best to corectly behave (and they do). But they simply do not expect from plugin anything then YumBaseError.
Although this is not material for RHEL5.8 as the original problem is definitely temporary network error and the fix is only not showing user traceback, but some nice error message. I'm going to close this BZ, but will clone it for RHEL6.
Miroslav, is it correct to assume that this bugzilla is about pup, not pulp?
Is this a duplicate of bug 745167?
Yes, and yes.
*** Bug 745167 has been marked as a duplicate of this bug. ***
Thanks. In that case, would bug 751292 be also a dupe?
Yes. And since bug 751292 has better history (mainly reference to bz where is already fix) I will mark this one as duplicate.
*** This bug has been marked as a duplicate of bug 751292 ***