Bug 86585

Summary: Traceback: up2dateErrors.CommunicationError: Error communicating with server.
Product: [Retired] Red Hat Linux Reporter: Mike McLean <mikem>
Component: up2dateAssignee: Adrian Likins <alikins>
Status: CLOSED CURRENTRELEASE QA Contact: Fanny Augustin <fmoquete>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: gafton, mihai.ibanescu
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-27 00:28:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mike McLean 2003-03-25 22:32:57 UTC
* rhnreg_ks --activationkey XXXXXXXXXXXX --profilename XXXXXXXXXXXX

Traceback (most recent call last):
  File "/usr/sbin/rhnreg_ks", line 304, in ?
    main()
  File "/usr/sbin/rhnreg_ks", line 274, in main
    profileName = profilename)
  File "/usr/share/rhn/up2date_client/rhnreg.py", line 290, in registerSystem
    raise up2dateErrors.CommunicationError(f.faultString)
up2dateErrors.CommunicationError: Error communicating with server. The message was:
IMPORTANT MESSAGE FOLLOWS:
We are upgrading our service capabilities. Full service will be restored
within 1 hour.

We apologize for any inconvenience this outage may cause.
    
Thank you for using Red Hat Network.
--the RHN team

Comment 2 Mike McLean 2003-03-25 22:38:02 UTC
Just to be clear:  I'm not complaining that the service is down, just that
rhnreg_ks seems unable to handle it cleanly.

Comment 3 Adrian Likins 2003-04-01 20:52:26 UTC
indeed....

should be fixed in cvs now, or 3.1.24 or higher