Bug 237201 - Problem with the up2date
Summary: Problem with the up2date
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date
Version: 4.3
Hardware: i386
OS: Linux
Target Milestone: ---
: ---
Assignee: Bret McMillan
QA Contact: Beth Nackashi
: 237198 237199 237200 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2007-04-19 22:32 UTC by Jesus Teran
Modified: 2007-11-17 01:14 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-05-22 14:46:48 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Jesus Teran 2007-04-19 22:32:48 UTC
Description of problem:
I want to register my server in Red Hat Network with up2date and i get the next 

Error Class Code: 70  
Error Class Info: All available subscriptions for the requested channel have 
been exhausted. Please contact a Red Hat Network Sales associate.
Explanation: An error has occurred while processing your request. If this 
problem persists please enter a bug report at bugzilla.redhat.com.
If you choose to submit the bug report, please be sure to include details of 
what you were trying to do when this error occurred and details on how to 
reproduce this problem.

But my subscription is enable right now.

Version-Release number of selected component (if applicable): Red Hat 
Enterprise Linux 4 release 3

How reproducible:

Steps to Reproduce:
1.sign like a root user
2.eject up2date
Actual results:
I get the error that i explined

Expected results:
Register  in the red hat network

Additional info:

Comment 1 Todd Sanders 2007-05-22 14:46:48 UTC
Please contact your Red Hat Support representative.  It appears that you do not
have the proper channel subscriptions in your RHN Account.

Comment 2 Todd Sanders 2007-05-22 14:47:44 UTC
*** Bug 237200 has been marked as a duplicate of this bug. ***

Comment 3 Todd Sanders 2007-05-22 14:48:15 UTC
*** Bug 237199 has been marked as a duplicate of this bug. ***

Comment 4 Todd Sanders 2007-05-22 14:48:58 UTC
*** Bug 237198 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.