[rhn-users] Up2date problems

[Scott Lacy]

Having problems with a couple of systems running up2date:

1)  I recently upgraded one system from RH8 to RH Enterprise AS.  
Up2date runs fine, but the system itself still insists on identifying 
itself to RHN as a Redhat 8 system, which means I can't entitle the 
system to Enterprise AS updates (the entitlement is there just waiting 
on it).  Redhat-release says it's RH Enterprise, so I'm a bit boggled as 
to what to do.


2)   Another Enterprise AS install:

Traceback (most recent call last):
  File "/usr/sbin/up2date", line 1190, in ?
    sys.exit(main() or 0)
  File "/usr/sbin/up2date", line 669, in main
    up2dateAuth.updateLoginInfo()
  File "up2dateAuth.py", line 141, in updateLoginInfo
  File "up2dateAuth.py", line 105, in login
  File "up2dateAuth.py", line 49, in maybeUpdateVersion
  File "/usr/share/rhn/up2date_client/up2dateUtils.py", line 228, in 
getVersion
    release, version = getOSVersionAndRelease()
  File "/usr/share/rhn/up2date_client/up2dateUtils.py", line 221, in 
getOSVersionAndRelease
    raise up2dateErrors.RpmError(
up2date_client.up2dateErrors.RpmError: RPM error.  The message was:
Could not determine what version of Red Hat Linux you are running.
If you get this error, try running

                rpm --rebuilddb


I've done rpm --rebuilddb, and that didn't help.  I did rpm -q 
redhat-release it claimed it wasn't on the system, but the files are on 
the system.  I think the RPM database is hosed, because it says 
/bin/bash and /bin/sh don't belong to any packages.


Any ideas before I break down and call support?  :P


Thanks,

Scott