Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 244827 - Trying to register my RedHat machine for updates but the process fails
Trying to register my RedHat machine for updates but the process fails
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date (Show other bugs)
x86_64 Linux
low Severity urgent
: ---
: ---
Assigned To: Pradeep Kilambi
Corey Welton
Depends On:
  Show dependency treegraph
Reported: 2007-06-19 08:29 EDT by DVSS Shankar Sastry
Modified: 2012-06-20 12:18 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 12:18:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description DVSS Shankar Sastry 2007-06-19 08:29:49 EDT
Description of problem:
Trying to connect my RedHat machine where the AS4 is installed to the Redhat 
network for automatic updates. After pressing forward with all the machine 
details, we get an error that says:

Error Class Code: 70
Error Class Info:
All available subscriptions for the request channel have been exhausted. PLease 
contact a RedHat Network Sales executive.

Further in the description it said there was an error in processing the request 
and to raise a bug in bugzilla.

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 2 Jiri Pallich 2012-06-20 12:18:38 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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