Bug 486454 - Gracefully handle failed 'Save to Bugzilla'
Gracefully handle failed 'Save to Bugzilla'
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
rawhide
All Linux
low Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-19 15:31 EST by Evan McNabb
Modified: 2009-02-19 16:28 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-02-19 16:28:16 EST
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 Evan McNabb 2009-02-19 15:31:14 EST
Description of problem:

If an incorrect username or password is supplied on the Save to Bugzilla screen, the installer has an additional traceback and the only option is to restart the install.

This seems similar to BZ 461148 (which was previously fixed).

Version-Release number of selected component (if applicable):
Rawhide 20090216 (anaconda 11.5.0.19)

How reproducible:
Every time

Steps to Reproduce:
1. Cause traceback in Anaconda
2. "Save" the exception, choose Bugzilla as method
3. Type incorrect username or password, click "Ok"
  
Actual results:

Nothing happens visually with the Anaconda screen. A traceback is shown on Ctrl-Alt-F1:

. . .
filer.LoginError: Could not login to https://bugzilla.redhat.com/xmlrpc.cgi with username mytestuser

At this point it is not possible to retry the submission or choose a different method of saving the dumpfile.

Expected results:

1) It tells the user (on the GUI) that an error occurred
2) The user can correct the username/password and retry
3) The user can select another source to save (scp or local)

Additional info:
Comment 1 Chris Lumens 2009-02-19 16:28:16 EST
Yep, we definitely should have been handling that exception all along.  My documentation even says that.  This will be fixed in the next build of anaconda.  Thanks for the bug report.

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