Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1368628

Summary: 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 pr
Product: Red Hat Enterprise Linux 6 Reporter: Arnautu Florin <arnautuflorin>
Component: doc-Technical_NotesAssignee: Lenka Špačková <lkuprova>
Status: CLOSED NOTABUG QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0CC: nitthoma, rhel-docs
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-22 10:51:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Arnautu Florin 2016-08-20 07:25:04 UTC
Description of problem: 


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


How reproducible:


Steps to Reproduce:
1.change default repo
2.try to install screen for example
3.get error "Loaded plugins: rhnplugin
This system is not registered with RHN.
RHN support will be disabled.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: rhel-beta. Please verify its path and try again"
4.try to reregister with valid account
5.get error "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."


Actual results:
cannot register to rhn, cannot yum install any program

Expected results:
should I reinstal the os? it is the only option available for me right now

Additional info:
I am a beginner, it might not be a bug

Comment 2 Lenka Špačková 2016-08-22 09:27:35 UTC
Hello Arnautu,
Thank you for creating this report. However, this is not a documentation bug. Please open a Customer Case to get in touch with a Customer Support representative who can help you identify and fix the problem.

Comment 3 Nithin Thomas 2016-08-22 09:37:37 UTC
Hello Arnautu,

You can go through the below article this may help you:

==> https://access.redhat.com/articles/1345223

Please open a case with us, if the issue still persists:

==> https://access.redhat.com/support/cases/#/case/new

Comment 4 Lenka Špačková 2016-08-22 10:51:58 UTC
Closing this bug as this is not a documentation bug and the problem should be handled outside Bugzilla.