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.

Bug 1112034

Summary: Getting the redhat support password wrong (probably) leads to the wrong error.
Product: Red Hat Enterprise Linux 7 Reporter: Wade Mealing <wmealing>
Component: abrtAssignee: abrt <abrt-devel-list>
Status: CLOSED DUPLICATE QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: jfilak
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-24 09:10:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Wade Mealing 2014-06-22 23:31:51 UTC
Description of problem:

An Empathy crash ended up making abrt fire up, I'm probably using the wrong password, but what the heck, it should let me know right ?


Version-Release number of selected component (if applicable):

$ rpm -qa | grep abrt
abrt-2.1.11-12.el7.x86_64
abrt-addon-xorg-2.1.11-12.el7.x86_64
abrt-tui-2.1.11-12.el7.x86_64
abrt-addon-kerneloops-2.1.11-12.el7.x86_64
abrt-gui-2.1.11-12.el7.x86_64
abrt-console-notification-2.1.11-12.el7.x86_64
abrt-libs-2.1.11-12.el7.x86_64
abrt-addon-python-2.1.11-12.el7.x86_64
abrt-addon-vmcore-2.1.11-12.el7.x86_64
abrt-cli-2.1.11-12.el7.x86_64
abrt-gui-libs-2.1.11-12.el7.x86_64
gnome-abrt-0.3.4-6.el7.x86_64
abrt-desktop-2.1.11-12.el7.x86_64
abrt-python-2.1.11-12.el7.x86_64
abrt-addon-pstoreoops-2.1.11-12.el7.x86_64
abrt-addon-ccpp-2.1.11-12.el7.x86_64
abrt-dbus-2.1.11-12.el7.x86_64


How reproducible:

Unknown

Steps to Reproduce:
1. Crash empathy
2. Abrt catches crash
3. Abrt asks to submit, provide support login and password.

Actual results:

--- Running report_RHTSupport ---
Failed to upload uReport to the server 'http://bug-report.itos.redhat.com/reports/new/' with curl: Recv failure: Connection reset by peer
Compressing data
Creating a new case
Error in case creation at 'https://api.access.redhat.com/rs/cases', HTTP code: 401, server says: '401 Unauthorized  This request requires authentication.  Please ensure that you have provided valid BASIC authentication credentials.'
('report_RHTSupport' exited with 1)


Expected results:

Report to be submitted..  If i have the password wrong, to be asked again.  

Additional info:

Unconfirmed if the password is the issue, but something is up.  This happened at Mon Jun 23 09:20:17 EST 2014

Comment 3 Jakub Filak 2014-06-24 09:10:37 UTC
Thank you for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 1104313 ***

Comment 4 Wade Mealing 2014-06-24 09:31:26 UTC
Looks like a dupe, thanks Jakub.