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.
@jboggs -- if I remember correctly, this is something that we manually patch in a python file somewhere. Can we look into getting a patch in the rhn code that will resolve this permanently?
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
-- based on c#2 no tech note required (internal regression)
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2012-0741.html
Created attachment 562442 [details] ovirt.log Description of problem: RHEV-H 6.3: Register to RHN failed. Version-Release number of selected component (if applicable): rhev-hypervisor6-6.3-20120215.0.el6 How reproducible: 100% Steps to Reproduce: 1. Install RHEV-H. 2. Enter Red Hat Network menu. 3. Register RHEV-H to RHN. Actual results: Register RHEV-H to RHN failed. ovirt.log ================================================================= 2012-02-16 08:28:47,408 - INFO - rhn - Registering to RHN account..... 2012-02-16 08:28:47,421 - DEBUG - rhn - ['/usr/sbin/rhnreg_ks', '--username', 'qa', '--password', 'XXXXXXXX', '--novirtinfo', '--norhnsd', '--nopackages', '--force'] 2012-02-16 08:28:47,513 - DEBUG - rhn - Traceback (most recent call last): File "/usr/sbin/rhnreg_ks", line 32, in <module> from up2date_client import rhnreg File "/usr/share/rhn/up2date_client/rhnreg.py", line 16, in <module> File "/usr/share/rhn/up2date_client/up2dateUtils.py", line 12, in <module> File "/usr/share/rhn/up2date_client/up2dateErrors.py", line 16, in <module> ImportError: No module named yum.Errors 2012-02-16 08:28:47,513 - ERROR - rhn - Error registering to RHN account! 2012-02-16 08:28:56,555 - DEBUG - ovirt-config-setup - Current Page: 15 2012-02-16 08:28:56,557 - DEBUG - rhn - RHN Config does not exist 2012-02-16 08:29:00,719 - DEBUG - ovirt-config-setup - Current Page: 15 2012-02-16 08:29:00,722 - DEBUG - rhn - RHN Config does not exist 2012-02-16 08:31:59,784 - DEBUG - ovirt-config-setup - Current Page: 15 2012-02-16 08:31:59,787 - DEBUG - rhn - RHN Config does not exist Expected results: Register to RHN can successful without error. Additional info: