Problem with up2date after upgrade

"Krell, Mike" <[email protected]> Wed, 30 Oct 2002 15:47:39 -0600
Newsgroups gmane.network.up2date.current.devel
Message-ID <85063BBE668FD411944400D0B744267A0210DAEE@ausmail.core.coremetrics.com>
  We have a beta environment, running current-1.0.6-1 and hosting a channel
for redhat 7.1.  I've upgraded from up2date-2.7.61-7.x.1 to
up2date-2.8.39-1.7.1 on the servers subscribing to the 7.1 channel, and have
started getting the following messages:

__________________
From the local box:
[root@betaminidb1 /root]# up2date -l

Fetching package list for channel: redhat-i386-7.1...
########################################

Fetching Obsoletes list for channel: redhat-i386-7.1...
There was a fatal error communicating with the server.  The message was:
400: "Function getObsoletes not recognized" while attempting to get 
$RHN/redhat-i386-7.1/getObsoletes/2002102818154
[root@betaminidb1 /root]# 

From /var/log/current.log on the current server:  (repeats several times)
Oct 30 15:34:56 ERROR: New function called: module up2date, function
getObsoletes
Oct 30 15:34:56   params were: [{'client_address': ('127.0.0.1', 45957),
  'command': 'GET',
  'headers': <mimetools.Message instance at 81e5b50>,
  'path':
'https://10.2.2.200:8091/XMLRPC/$RHN/redhat-i386-7.1/getObsoletes/2002102818
1546',
  'version': ''},
 'redhat-i386-7.1',
 '20021028181546']
__________________

Any ideas on this?  Will most likely try downgrading to the former up2date
version after posting this, just curious if anyone else has seen this kind
of problem before.  Thanks!

-Mike