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.

I was building a package on RHEL6.2 snapshot 3. (python-sqlalchemy from Fedora 15)
and it through a python exception for expected reasons.
abrt catches and displays this exception ok.

However the first time the exception was caught the VM completely locked up and unfortunately I was unable to get any state from it. After restarting it I noticed
the abrt messages in the logs.

I've attached those logs and the abrt directory associated with the crash.
A wild guess is that abrt tried to copy something to its crash dir that caused the machine to lockup.

The VM was hosted on Fedora 15.

Created attachment 533308 [details]
abrt messages from /var/log/messages

Created attachment 533309 [details]
The abrt crash dir associated with this lockup

The particular crash details are unimportant, and I know why it happened.
I'm including the abrt crash dir mainly as general info on the system

Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Can you please send me /etc/abrt/* and /etc/libreport/* (if you still have that machine..)

Created attachment 546290 [details]
requested config

Created attachment 585214 [details]
Proposed patch

Quality Engineering Management has reviewed and declined this request.
You may appeal this decision by reopening this request.