Bug 753006

Summary: kobo.client.HubProxy does not raise an exception on login failure
Product: [Fedora] Fedora Reporter: Dan Callaghan <dcallagh>
Component: koboAssignee: Daniel Mach <dmach>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dmach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 13:57:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dan Callaghan 2011-11-11 02:13:09 UTC
Description of problem:
kobo.client.HubProxy does not raise an exception on login failure. Instead it just logs at DEBUG level and discards the exception.

Version-Release number of selected component (if applicable):
kobo-0.3.5-0.1.git.20110614.b85cb7e.el6eso

How reproducible:
always

Steps to Reproduce:
1. Set password incorrectly
2. Construct kobo.client.HubProxy and let it log in
  
Actual results:
A message is logged at DEBUG level, and then the exception is discarded.
2011-11-11 12:03:42 [DEBUG   ] Failed to create new session: <Fault 1: "<class 'turbogears.identity.exceptions.IdentityException'>:Invalid username or password">

Expected results:
Exception should be raised

Additional info:
We would like to make our Beaker lab controller daemons authenticate to the server before they daemonise, so that if they fail to authenticate they will exit and the init script will notice. The idea is to detect a mistake in the configured username/password. Right now this is impossible (the daemon will happily start and continue logging DEBUG messages about the authentication failure).

Also ERROR is probably a more suitable log level than DEBUG for this.

Comment 1 Fedora End Of Life 2013-04-03 14:35:30 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 2 Fedora End Of Life 2015-01-09 16:51:36 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-02-17 13:57:51 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Dan Callaghan 2015-02-17 22:16:10 UTC
This bug still applies but I don't really feel like fighting bugzapper over it so never mind...