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.
This feature is a new plugin based RHN registration page. This happened because the TUI was switched to a new framework and a rework of the Red Hat Network registration page was necessary to use the new urwid framework.
Description of problem:
The UI was re-written in 2.60, but the rhn page was not updated. It needs to be updated before releasing 6.5
Version-Release number of selected component (if applicable):
2.6.0-1
How reproducible:
always
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes
Thanks in advance.
Test version:
rhevh-6.5-20131031.1.0
ovirt-node-3.0.1-7.el6.noarch
Test scenario:
- auto install
- rhn / sam / satellite
- proxy with and without user/password
Test steps:
1. Disable network. - Pass
Disable network and move to RHN menu,
Networking is not configured, please configure it before configuring RHN
2. Enable network. - pass
RHN page used the new UI and all menus work fine,
3. RHN - Pass
Register to RHN can successful.
4. Satellite - Pass
Register to satellite can successful
5. SAM - Pass
Register to SAM can successful.
6. Auto install - pass
Auto install with rhn/sam/satellite parameters
All basic functions work fine now. So the bug is fixed, change bug status to VERIFIED.
I noticed that there are some other minor issue in RHN page(e.g. bug1029724; bug 1022508, bug 998822), but it will not affect for verify this bug.
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-2014-0033.html