Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ 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
How reproducible:
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.
2.
3.
Actual results:
Package updater retrieves packages, installs them, and fails at what appears to be near the end of the cleanup phase.
Expected results:
successful completion without a crash :)
Additional info:
I have attached the crash "dump" from pup.
--- Additional comment from james.antill on 2011-03-21 14:39:03 EDT ---
File "/usr/lib/python2.4/site-packages/rhn/transports.py", line 704, in send_http
headers=self.headers)
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
self.endheaders()
File "/usr/lib64/python2.4/httplib.py", line 804, in endheaders
self._send_output()
File "/usr/lib64/python2.4/httplib.py", line 685, in _send_output
self.send(msg)
File "/usr/lib64/python2.4/httplib.py", line 664, in send
self.sock.sendall(str)
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.
[SNIP]
--- Additional comment from msuchy 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.
Comment 2Jan Pazdziora (Red Hat)
2011-11-24 10:27:02 UTC
Miroslav, is it correct to assume that this bugzilla is about pup, not pulp?
Comment 3Jan Pazdziora (Red Hat)
2011-11-24 10:38:48 UTC
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 ***