Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 103135

Summary: Unable to authenticate error message
Product: [Retired] Red Hat Raw Hide Reporter: Michael Lee Yohe <michael>
Component: up2dateAssignee: Adrian Likins <alikins>
Status: CLOSED CURRENTRELEASE QA Contact: Fanny Augustin <fmoquete>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: fmonkey
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-08-24 18:57:05 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:
Bug Depends On:    
Bug Blocks: 100644    

Description Michael Lee Yohe 2003-08-26 20:57:28 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686) Gecko/20030722 Galeon/1.3.7

Description of problem:
Upon upgrading to the latest Rawhide up2date, I have noticed that executing
up2date does nothing.  If I start up2date from the console, I receive the following:

# up2date
There was an authentication error: Unable to authenticate

This error message should be more descriptive (citing what the user may or may
not be able to do to fix it).  It should also be available as a dialog box, if
up2date is running in Gnome mode.

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

How reproducible:
Always

Steps to Reproduce:
1. see description


Actual Results:  "There was an authentication error: Unable to authenticate" is
displayed only if up2date is executed from a console.

Expected Results:  The error message should be displayed in a dialog box, and be
more descriptive as to what the actual problem is.

Additional info:
Comment 1 Bill Nottingham 2003-08-27 02:55:44 UTC 
*** Bug 103136 has been marked as a duplicate of this bug. ***
Comment 2 Bill Nottingham 2003-08-27 02:55:51 UTC 
*** Bug 103137 has been marked as a duplicate of this bug. ***
Comment 3 Bill Nottingham 2003-08-27 02:55:56 UTC 
*** Bug 103140 has been marked as a duplicate of this bug. ***
Comment 4 Michael Lee Yohe 2003-08-27 15:53:11 UTC 
Sorry for all the duplicates.. Bugzilla was suffering from extreme horkage
yesterday.
Comment 5 Bill Nottingham 2003-08-29 03:39:38 UTC 
*** Bug 103301 has been marked as a duplicate of this bug. ***
Comment 6 Adam H. Pendleton 2003-09-23 18:05:26 UTC 
I am receiving the same error.  I have deleted my system profile from RHN,
re-run rhn_register, and get these error outputs from rhn_register:

Traceback (most recent call last):
  File "/usr/share/rhn/up2date_client/gui.py", line 1023, in onSendPageNext
    up2dateAuth.updateLoginInfo()
  File "/usr/share/rhn/up2date_client/up2dateAuth.py", line 140, in updateLoginInfo
    raise up2dateErrors.AuthenticationError("Unable to authenticate")
up2date_client.up2dateErrors.AuthenticationError: Unable to authenticate
Traceback (most recent call last):
  File "/usr/share/rhn/up2date_client/gui.py", line 1048, in onRegFinishPagePrepare
    ret = rhnreg.finishMessage(self.systemId)
  File "/usr/share/rhn/up2date_client/rhnreg.py", line 197, in finishMessage
    raise up2dateErrors.CommunicationError(f.faultString)
up2date_client.up2dateErrors.CommunicationError: Error communicating with
server. The message was:
While running 'registration.finish_message': caught
server.apacheRequest.UnknownXML : Invalid request received (function:
registration.finish_message invalid).


I am using up2date-3.9.28-2.
Comment 7 Adam H. Pendleton 2003-09-23 19:55:28 UTC 
Upgrading to up2date-3.9.29-2 fixed this problem for me.